openstack
/
nova
Code Issues Proposed changes

Correct some nits for moving servers in concept doc 

* There isn't any support specify a host for cold migration API.
  Remove the words about cold migration can do explicitly decision.
* Use some cloud operators instead of some users for resource
  optimization case.

blueprint complete-todo-in-api-concept-doc

Change-Id: Iea266d61551666edfa4f6bb3d4f3d3f03c8b57f4
This commit is contained in:
He Jie Xu 2015-11-26 15:07:53 +08:00
parent d93cedb8af
commit 29847bb26c
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
api-guide/source/server_concepts.rst
View File

@ -413,10 +413,9 @@ and live migration (moving a server that is active).
Cold migration moves a server from one host to another by copying its
state, local storage and network configuration to new resources
allocated on a new host selected by scheduling policies or as
an explicit decision. The operation is relatively quick as the
server is not changing its state during the copy process. The user
does not have access to the server during the operation.
allocated on a new host selected by scheduling policies. The operation is
relatively quick as the server is not changing its state during the copy
process. The user does not have access to the server during the operation.
Live migration moves a server from one host to another while it
is active, so it is constantly changing its state during the action.
@ -461,9 +460,9 @@ a cloud:
- **Resource Optimization**
To reduce energy usage, some users will try and move servers so
they fit into the minimum number of hosts, allowing some servers
to be turned off.
To reduce energy usage, some cloud operators will try and move
servers so they fit into the minimum number of hosts, allowing
some servers to be turned off.
Sometimes higher performance might be wanted, so servers are
spread out between the hosts to minimize resource contention.