From b94d5314b1f80af17942ae5437a5aae8931ce928 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Wed, 4 Nov 2015 17:01:06 -0500 Subject: [PATCH] cleanup of emc-vnx-driver xml file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit changed avoid to avoids - made plural added “the” where necessary changed computer node to compute node changed vm to VM changed tht to that - typo corrected run on sentences added hyphen when necessary to comply w/rest of doc Change-Id: Ia533376b08aa7da3d46dcba401ddf5f6852a3e2a --- .../block-storage/drivers/emc-vnx-driver.xml | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/doc/config-reference/block-storage/drivers/emc-vnx-driver.xml b/doc/config-reference/block-storage/drivers/emc-vnx-driver.xml index 381dd7a035..f1dd39c6fb 100644 --- a/doc/config-reference/block-storage/drivers/emc-vnx-driver.xml +++ b/doc/config-reference/block-storage/drivers/emc-vnx-driver.xml @@ -307,7 +307,7 @@ storage_vnx_authentication_type = global - This approach avoid the plain text password in your cinder + This approach avoids the plain text password in your cinder configuration file. Supply a security file as below: storage_vnx_security_file_dir=<path to security file> @@ -325,7 +325,7 @@ storage_vnx_authentication_type = global Driver name - For FC Driver, add following option: + For the FC Driver, add the following option: volume_driver=cinder.volume.drivers.emc.emc_cli_fc.EMCCLIFCDriver @@ -368,7 +368,7 @@ storage_vnx_authentication_type = global When a comma-separated list is given to - io_port_list, driver will only register the + io_port_list, the driver will only register the initiator to the ports specified in the list and only return target port(s) which belong to the target ports in the io_port_list instead of all target ports. @@ -411,7 +411,7 @@ storage_vnx_authentication_type = global - Driver will raise an exception if ports in + The driver will raise an exception if ports in io_port_list are not existed in VNX during startup. @@ -468,8 +468,8 @@ storage_vnx_authentication_type = global For volume attaching, the driver has a storage group on VNX for each compute node hosting the vm instances which are going to consume VNX Block Storage (using compute node's hostname as - storage group's name). All the volumes attached to the vm - instances in a computer node will be put into the storage group. + storage group's name). All the volumes attached to the VM + instances in a compute node will be put into the storage group. If destroy_empty_storage_group=True, the driver will remove the empty storage group after its last volume is detached. For data safety, it does not suggest to set @@ -492,7 +492,7 @@ storage_vnx_authentication_type = global
FC SAN auto zoning - EMC VNX FC driver supports FC SAN auto zoning when ZoneManager + The EMC VNX FC driver supports FC SAN auto zoning when ZoneManager is configured. Set zoning_mode to fabric in DEFAULT section to enable this feature. For ZoneManager configuration, please @@ -585,13 +585,13 @@ storage_vnx_authentication_type = global
Extra spec options - Extra spec is used in volume types created in cinder as the - preferred property of volume. + Extra specs are used in volume types created in cinder as the + preferred property of the volume. - Block storage scheduler will use extra spec to find the suitable backend - for the volume. And Block storage driver will create volume based on the - properties specified by extra spec. + The Block storage scheduler will use extra specs to find the suitable back end + for the volume and the Block storage driver will create the volume based on the + properties specified by the extra spec. Use following command to create a volume type: @@ -813,7 +813,7 @@ storage_vnx_authentication_type = global
- Snap copy + Snap-copy @@ -844,14 +844,14 @@ storage_vnx_authentication_type = global - VNX driver supports snap copy which extremely accelerates the + The VNX driver supports snap-copy, which extremely accelerates the process for creating a copied volume. By default, the driver will do full data copy when creating a volume from a snapshot or cloning a volume, which is - time-consuming especially for large volumes. When snap copy is - used, driver will simply create a snapshot and mount it as a + time-consuming especially for large volumes. When the snap-copy is + used, the driver will simply create a snapshot and mount it as a volume for the 2 kinds of operations which will be instant even for large volumes. @@ -859,7 +859,7 @@ storage_vnx_authentication_type = global To enable this functionality, the source volume should have copytype:snap=True in the extra specs of its volume type. Then the new volume cloned from the source or copied - from the snapshot for the source, will be in fact a snap copy + from the snapshot for the source, will be in fact a snap-copy instead of a full copy. If a full copy is needed, retype/migration can be used to convert the snap-copy volume to a full-copy volume which may be time-consuming. @@ -886,7 +886,7 @@ storage_vnx_authentication_type = global Clone and snapshot creation are not allowed on a copied volume - created through snap copy before it is converted to a full + created through the snap-copy before it is converted to a full copy. @@ -1133,7 +1133,7 @@ devices {
Storage group with host names in VNX - When the driver notices tht there is no existing storage group + When the driver notices that there is no existing storage group that has the host name as the storage group name, it will create the storage group and also add the compute node's or Block Storage nodes' registered initiators into the storage group.