VMware: nova-network creates a port group only on one ESXi in cluster in case with VlanManager
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.
ii nova-cert 1:2015.
ii nova-common 1:2015.
ii nova-compute 1:2015.
ii nova-compute-kvm 1:2015.
ii nova-conductor 1:2015.
ii nova-consoleauth 1:2015.
ii nova-consoleproxy 1:2015.
ii nova-network 1:2015.
ii nova-objectstore 1:2015.
ii nova-scheduler 1:2015.
ii python-nova 1:2015.
ii python-novaclient 1:2.23.
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: | added: vmware |
I guess I always assumed most people running the vcenter driver are also running with neutron.