openstack/tripleo-docs
Code Issues Proposed changes

Merge "Updates to Bare Metal States in provisioning"

Browse Source
This commit is contained in:
Zuul
2020-05-19 20:24:06 +00:00
committed by Gerrit Code Review
parent 7a0f018b89 aac9788bc0
commit 8171d064b1
1 changed files with 13 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
deploy-guide/source/provisioning/node_states.rst
View File

@@ -8,18 +8,18 @@ TripleO uses or might use. Please refer to `the Ironic documentation
enroll
------
With recent versions of the bare metal API (starting with 1.11), nodes begin
their life in a state called ``enroll``. Nodes in this state are not available
for deployment, nor for most of other actions. Ironic does not touch such nodes
in any way.
In a typical Ironic workflow nodes begin their life in a state called ``enroll``.
Nodes in this state are not available for deployment, nor for most of other
actions. Ironic does not touch such nodes in any way.
Starting with the Newton release, TripleO node registration command allows
to import nodes in this state instead of the default ``available``.
To do so pass the option ``--initial-state=enroll``::
In the TripleO workflow the nodes start their life in the ``manageable`` state
and only see the ``enroll`` state if their power management fails to validate::
openstack baremetal import --initial-state=enroll instackenv.json
openstack overcloud import instackenv.json
Then move the nodes to manageable_ state and eventually to available_.
Nodes can optionally be introspected in this step by passing the --provide flag
which will progress them through through the manageable_ state and eventually to
the available_ state ready for deployment.
manageable
----------
@@ -33,9 +33,9 @@ various pre-deployment actions, such as introspection, RAID configuration, etc.
So to sum it up, nodes in ``manageable`` state are being configured before
exposing them into the cloud.
Nodes get into ``manageable`` state automatically. The ``manage`` action
can be used to bring nodes already moved to available_ state back to
``manageable`` for configuration::
The ``manage`` action
can be used to bring nodes from enroll_ to ``manageable`` or nodes already
moved to available_ state back to ``manageable`` for configuration::
openstack baremetal node manage <NAME OR UUID>
@@ -48,10 +48,7 @@ deployed to at any moment. No long-running configuration actions should be run
in this state.
.. note::
The TripleO introspection command ``openstack baremetal introspection bulk
start`` moves ``available`` nodes to manageable_ state automatically
before and moves them back after a successful introspection. However, nodes
which failed introspection stay in ``manageable`` state and must be
Nodes which failed introspection stay in ``manageable`` state and must be
reintrospected or made ``available`` manually::
openstack baremetal node provide <NAME OR UUID>