Modify some spelling errors

These changes are good for you to read this document better.
There are change "extention" to "extension" and "accross" to "across"
and so on.

Change-Id: I33337131bb3e19b390df75924191c5fc04529ef5
This commit is contained in:
zhangbailin 2017-08-16 18:23:24 -07:00
parent 9f38a870f6
commit e46d24be09
4 changed files with 5 additions and 5 deletions

View File

@ -16,7 +16,7 @@ rows, or archive them to a 'shadow' table. I believe this is unmaintainable
as we move towards more upgradable releases. Today, most users depend on
manual DB queries to delete this data, but this opens up to human errors.
The goal is to have this be an extention to the `cinder-manage db` command.
The goal is to have this be an extension to the `cinder-manage db` command.
Similar specs are being submitted to all the various projects that touch
a database.

View File

@ -67,7 +67,7 @@ We can do nothing, and ask that each driver maintainer be more careful about
doing any creating of exports inside of initialize_connection if they already
exist. This basically makes create_export useless and a noop for all of those
drivers. I'd rather see every driver use each method as they were intended, so
to make reviewing drivers more consistent accross all of Cinder.
to make reviewing drivers more consistent across all of Cinder.
Data model impact

View File

@ -57,7 +57,7 @@ Proposed change
We will add a new Cinder driver that uses socket API interact with Huawei
SDShypervisor storage. SDShypervisor data panel using private Key value
protocal, so we also add a new connector to realize attach/detach volume.
protocol, so we also add a new connector to realize attach/detach volume.
The following diagram shows the command and data paths.
@ -184,7 +184,7 @@ Add unit test code for Huawei SDShypervisor cinder driver and connector.
Dependencies
============
Because Huawei SDShypervisor data panel using private Key-Value protocal,
Because Huawei SDShypervisor data panel using private Key-Value protocol,
we will create a new libvirt volume driver in Nova to realize
attach/detach volume to instance. Nova BP page is
https://blueprints.launchpad.net/nova/+spec/huawei-sdshypervisor-volume-driver

View File

@ -170,7 +170,7 @@ Individual drivers will implement force_detach as needed by the driver, most
likely calling terminate_connection(..) and possibly other cleanup. The
force_detach(..) api should be idempotent: It should succeed if the volume is
not attached, and succeed if the volume starts off connected and can be
sucessfully detached.
successfully detached.
Alternatives
------------