f838a14bcf
This addresses nits from the two reviews related to the deploy_steps framework: - I5feac3856cc4b87a850180b7fd0b3b9805f9225f - I1baeeaaa6ed521e4189958fd7624cd6c5de96707 It also updates the release note to: - indicate that support for drivers with no deploy steps will be removed in the Stein release (as opposed to the T* release), based on discussions in [1]. - mention that node.deploy_step is available in REST API version 1.44. [1] http://eavesdrop.openstack.org/meetings/ironic/2018/ironic.2018-07-09-15.00.log.html#l-64 Change-Id: I97ab00cab21814287d1b8344b3e4ca0c093fb6ad Story: #1753128 Task: #22592
23 lines
925 B
YAML
23 lines
925 B
YAML
---
|
|
features:
|
|
- |
|
|
The `framework for deployment steps
|
|
<https://specs.openstack.org/openstack/ironic-specs/specs/approved/deployment-steps-framework.html>`_
|
|
is in place. All in-tree drivers (DeployInterfaces) have one (big) deploy
|
|
step; the conductor executes this step when deploying a node.
|
|
|
|
Starting with the Bare Metal REST API version 1.44, the current deploy
|
|
step (if any) being executed is available in a node's ``deploy_step``
|
|
field in the responses for the following queries:
|
|
|
|
* ``GET /v1/nodes/<node identifier>``
|
|
* ``GET /v1/nodes/detail``
|
|
* ``GET /v1/nodes?fields=deploy_step,...``
|
|
deprecations:
|
|
- |
|
|
All drivers must implement their deployment process using `deploy steps`.
|
|
Out-of-tree drivers without deploy steps will be supported until the
|
|
Stein release.
|
|
For more details, see
|
|
`story 1753128 <https://storyboard.openstack.org/#!/story/1753128>`_.
|