Hyper-V Spawn on Neutron Event

Registered by Claudiu Belu on 2015-11-18

Under large scale deployments, Hyper-V Neutron port binding can take a longer time. Starting the instance before the port was setup, can cause the instance's DHCP requests to timeout and thus, become unreachable.

This problem can be solved by waiting for the Neutron port bound event before starting the VM. The configuration option "vif_plugging_timeout" will determine the maximum amount of time to wait for the Neutron event.

This approach was already implemented in libvirt [1].

[1] https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4569

Blueprint information

Status:
Complete
Approver:
John Garbutt
Priority:
Low
Drafter:
Claudiu Belu
Direction:
Needs approval
Assignee:
Claudiu Belu
Definition:
Obsolete
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Completed by
Claudiu Belu on 2017-04-13

Related branches

Sprints

Whiteboard

As there is no code up for review, removing this blueprint from mitaka, as part of the non-priority Feature Freeze. For more details please see: http://docs.openstack.org/developer/nova/process.html --johnthetubaguy 2015.01.15

This was approved as a feature parity specless blueprint in mitaka, re-approving for newton. -- mriedem 20160323

There is no code up for this yet and we're at non-priority feature freeze so this is going to be deferred for
the Newton release. You can re-propose a spec for Ocata if you plan to pursue this.
-- mriedem 20160629

No longer valid - behaviour already implemented - it was marked as a high importance bug:
https://bugs.launchpad.net/tempest/+bug/1631872

-- claudiub 2017-04-14

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.