openstack
/
magnum
Code Issues Proposed changes

Merge "Add documentation for smart scale down feature"

This commit is contained in:
Jenkins 2015-07-14 00:04:22 +00:00 committed by Gerrit Code Review
parent e5eac5fbca cc5aad23e5
commit b00a0c4b74
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/dev/dev-quickstart.rst
View File

@ -235,8 +235,12 @@ by updating the node_count attribute. For example, to add one more node::
Bays will have an initial status of UPDATE_IN_PROGRESS. Magnum will update
the status to UPDATE_COMPLETE when it is done updating the bay.
NOTE: Reducing node_count will remove all your existing containers on the nodes
that are deleted.
NOTE: If you choose to reduce the node_count, Magnum will first try to remove
empty nodes with no containers running on them. If you reduce node_count by
more than the number of empty nodes, Magnum must remove nodes that have running
containers on them. This action will delete those containers. We strongly
recommend using a replication controller before reducing the node_count so
any removed containers can be automatically recovered on your remaining nodes.
Kubernetes provides a number of examples you can use to check that things
are working. You may need to clone kubernetes by::