yahoo-eng-team team mailing list archive

[OpenStack Infra <1552786@xxxxxxxxxxxxxxxxxx>]

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 <tbachman@xxxxxxxxx>
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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1552786

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

Status in OpenStack Compute (nova):
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1552786/+subscriptions