Active Node Creation via adopt state

At present the ironic API explicitly sets the new state for
nodes to the beginning step in the ironic workflow.

As part of hardware fleet lifecycle management, an operator
expects to be able to migrate inventory and control systems
for their hardware fleet utilizing their existing inventory
data and allocation records. Ultimately this means that
an imported host MAY already be allocated and unavailable
for immediate allocation.

As such, a mechanism is required to permit users to put nodes
into an ACTIVE state without performing a deployment operation.

This adds a new API provision_state verb to allow users to move
nodes from MANAGEABLE state to ACTIVE state.

Partial-Bug: #1526315
Change-Id: Ib3eadf4172e93add9a9855582f56cbb3707f3d39
Depends-On: Ie114bfaab249d73ea3ca7c0edc314ca1ed0448eb

1 files changed, 14 insertions, 0 deletions

diff --git a/releasenotes/notes/active-node-creation-a41c9869c966c82b.yaml b/releasenotes/notes/active-node-creation-a41c9869c966c82b.yaml
new file mode 100644
index 000000000..91abd8e91
--- /dev/null
+++ b/releasenotes/notes/active-node-creation-a41c9869c966c82b.yaml
@@ -0,0 +1,14 @@
+---
+features:
+  - Addition of the provision state target verb of ``adopt``
+    which allows an operator to move a node into an ``active``
+    state from ``manageable`` state, without performing a deployment
+    operation on the node. This can be used to represent nodes that have
+    been previously deployed by other means that will now be managed by
+    ironic and be later released to the available hardware pool.
+other:
+  - When a node is enrolled into ironic, upon transition to the
+    ``manageable`` state, the current power state of the node is
+    recorded.  Once the node is adopted and in an ``active`` state,
+    that recorded power state will be enfored by ironic unless an
+    operator changes the power state in ironic.