During spawn, the Hyper-V driver should wait for the Neutron
VIF plug events before starting the instance, in order to ensure
that the VIFs are already bound and the guest will be able to
send DHCP requests.
The configuration option "vif_plugging_timeout" will determine
the maximum amount of time to wait for the Neutron events.
Setting the configuration option "vif_plugging_is_fatal" to True
will cause an exception to be raised during spawn, if the Hyper-V
driver did not receive needed Neutron port bound events.
Reviewed: https:/ /review. openstack. org/399001 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=00fdf284085 866c77590255059 ae74b672dd5a85
Committed: https:/
Submitter: Jenkins
Branch: master
commit 00fdf284085866c 77590255059ae74 b672dd5a85
Author: Claudiu Belu <email address hidden>
Date: Thu Nov 17 13:10:06 2016 +0200
hyper-v: wait for neutron vif plug events
During spawn, the Hyper-V driver should wait for the Neutron
VIF plug events before starting the instance, in order to ensure
that the VIFs are already bound and the guest will be able to
send DHCP requests.
The configuration option "vif_plugging_ timeout" will determine
the maximum amount of time to wait for the Neutron events.
Setting the configuration option "vif_plugging_ is_fatal" to True
will cause an exception to be raised during spawn, if the Hyper-V
driver did not receive needed Neutron port bound events.
Closes-Bug: #1631872
Change-Id: Ie8b4cc64f580ac a1115d88258728a b90241d112b