Update active node creation spec based on feedback
Initially the active node creation specification, upon discussion in the ironic community, it was desired to conceal the new states from older clients. The desire to do this has changed. Due to the review feedback from the revision to implement this feature, https://review.openstack.org/#/c/275766/, I am revising the specification. Change-Id: Ie114bfaab249d73ea3ca7c0edc314ca1ed0448eb
This commit is contained in:
parent
a75428a049
commit
41dd497cd3
|
@ -219,19 +219,9 @@ the interface.
|
|||
Upgrades and Backwards Compatibility
|
||||
====================================
|
||||
|
||||
This feature will not be visible to older API clients via a the API
|
||||
This feature will not be usable by older API clients via the API
|
||||
micro-version interface.
|
||||
|
||||
An older API client will receive the ``DEPLOYING`` as opposed to
|
||||
``ADOPTING`` as this is the closest existing state representing the
|
||||
current state of the node. Additionally the state of ``DEPLOYING`` will
|
||||
prevent the nova API from considering the node as an available node for
|
||||
deployment on to.
|
||||
|
||||
An older API client will receive the ``ERROR`` state for any node in
|
||||
``ADOPTFAIL`` to allow for easy identification and deliniation of
|
||||
a node that failed verification.
|
||||
|
||||
Documentation Impact
|
||||
====================
|
||||
|
||||
|
|
Loading…
Reference in New Issue