openstack
/
instack-undercloud
Code Issues Proposed changes

Merge "Clarify need to include environment when deleting a node with cli"

This commit is contained in:
James Slagle 2015-08-25 13:36:43 +02:00 committed by Gerrit Code Review
parent 4f78afa183 2fb3441f81
commit da25967596
2 changed files with 13 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/source/post_deployment/delete_nodes.rst
View File

@ -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 <list of nova instance IDs>
openstack overcloud node delete --stack $STACK_NAME --plan $PLAN_UUID <list of nova instance IDs>
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] <list of nova instance IDs>
openstack overcloud node delete --stack $STACK_NAME --templates [templates dir] <list of nova instance IDs>
If you passed any extra environment files when you created the overcloud (for
instance, in order to configure :doc:`network isolation

5
doc/source/post_deployment/quiesce_compute.rst
View File

@ -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 <service-id> nova-compute
nova service-disable <service-host> nova-compute
Begin the process of migrating VMs off the node::
nova host-servers-migrate <service-id>
nova host-servers-migrate <service-host>
Completing Migration
--------------------