VMware: Port Group and Port ID not explicit from port binding
Bug #1552786 reported by
Thomas Bachman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Thomas Bachman | ||
Mitaka |
Fix Released
|
Low
|
Lee Yarwood |
Bug Description
Various Neutron core plugins and/or ML2 mechanism drivers that support VMware vCenter as a Nova compute backend have different ways to map Neutron resources to vCenter constructs. The vCenter VIF driver code in Nova currently assumes a particular mapping. The Neutron plugin or driver should be able to use the port's binding:vif_details attribute to explicitly specify the vCenter port key and port group to be used for the VIF.
Changed in nova: | |
assignee: | nobody → Giridhar Jayavelu (gjayavelu) |
tags: | added: mitaka-backport-potential |
Changed in nova: | |
importance: | Wishlist → Low |
To post a comment you must log in.
This sounds like a feature enhancement rather than a bug, so marking this as wishlist.