b2ad22819b
The command line workflows with Tuskar have proven to be more limited than using Heat directly. This change removes Tuskar from the CLI documentation and updates all the examples. Essentially this means removing all uses of --plan in the deploy command and all other 'openstack management ...' commands. Tuskar is still referenced in a number of places and can't be fully removed until there is an alternative for the Tuskar UI. Change-Id: I2d4aa114156c5bafb003e6a67862ed6d1449fd98
28 lines
915 B
ReStructuredText
28 lines
915 B
ReStructuredText
.. _delete_nodes:
|
|
|
|
Deleting Overcloud Nodes
|
|
========================
|
|
|
|
You can delete specific nodes from an overcloud with command::
|
|
|
|
openstack overcloud node delete --stack $STACK_NAME --templates [templates dir] <list of nova instance IDs>
|
|
|
|
This command updates the 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`.
|
|
|
|
.. note::
|
|
A list of nova instance IDs can be listed with command::
|
|
|
|
nova list
|