Clarify os-stop API description
The original changed description tried to explain the instance data still exists after the API operation, but that was not clear. This patch makes it clear as possible for users. In addition, this patch removes the related sentence of os-start to avoid the same confusion. Change-Id: I46c4d24a67717807f4c6650a739f7855108783e9
This commit is contained in:
parent
e611116e58
commit
095322657d
@ -710,7 +710,6 @@ to start the server.
|
||||
**Asynchronous Postconditions**
|
||||
|
||||
After you successfully start a server, its status changes to ``ACTIVE``.
|
||||
The server appears on the compute node that the Compute service manages.
|
||||
|
||||
**Troubleshooting**
|
||||
|
||||
@ -762,8 +761,8 @@ to stop the server.
|
||||
**Asynchronous Postconditions**
|
||||
|
||||
After you successfully stop a server, its status changes to ``SHUTOFF``.
|
||||
The server instance data appears only on the compute node that
|
||||
Compute service manages.
|
||||
This API operation does not delete the server instance data and the data
|
||||
will be available again after ``os-start`` action.
|
||||
|
||||
Normal response codes: 202
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user