On 02/18/2014 12:36 PM, Matt Riedemann wrote: >> 4) We talked about Nova's integration with Neutron and made some good >> progress. We came up with a blueprint (ideally for Icehouse) to improve >> Nova-Neutron interaction. >> >> There are two cases we need to improve that have been particularly >> painful. The first is the network info cache. Neutron can issue an API >> callback to Nova to let us know that we need to refresh the cache. The >> second is knowing that VIF setup is complete. Right now we have cases >> where we issue a request to Neutron and it is processed asynchronously. >> We have no way to know when it has finished. For example, we really >> need to know that VIF plumbing is set up before we boot an instance and >> it tries its DHCP request. We can do this with nova-network, but with >> Neutron it's just a giant race. I'm actually surprised we've made it >> this long without fixing this. > > One or both of these issues (thinking VIF readiness) is also causing a > gate failure in master and stable/havana: > > https://bugs.launchpad.net/nova/+bug/1210483 > > I'd like to propose skipping that test if Tempest is configured with > Neutron until we get the bug fixed/blueprint resolved. > > By the way, can I get a link to the blueprint to reference in the bug > (or vice-versa)?
I haven't seen a blueprint for this yet. Mark, is that something you were planning on driving? -- Russell Bryant _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
