From cc5aad23e5dc884e5587b9109dc8f64ab06e3785 Mon Sep 17 00:00:00 2001 From: Hongbin Lu Date: Mon, 6 Jul 2015 12:15:17 -0400 Subject: [PATCH] Add documentation for smart scale down feature Change-Id: Ie96a4ea9ad45cd330a4ed69195e101704a36ee85 Implements: blueprint magnum-smart-bay-scale-down --- doc/source/dev/dev-quickstart.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/source/dev/dev-quickstart.rst b/doc/source/dev/dev-quickstart.rst index 4d36c25fe4..5cb60b18ab 100644 --- a/doc/source/dev/dev-quickstart.rst +++ b/doc/source/dev/dev-quickstart.rst @@ -236,8 +236,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::