womax/nova
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

"SUSPENDED" description changed in server_concepts guide and API REF

Browse Source 
The description of "SUSPENDED" server status was misguiding. Rewording
it to make it more accurate.

Change-Id: Ie93b3b38c2000f7e9caa3ca89dea4ec04ed15067
Closes-Bug: #1815403
This commit is contained in:
Sharat Sharma
2019-06-06 06:31:27 -04:00
committed by Stephen Finucane
parent 520fed1d91
commit 3badb674f6
2 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
api-guide/source/server_concepts.rst
+6 -6
View File
@@ -70,12 +70,12 @@ server status is one of the following values:
- ``SUSPENDED``: The server is suspended, either by request or
necessity. This status appears for only the following hypervisors:
XenServer/XCP, KVM, and ESXi. Administrative users may suspend a
server if it is infrequently used or to perform system maintenance.
When you suspend a server, its state is stored on disk, all
memory is written to disk, and the server is stopped.
Suspending a server is similar to placing a device in hibernation;
memory and vCPUs become available to create other servers.
XenServer/XCP, KVM, and ESXi. When you suspend a server, its state is stored
on disk, all memory is written to disk, and the server is stopped.
Suspending a server is similar to placing a device in hibernation and its
occupied resource will not be freed but rather kept for when the server is
resumed. If an instance is infrequently used and the occupied resource needs
to be freed to create other servers, it should be shelved.
- ``UNKNOWN``: The state of the server is unknown. It could be because a part
of the infrastructure is temporarily down (see :doc:`down_cells`