Related to https://review.openstack.org/#/c/84361/ and https://bugs.launchpad.net/ironic/+bug/1300589
Updates to Neutron resources via its API are processed asynchronously on its backend. This exposes potential races with Ironic. Example: an API request from Ironic to update a port's DHCP settings will return successfully long before the associated dnsmasq config has been updated and the server restarted. There is a small potential for a race condition where Ironic will boot a machine before its DHCP has been properly configured, especially if the machine boots very quickly (ie a local VM)
Though none are used by Ironic (yet?), other Neutron operations are dependent on some other state in Neutron. For instance, a firewall will stay PENDING until an associated router and router interface have been created and are ACTIVE.
We need a way to synchronize these events. During Icehouse, Nova solved almost identical issues regarding orchestration between Nova and Neutron via an admin API endpoint Neutron can use to post back notifications. Ironic's Neutron usage is relatively limited ATM, but providing a framework similar to Nova's for this type of orchestration would solve the current issues and allow future drivers to take advantage of other Neutron features.
Hi Shraddha,
Are you still working this bug?