At a quick glance, this sequence diagram matches what I envisioned/expected.
I'd like to suggest a few additional steps be called out, however I'm not sure how to edit this so I'll write them here. As part of the installation of Ironic, and assuming this is done through Bifrost, the Actor should configure Bifrost for their particular network environment. For instance: what eth device is connected to the IPMI network; what IP ranges can Bifrost assign to physical servers; and so on. There are a lot of other options during the install that can be changed, but the network config is the most important. Full defaults for this roles' config options are here: https://github.com/openstack/bifrost/blob/master/playbooks/roles/bifrost-ironic-install/defaults/main.yml and documentation is here: https://github.com/openstack/bifrost/tree/master/playbooks/roles/bifrost-ironic-install Immediately before "Ironic PXE boots..." step, the Actor must perform an action to "enroll" hardware (the "deployment targets") in Ironic. This could be done in several ways: passing a YAML file to Bifrost; using the Ironic CLI; or something else. "Ironic reports success to the bootstrap operation" is ambiguous. Ironic does not currently support notifications, so, to learn the status of the deployments, you will need to poll the Ironic API (eg, "ironic node-list"). Cheers, --Devananda On 06/23/2016 06:54 PM, Steven Dake (stdake) wrote: > Hey folks, > > I created the following sequence diagram to show my thinking on Ironic > integration. I recognize some internals of the recently merged bifrost > changes > are not represented in this diagram. I would like to see a bootstrap action > do > all of the necessary things to bring up BiFrost in a container using Sean's > WIP > Kolla patch followed by bare metal minimal OS load followed by Kolla > dependency > software (docker-engine, docker-py, and ntpd) loading and initialization. > > This diagram expects ssh keys to be installed on the deployment targets via > BiFrost. > > https://creately.com/diagram/ipt09l352/ROMDJH4QY1Avy1RYhbMUDraaQ4%3D > > Thoughts welcome, especially from folks in the Ironic community or Sean who is > leading this work in Kolla. > > Regards, > -steve > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev