Greetings everyone, Now that the PTG is over, I would like to go ahead and get the specification that was proposed to ironic-specs updated to represent the discussions that took place at the PTG.
A few highlights from my recollection: * Ironic being the source of truth for the hardware configuration for the neutron agent to determine where to push configuration to. This would include the address and credential information (certificates right?). * The information required is somehow sent to neutron (possibly as part of the binding profile, which we could send at each time port actions are requested by Ironic.) * The Neutron agent running on the control plane connects outbound to the smartnic, using information supplied to perform the appropriate network configuration. * In Ironic, this would likely be a new network_interface driver module, with some additional methods that help facilitate the work-flow logic changes needed in each deploy_interface driver module. * Ironic would then be informed or gain awareness that the configuration has been completed and that the deployment can proceed. (A different spec has been proposed regarding this.) I have submitted a forum session based upon this and the agreed upon goal at the PTG was to have the ironic spec written up to describe the required changes. I guess the next question is, who wants to update the specification? -Julia __________________________________________________________________________ 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