openstack/cinder
Code Issues Proposed changes

Replace Chinese punctuation with English punctuation

Browse Source 
Curly quotes(Chinese punctuation) usually input from Chinese input method.
When read from english context, it makes some confusion.

Change-Id: I52bdfb16b1270df9d2a8109608a6a1bebc300966
This commit is contained in:
inspurericzhang 2018-05-02 17:53:13 +08:00
parent ac2a518b5e
commit 170298e37c
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/cli/cli-manage-volumes.rst
View File

@ -682,8 +682,8 @@ The arguments to be passed are:
multiple properties)
``--state <state>``
New snapshot state. (“available”, “error”, “creating”, “deleting”,
or “error_deleting”)
New snapshot state. ("available", "error", "creating", "deleting",
or "error_deleting")
(admin only) (This option simply changes the state of the snapshot in the
database with no regard to actual status, exercise caution when using)

6
doc/source/contributor/attach_detach_conventions.rst
View File

@ -48,14 +48,14 @@ reserve_volume(self, context, volume)
-------------------------------------
Probably the most simple call in to Cinder. This method simply checks that
the specified volume is in an “available” state and can be attached.
the specified volume is in an "available" state and can be attached.
Any other state results in an Error response notifying Nova that the volume
is NOT available. The only valid state for this call to succeed is “available”.
is NOT available. The only valid state for this call to succeed is "available".
NOTE: multi-attach will add "in-use" to the above acceptable states.
If the volume is in fact available, we immediately issue an update to the Cinder
database and mark the status of the volume to “attaching” thereby reserving the
database and mark the status of the volume to "attaching" thereby reserving the
volume so that it won't be used by another API call anywhere else.
initialize_connection(self, context, volume, connector)

2
doc/source/contributor/migration.rst
View File

@ -189,7 +189,7 @@ Two volume types need to be created. One is with the extra specs:
What can be tracked during volume migration
-------------------------------------------
The volume migration is an administrator only action and it may take
a relatively long time to finish. The property ‘migration status’ will
a relatively long time to finish. The property 'migration status' will
indicate the stage of the migration process for the volume. The
administrator can check the 'migration status' via the 'cinder list'
or 'cinder show <volume-id>' command. The 'cinder list' command presents