From 2fb3441f81bc25036b4c9f73feb15a25339b35b3 Mon Sep 17 00:00:00 2001 From: marios Date: Tue, 4 Aug 2015 16:49:11 +0300 Subject: [PATCH] Clarify need to include environment when deleting a node with cli As documented @ BZ 1245226 clarify that you must include the custom environment files to the node delete cli. Also squashes 2 nits in the quiesce procedure we document and point to from the node delete docs. Change-Id: Ie785939cbb999adb0fa87c726d13f94c8ad39bf4 Related-Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1245226 --- doc/source/post_deployment/delete_nodes.rst | 12 ++++++++++-- doc/source/post_deployment/quiesce_compute.rst | 5 +++-- 2 files changed, 13 insertions(+), 4 deletions(-) diff --git a/doc/source/post_deployment/delete_nodes.rst b/doc/source/post_deployment/delete_nodes.rst index a169132a5..3c91e7b45 100644 --- a/doc/source/post_deployment/delete_nodes.rst +++ b/doc/source/post_deployment/delete_nodes.rst @@ -5,12 +5,20 @@ Deleting Overcloud Nodes You can delete specific nodes from an overcloud with command:: - openstack overcloud node delete --stack $STACK --plan $PLAN_UUID + openstack overcloud node delete --stack $STACK_NAME --plan $PLAN_UUID This command updates number of nodes in tuskar plan and then updates heat stack with updated numbers and list of resource IDs (which represent nodes) to be deleted. +.. note:: + If you passed any extra environment files when you created the overcloud (for + instance, in order to configure :doc:`network isolation + <../advanced_deployment/network_isolation>`), you must pass them again here + using the ``-e`` or ``--environment-file`` option to avoid making undesired + changes to the overcloud. + + .. note:: Before deleting a compute node please make sure that the node is quiesced, see :ref:`quiesce_compute`. @@ -27,7 +35,7 @@ If the overcloud was :doc:`deployed from heat templates directly <../advanced_deployment/template_deploy>` then use the ``--templates`` parameter when deleting nodes:: - openstack overcloud node delete --stack $STACK --templates [templates dir] + openstack overcloud node delete --stack $STACK_NAME --templates [templates dir] If you passed any extra environment files when you created the overcloud (for instance, in order to configure :doc:`network isolation diff --git a/doc/source/post_deployment/quiesce_compute.rst b/doc/source/post_deployment/quiesce_compute.rst index 83e1867e2..1f17c8f3e 100644 --- a/doc/source/post_deployment/quiesce_compute.rst +++ b/doc/source/post_deployment/quiesce_compute.rst @@ -52,11 +52,12 @@ First, obtain a list of the current Nova services:: Disable the `nova-compute` service on the node you wish to quiesce, to prevent new VMs being scheduled on it:: - nova service-disable nova-compute + nova service-disable nova-compute + Begin the process of migrating VMs off the node:: - nova host-servers-migrate + nova host-servers-migrate Completing Migration --------------------