Add a Mistral workflow to move nodes from available to manageable

[Dougal Matthews]

The baremetal workflows have provide_manageable_nodes, which takes all manageable nodes and makes them available. We don't have a good way to do the opposite of this.

Either a specific workflow would do, or a more generic workflow could solve multiple cases.

[Dougal Matthews (d0ugal)]

This bug came out of this change: https://github.com/openstack/python-tripleoclient/commit/f1398ac51b01e6700abe4d0e51bb51d1f6fed032#diff-754d55395cca5fd122f66e1b7069a2a2R256

[Emilien Macchi (emilienm)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[Toure Dunnon (toure)]

What would be the criteria to move a node from managed to available? Would this just be at the operator's discretion?

[Dougal Matthews (d0ugal)]

I have updated the title and the tags. This has been partially solved, the remaining issue is to update tripleoclient to use the workflow tripleo.baremetal.v1.set_node_state instead of the tripleoclient.utils.set_node_state Python function.

[Dougal Matthews (d0ugal)]

Actually, I added the old tags and reset the title. The workflow "tripleo.baremetal.v1.set_node_state" almost does what this bug wants, but it expects one node and we want to transition a set of nodes. So the criteria for this bug would be exactly the same as that workflow but with multiple nodes :)

Then tripleoclient needs to be updated to use it instead of its own set_node_state function.

[Dougal Matthews (d0ugal)]

Thinking about this more, I am not even sure it is worth doing. It is really low priority IMO.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, NEWTON, OCATA, PIKE, QUEENS, QUEENS).
  Valid example: CONFIRMED FOR: FUTURE