Hyper-V Spawn on Neutron Event
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_
This approach was already implemented in libvirt [1].
[1] https:/
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
- Milestone target:
- None
- Started by
- Completed by
- Claudiu Belu
Related branches
Related bugs
| Bug #1631872: Not all neutron ports are ACTIVE after the vm spawns (hyper-v) | Fix Released |
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://
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:/
-- claudiub 2017-04-14
