BigSwitch: driver doesn't include current bound segment

[Kevin Benton]

The current ML2 mechanism driver for bigswitch doesn't include the current bound segment for the backend controller. It's just inferring it from the segment ID in the network, which won't work if the network has multiple segments.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/81367
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=3d6381fd524f980d32d7129292372b0707d479a0
Submitter: Jenkins
Branch: master

commit 3d6381fd524f980d32d7129292372b0707d479a0
Author: Kevin Benton <email address hidden>
Date: Tue Mar 18 13:11:27 2014 -0700

    BigSwitch ML2: Include bound_segment in port

    Includes bound segment in port create/update
    requests to disambiguate when the parent network
    has multiple segments.

    Closes-Bug: #1294355
    Change-Id: I59ef38aa5de46c1229384e0c4a9f0ee01c1bc678