openstack
/
openstack-virtual-baremetal
Code Issues Proposed changes

Add docs about deleting an OVB environment 

Previously it was assumed that the user would know to delete the
Heat stack to delete an environment.  Since that's not actually
obvious to a new user, add explicit documentation of it.
This commit is contained in:
Ben Nemec 2018-01-24 09:27:17 -06:00
parent c65fbbb9b5
commit f001b76e08
2 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/deploy/baremetal.rst
View File

@ -111,3 +111,12 @@ method, which creates most of the resources needed automatically.
#. The undercloud vm can now be used with something like TripleO
to do a baremetal-style deployment to the virtual baremetal instances
deployed previously.
Deleting an OVB Environment
---------------------------
All of the OpenStack resources created by OVB are part of the Heat stack, so
to delete the environment just delete the Heat stack. There are a few local
files that may also have been created as part of the deployment, such as
nodes.json files and bmc_bm_pairs. Once the stack is deleted these can be
removed safely as well.

9
doc/source/deploy/quintupleo.rst
View File

@ -74,6 +74,15 @@ however.
that lists which BMC address corresponds to a given baremetal
instance.
Deleting an OVB Environment
---------------------------
All of the OpenStack resources created by OVB are part of the Heat stack, so
to delete the environment just delete the Heat stack. There are a few local
files that may also have been created as part of the deployment, such as
ID environment files, nodes.json files, and bmc_bm_pairs. Once the stack is
deleted these can be removed safely as well.
.. _advanced-options:
Advanced Options