VMware: Port Group and Port ID not explicit from port binding

Bug #1552786 reported by Thomas Bachman
6
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.

Revision history for this message
Matt Riedemann (mriedem) wrote :

This sounds like a feature enhancement rather than a bug, so marking this as wishlist.

tags: added: vmware
Changed in nova:
importance: Undecided → Wishlist
status: New → Opinion
Tracy Jones (tjones-i)
Changed in nova:
assignee: nobody → Giridhar Jayavelu (gjayavelu)
Revision history for this message
Matt Riedemann (mriedem) wrote :

Honestly you probably need to file a blueprint for this in the newton release:

https://wiki.openstack.org/wiki/Blueprints

Revision history for this message
Tracy Jones (tjones-i) wrote :

Giri - can you take a look? This may not be the scope of a bug but may need a BP

Revision history for this message
Thomas Bachman (tbachman) wrote :

I'll submit a patch, in order to give folks an idea of the extent of the change -- might help determine whether or not it merits a blueprint.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/288076

Changed in nova:
assignee: Giridhar Jayavelu (gjayavelu) → Thomas Bachman (bachman)
status: Opinion → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/288076
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e964b4778cfe6a1864718bdad4ab037ddf976766
Submitter: Jenkins
Branch: master

commit e964b4778cfe6a1864718bdad4ab037ddf976766
Author: Thomas Bachman <email address hidden>
Date: Thu Mar 3 10:32:09 2016 -0500

    VMware: Use Port Group and Key in binding details

    This uses the port group and port key information passed
    via the binding:vif_details attribute, if available. This
    allows these parameters to be passed explicitly.

    Change-Id: I41949e8134c2ca860e7b7ad3a2679b9f2884a99a
    Closes-Bug: #1552786

Changed in nova:
status: In Progress → Fix Released
tags: added: mitaka-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/304738

Matt Riedemann (mriedem)
Changed in nova:
importance: Wishlist → Low
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/nova 14.0.0.0b1

This issue was fixed in the openstack/nova 14.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (stable/mitaka)

Reviewed: https://review.openstack.org/304738
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ac04b087d84496e8f7d164883bb0c9ecb7296fc4
Submitter: Jenkins
Branch: stable/mitaka

commit ac04b087d84496e8f7d164883bb0c9ecb7296fc4
Author: Thomas Bachman <email address hidden>
Date: Thu Mar 3 10:32:09 2016 -0500

    VMware: Use Port Group and Key in binding details

    This uses the port group and port key information passed
    via the binding:vif_details attribute, if available. This
    allows these parameters to be passed explicitly.

    Change-Id: I41949e8134c2ca860e7b7ad3a2679b9f2884a99a
    Closes-Bug: #1552786
    (cherry picked from commit e964b4778cfe6a1864718bdad4ab037ddf976766)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 13.1.2

This issue was fixed in the openstack/nova 13.1.2 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.