ML2 Cisco Nexus MD: Access host ID via port-binding

[Rich Curran]

The Cisco Nexus ML2 mechanism driver code accesses the host ID via a call to the Nova client.
The port-binding blueprint (https://review.openstack.org/#/c/43129) allows for access to the host ID.
Once this BP is merged then this call to the nova client can be removed and replaced with direct port-binding access code.

[Robert Kukura (rkukura)]

Also, since ml2-portbinding could bind any of the segments in a multi-segment network, port_context.bound_segment should be used instead of port_context.network.network_segments[0].

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/48686
Committed: http://github.com/openstack/neutron/commit/6925bd7e00d5c39d20450bcf41e848435b6d9830
Submitter: Jenkins
Branch: master

commit 6925bd7e00d5c39d20450bcf41e848435b6d9830
Author: Rich Curran <email address hidden>
Date: Fri Sep 27 11:35:08 2013 -0400

    ML2 Cisco Nexus mech driver portbinding support

    This commit adds portbinding extension support to
    the cisco nexus mechanism driver.

    Fixes bug: 1220878

    Change-Id: I72003961b46190b82681b471f4f9cb5b11d3d068