Hi Mathieu,
The current train of thought is to have neutron notify nova via a call back
when ports are ready. This model should hopefully scale better as now
nova-compute won't need to poll on neutron checking on the port status. Dan
Smith already has a patch out that adds an api to nova for it to
Hi Aaron,
You seem to have abandonned this patch :
https://review.openstack.org/#/c/74218/
You want neutron to update port in nova, can you please tell us how do
you want to do that?
I think that we should use such a mechanism for live-migration.
live-migration should occur once the port is set
Hi Maru,
Thanks for getting this thread started. I've filed the following blueprint
for this:
https://blueprints.launchpad.net/nova/+spec/check-neutron-port-status
and have a have a prototype of it working here:
https://review.openstack.org/#/c/74197/
https://review.openstack.org/#/c/74218/
On
+1 for this feature which could potentially resolve a race condition
that could occur after port-binding refactoring in ML2 [1].
in ML2, the port could be ACTIVE once a MD has bound the port. the
vif_type could then be known by nova, and nova could create the
network correctly thanks to vif_type an
Booting a Nova instance when Neutron is enabled is often unreliable due to the
lack of coordination between Nova and Neutron apart from port allocation.
Aaron Rosen and I have been talking about fixing this by having Nova perform a
check for port 'liveness' after vif plug and before vm boot. T
