Doc8 and file cleanup
Trivial cleanup, primarily to have something to merge to trigger spec publishing that was missed. Change-Id: I57044352648d8041ec08e761a9e03ecf8f42aaef
This commit is contained in:
parent
991c256b3b
commit
fedba17a10
|
@ -14,7 +14,8 @@ We welcome feedback, comments and bug reports at
|
||||||
Intended audience
|
Intended audience
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
This spec assumes the reader has a general understanding of storage and is familiar with these concepts:
|
This spec assumes the reader has a general understanding of storage and is
|
||||||
|
familiar with these concepts:
|
||||||
|
|
||||||
- ReSTful web services
|
- ReSTful web services
|
||||||
|
|
||||||
|
|
|
@ -125,9 +125,9 @@ only way to safely control this is be requiring that a type of
|
||||||
"multiattach" is created and used on volume creation.
|
"multiattach" is created and used on volume creation.
|
||||||
|
|
||||||
If an additional attach request is made to a volume that is NOT of the type
|
If an additional attach request is made to a volume that is NOT of the type
|
||||||
multi-attach enabled the request should fail as the volume is already in-use, and
|
multi-attach enabled the request should fail as the volume is already in-use,
|
||||||
either a new volume should be created of the correct type, or the volume should
|
and either a new volume should be created of the correct type, or the volume
|
||||||
be retyped. Of course if the policy allows and the type is correct the
|
should be retyped. Of course if the policy allows and the type is correct the
|
||||||
additional attachment request should be processed and the existing
|
additional attachment request should be processed and the existing
|
||||||
attachment(s) are left active and NOT interrupted.
|
attachment(s) are left active and NOT interrupted.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue