VMware: unable to launch instance when using NSXv

[Gary Kotton]

A VXLAN DVS portgroup will contain the UUID of the netron network. It will not contain the name-UUID as proposed in patch 709127cabed602d6868dedf0bef7ca9547a86e06. The reason for this is that the the VC has a maximum length of 80 characters for the name of a port group. A VXLAN port group also needs to contain then DVS and VDN scope morefs.
The fact that the name is included in the search for the matching portgroup leads to instances not being able to be booted and a error 'No available host'

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 78a706f784b8b42df4c85ac18270da848c99cd67
Author: Gary Kotton <email address hidden>
Date: Wed Jan 28 04:46:02 2015 -0800

    Network: correct VMware DVS port group name lookup

    Commit 709127cabed602d6868dedf0bef7ca9547a86e06 added support
    for DVS network backends. The original design included the
    name of the network in the port group. The name was excluded due
    to VC limitations (maximum of 80 characters for a port group name).
    This prevents instances from being booted as there is no match
    for the port group.

    The fix ensures that we only use the Neutron network UUID.

    Change-Id: I7e3223f88c4f477116ac493eb45466ea1c0a29a9
    Closes-bug: #1415461