VMware: nova-network creates a port group only on one ESXi in cluster in case with VlanManager

Bug #1498865 reported by Ilya Bumarskov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

In case with VlanManager nova-compute creates a appropriate port group (vSwitch) only on one ESXi in cluster. Thus all instances are created only on one ESXi host in cluster.

Openstack Release: Kilo on Ubuntu 14.04

root@node-2:~# dpkg -l | grep nova
ii nova-api 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - compute API frontend
ii nova-cert 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - certificate manager
ii nova-common 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - common files
ii nova-compute 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - compute node
ii nova-compute-kvm 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - compute node (KVM)
ii nova-conductor 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - conductor service
ii nova-consoleauth 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - Console Authenticator
ii nova-consoleproxy 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - NoVNC proxy
ii nova-network 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - network manager
ii nova-objectstore 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - object store
ii nova-scheduler 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - virtual machine scheduler
ii python-nova 1:2015.1.1-1~u14.04+mos19662 all OpenStack Compute - libraries
ii python-novaclient 1:2.23.0-1~u14.04+mos1245 all client library for OpenStack Compute API

Steps to reproduce:

1. Deploy Fuel 7.0
2. Create env with vcenter support
3. Set Nova VlanManager
4. Add a controller node
5. Configure VMware settings (At least two ESXi hosts should be in cluster)
6. Deploy enviroment
7. Login to Horizon and create a bunch of instances using vcenter availability zone
8. Verify ESXi network settings using vCenter

Observed behavior:

Appropriate port group (br103 in my case) was added only on one ESXi in cluster. All VMs were created only on one ESXi.

Workaround:
We can manually add appropriate port groups on other ESXi in cluster. In such case all new created VMs will be distributed across all ESXi in cluster.

Tags: network vmware
tags: added: vmware
Revision history for this message
Matt Riedemann (mriedem) wrote :

I guess I always assumed most people running the vcenter driver are also running with neutron.

Changed in nova:
status: New → Confirmed
tags: added: network
summary: - VMware: nova-compute creates a port group only on one ESXi in cluster in
+ VMware: nova-network creates a port group only on one ESXi in cluster in
case with VlanManager
Revision history for this message
Matt Riedemann (mriedem) wrote :

I guess both nova-network and neutron are officially supported:

http://docs.openstack.org/kilo/config-reference/content/vmware.html#VMware_networking

But I'd think the neutron vmware plugin would work best:

http://docs.openstack.org/kilo/config-reference/content/networking-plugin-vmware.html

Revision history for this message
Matt Riedemann (mriedem) wrote :

Per this doc:

http://docs.openstack.org/kilo/config-reference/content/vmware.html#VMware_networking

"The nova-network service with the VlanManager. Set the vlan_interface configuration option to match the ESX host interface that handles VLAN-tagged VM traffic."

What is your value for the "vlan_interface" config option in nova.conf? Maybe you have a configuration issue here.

Changed in nova:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.