4f8b97dff6
This updates the state machine diagram and documentation to indicate which transitions are initiated by API requests versus the ones that are internally done by the conductor. Stable states are highlighted a bit. Change-Id: I1a2de81b14696286f1da47c06374ad235962c849 Closes-Bug: #1527316
31 lines
1.0 KiB
ReStructuredText
31 lines
1.0 KiB
ReStructuredText
.. _states:
|
|
|
|
======================
|
|
Ironic's State Machine
|
|
======================
|
|
|
|
State Machine Diagram
|
|
=====================
|
|
|
|
The diagram below shows the provisioning states that an Ironic node goes
|
|
through during the lifetime of a node. The diagram also depicts the events
|
|
that transition the node to different states.
|
|
|
|
Stable states are highlighted with a thicker border. All transitions from
|
|
stable states are initiated by API requests. There are a few other
|
|
API-initiated-transitions that are possible from non-stable states.
|
|
The events for these API-initiated transitions are indicated with '(via API)'.
|
|
Internally, the conductor initiates the other transitions (depicted in gray).
|
|
|
|
.. figure:: ../images/states.svg
|
|
:width: 660px
|
|
:align: left
|
|
:alt: Ironic state transitions
|
|
|
|
.. note::
|
|
|
|
For more information about the states, see the specification located at
|
|
`ironic-state-machine`_.
|
|
|
|
.. _ironic-state-machine: http://specs.openstack.org/openstack/ironic-specs/specs/kilo-implemented/new-ironic-state-machine.html
|