During node registration, the following sequence occurs in tripleoclient and mistral
o Get token from keystone
o POST a "register" workflow to mistral (tripleo.baremetal.v1.register_or_update)
o open a websocket to wait for the mistral workflow to finish
- In mistral the following happens
- for each node register it with ironic (essentially the same the the entire OSPd 9 process)
- for each node
- set the node provision state too manageable
- wait for ironic to actually set the node state (1 sec sleep between checks)
- set the node provision state too available
- wait for ironic to actually set the node state (1 sec sleep between checks)
- set the node provision state too manageable
o POST a "provide" workflow to mistral (tripleo.baremetal.v1.provide)
o open a websocket to wait for the mistral workflow to finish
- In mistral the following happens
- for each node
- set the node provision state too available
It looks like we are duplicating the logic to set the nodes to manageable and then too available.
I believe the problem is in
http://git.openstack.org/cgit/openstack/tripleo-common/tree/workbooks/baremetal.yaml
the "register_or_update" workflow calls
tripleo_common.actions.baremetal:RegisterOrUpdateNodes which
registers nodes, sets them too manageable, waits for each one to set, sets each node to available and waits for the state of each node to set again
tripleo.baremetal.v1.set_node_state which
which sets each node back too manageable,
tripleoclient then also calls the "provide" workflow
which sets each node to available again
This adds a lot of time to node registration, a lot of this time is mistral overhead
Fix proposed to branch: master
Review: https:/