Jay S. Bryant 0395353c4b Move config-reference to configuration

It was discovered today that the 'config-reference' directory
was supposed to have been renamed to 'configuration'.  The doc
team was expecting it to be at that location so that they could
automatically link to it from contributor/index.html .

This patch just moves the directory.  I am going to be submitting
a subsequent patch that properly sets out the framework for the
additional directories so that we don't have addition problems
in the future.

Change-Id: I6729aaf4593a0b089277f6d7d0aa50fee3ca340f

2017-07-18 13:10:25 -05:00

3.1 KiB

Raw Blame History

Coho Data volume driver

The Coho DataStream Scale-Out Storage allows your Block Storage service to scale seamlessly. The architecture consists of commodity storage servers with SDN ToR switches. Leveraging an SDN OpenFlow controller allows you to scale storage horizontally, while avoiding storage and network bottlenecks by intelligent load-balancing and parallelized workloads. High-performance PCIe NVMe flash, paired with traditional hard disk drives (HDD) or solid-state drives (SSD), delivers low-latency performance even with highly mixed workloads in large scale environment.

Coho Data's storage features include real-time instance level granularity performance and capacity reporting via API or UI, and single-IP storage endpoint access.

Supported operations

Create, delete, attach, detach, retype, clone, and extend volumes.
Create, list, and delete volume snapshots.
Create a volume from a snapshot.
Copy a volume to an image.
Copy an image to a volume.
Create a thin provisioned volume.
Get volume statistics.

Coho Data QoS support

QoS support for the Coho Data driver includes the ability to set the following capabilities in the OpenStack Block Storage API cinder.api.contrib.qos_specs_manage QoS specs extension module:

maxIOPS - The maximum number of IOPS allowed for this volume.
maxMBS - The maximum throughput allowed for this volume.

The QoS keys above must be created and associated with a volume type. For information about how to set the key-value pairs and associate them with a volume type, see the volume qos section in the OpenStackClient command list.

Note

If you change a volume type with QoS to a new volume type without QoS, the QoS configuration settings will be removed.

System requirements

NFS client on the Block storage controller.

Coho Data Block Storage driver configuration

Create cinder volume type.
```
$ openstack volume type create coho-1
```

Edit the OpenStack Block Storage service configuration file. The following sample, /etc/cinder/cinder.conf, configuration lists the relevant settings for a typical Block Storage service using a single Coho Data storage:

[DEFAULT]
enabled_backends = coho-1
default_volume_type = coho-1

[coho-1]
volume_driver = cinder.volume.drivers.coho.CohoDriver
volume_backend_name = coho-1
nfs_shares_config = /etc/cinder/coho_shares
nas_secure_file_operations = 'false'

Add your list of Coho Datastream NFS addresses to the file you specified with the nfs_shares_config option. For example, if the value of this option was set to /etc/cinder/coho_shares, then:
```
$ cat /etc/cinder/coho_shares
<coho-nfs-ip>:/<export-path>
```
Restart the cinder-volume service to enable Coho Data driver.

3.1 KiB Raw Blame History