openstack/cinder-specs
Code Issues Proposed changes

Modify grammatical errors

Browse Source 
Change-Id: I68d7c34de77b664f9446dd32dada9064d83272ca
This commit is contained in:
chengebj5238 2018-02-06 17:28:39 +08:00
parent 1c47dd0690
commit f0a6ebcad2
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
specs/kilo/volume-sorting.rst
View File

@ -147,13 +147,13 @@ returned from a detailed query is a valid sort key.
Performance data was gathered by running on a simple devstack VM with 2GB Performance data was gathered by running on a simple devstack VM with 2GB
memory. 5000 volumes were inserted into the DB. The data shows that the memory. 5000 volumes were inserted into the DB. The data shows that the
sort time on the main data table is dwarfed (see first table below) when sort time on the main data table is dwarfed (see first table below) when
running a detailed query -- most of the time is spent querying the the other running a detailed query -- most of the time is spent querying the other
tables for each item; therefore, the impact of the sort key on a detailed tables for each item; therefore, the impact of the sort key on a detailed
query is minimal. query is minimal.
For example, the data below compares the processing time of a GET request for For example, the data below compares the processing time of a GET request for
a non-detailed query to a detailed query with various limits using the default a non-detailed query to a detailed query with various limits using the default
sort keys. The purpose of this table is to show the the processing time for a sort keys. The purpose of this table is to show the processing time for a
detailed query is dominated by getting the additional details for each item. detailed query is dominated by getting the additional details for each item.
+-------+--------------------+----------------+---------------------------+ +-------+--------------------+----------------+---------------------------+

2
specs/liberty/volume-migration-improvement.rst
View File

@ -189,7 +189,7 @@ REST API impact
The REST API should be able to provide the migration status and the migration The REST API should be able to provide the migration status and the migration
progress information for the volumes. For the migration status, it can be progress information for the volumes. For the migration status, it can be
retrieved from the database. For the the migration progress, the API request retrieved from the database. For the migration progress, the API request
will be scheduled to the cinder volume service, where the volume is located, will be scheduled to the cinder volume service, where the volume is located,
and cinder volume service reports the updated progress back. and cinder volume service reports the updated progress back.

2
specs/mitaka/assisted_snapshot_improvements.rst
View File

@ -51,7 +51,7 @@ volume_admin_metadata table::
volume : relationship joining to volumes table volume : relationship joining to volumes table
Setting a snapshot_status metadata value will allow the API layer Setting a snapshot_status metadata value will allow the API layer
to transfer this information to the the volume service. to transfer this information to the volume service.
Volume manager<->driver interaction Volume manager<->driver interaction
----------------------------------- -----------------------------------