Hi Mohammad,
Why is the blocking needed? Is it to report some kind of status back to
Docker/Kubernetes, or to allow some follow-on action to happen?
When using networking-calico as the driver, I think that only option (1)
would work, out of the options you've suggested below. (3) doesn't work,
Neutron has the ability already of sending an event as a REST call to
notify a third party that a port became active [1]
This is used by Nova to hold on booting instances until network has been
wired.
Perhaps kuryr could leverage this without having to tap into the AMQP bus,
as that would be implem
For the Kuryr project, in order to support blocking until vifs are plugged
in (that is adding config options similar to the following options define
in Nova: vif_plugging_is_fatal and vif_plugging_timeout), we need to detect
that the Neutron plugin being used is done with plugging a given vif.
H
