This is not a bug of Neutron, vmware will use "DEFAULT.neutron_ovs_bridge"
value in nova.conf as vm bridge if using OpenStack Networking Service and ovs
l2 agent started.
so set this bug as invalid.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1255898
Title:
Can't assign a vm to the vmware.integration_bridge if using OpenStack
Networking Service
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
When using vcenter as the compute host with OpenStack Networking Service, a
port group need to be created firstly,
but according to the config-referrence
guide(http://docs.openstack.org/havana/config-reference/content/vmware.html)
vm failed to bound into the vmware.integration_bridge of file
/etc/nova/nova.conf.
Root cause is that seems the logical is the vcenter driver will first
get the value of bridge assigned by the OpenStack Networking Service
which Neutron has a default value "br-int", if none then try to get
the vmware.integration_bridge designed in Nova config files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1255898/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
