Revision history [back]

click to hide/show revision 1
initial version

Openstack KILO : Scheduling of VMs based on availability zone is not working properly

Hello friends,

I have openstack KILO cluster configured with 3 availability zones 1. KVM 2.KVM-DPDK & 3. vmware1-az.

Tried booting VM from both horizon web-ui as well as from the nova command-line client. In both cases i am observing that VM scheduling is not happening properly i.e when i specified AZ as KVM the VM actually started booting on vmware1-az AZ (on ESXI) and vice versa. Same with the case is KVM-DPDK AZ. This doesn't happen all the time, sometime things work as expected but the behavior is not predictable.

Any known bugs in KILO or am i missing any configuration option ? Any specific log message i need to look for ?

Thanks in advance for the help.

Regards, Vivek

My availability-zone-list as displayed by nova command:

root@b7s16:/var/log/nova# nova availability-zone-list +-----------------------+----------------------------------------+ | Name | Status | +-----------------------+----------------------------------------+ | internal | available | | |- b7s16 | | | | |- nova-conductor | enabled :-) 2016-05-11T04:03:48.000000 | | | |- nova-scheduler | enabled :-) 2016-05-11T04:04:02.000000 | | | |- nova-consoleauth | enabled :-) 2016-05-11T04:03:55.000000 | | | |- nova-console | enabled :-) 2016-05-11T04:04:02.000000 | | |- b7s17 | | | | |- nova-conductor | enabled :-) 2016-05-11T04:03:53.000000 | | | |- nova-scheduler | enabled :-) 2016-05-11T04:03:55.000000 | | | |- nova-consoleauth | enabled :-) 2016-05-11T04:03:53.000000 | | | |- nova-console | enabled :-) 2016-05-11T04:03:54.000000 | | |- b7s18 | | | | |- nova-conductor | enabled :-) 2016-05-11T04:03:53.000000 | | | |- nova-scheduler | enabled :-) 2016-05-11T04:03:54.000000 | | | |- nova-consoleauth | enabled :-) 2016-05-11T04:03:53.000000 | | | |- nova-console | enabled :-) 2016-05-11T04:03:53.000000 | | KVM | available | | |- b7s12 | | | | |- nova-compute | enabled :-) 2016-05-11T04:03:48.000000 | | |- b7s13 | | | | |- nova-compute | enabled :-) 2016-05-11T04:03:58.000000 | | KVM-DPDK | available | | |- b7s14 | | | | |- nova-compute | enabled :-) 2016-05-11T04:03:56.000000 | | |- b7s6 | | | | |- nova-compute | enabled :-) 2016-05-11T04:04:00.000000 | | vmware1-az | available | | |- b7s7 | | | | |- nova-compute | enabled :-) 2016-05-11T04:03:59.000000 | +-----------------------+----------------------------------------+ root@b7s16:/var/log/nova#

Openstack KILO : Scheduling of VMs based on availability zone is not working properly

Hello friends,

I have openstack KILO cluster configured with 3 availability zones 1. KVM 2.KVM-DPDK & 3. vmware1-az.

Tried booting VM from both horizon web-ui as well as from the nova command-line client. In both cases i am observing that VM scheduling is not happening properly i.e when i specified AZ as KVM the VM actually started booting on vmware1-az AZ (on ESXI) and vice versa. Same with the case is KVM-DPDK AZ. This doesn't happen all the time, sometime things work as expected but the behavior is not predictable.

Any known bugs in KILO or am i missing any configuration option ? Any specific log message i need to look for ?

Thanks in advance for the help.

Regards, Vivek

My availability-zone-list as displayed by nova command:

root@b7s16:/var/log/nova# nova availability-zone-list
+-----------------------+----------------------------------------+
| Name                  | Status                                 |
+-----------------------+----------------------------------------+
| internal              | available                              |
| |- b7s16              |                                        |
| | |- nova-conductor   | enabled :-) 2016-05-11T04:03:48.000000 |
| | |- nova-scheduler   | enabled :-) 2016-05-11T04:04:02.000000 |
| | |- nova-consoleauth | enabled :-) 2016-05-11T04:03:55.000000 |
| | |- nova-console     | enabled :-) 2016-05-11T04:04:02.000000 |
| |- b7s17              |                                        |
| | |- nova-conductor   | enabled :-) 2016-05-11T04:03:53.000000 |
| | |- nova-scheduler   | enabled :-) 2016-05-11T04:03:55.000000 |
| | |- nova-consoleauth | enabled :-) 2016-05-11T04:03:53.000000 |
| | |- nova-console     | enabled :-) 2016-05-11T04:03:54.000000 |
| |- b7s18              |                                        |
| | |- nova-conductor   | enabled :-) 2016-05-11T04:03:53.000000 |
| | |- nova-scheduler   | enabled :-) 2016-05-11T04:03:54.000000 |
| | |- nova-consoleauth | enabled :-) 2016-05-11T04:03:53.000000 |
| | |- nova-console     | enabled :-) 2016-05-11T04:03:53.000000 |
| KVM                   | available                              |
| |- b7s12              |                                        |
| | |- nova-compute     | enabled :-) 2016-05-11T04:03:48.000000 |
| |- b7s13              |                                        |
| | |- nova-compute     | enabled :-) 2016-05-11T04:03:58.000000 |
| KVM-DPDK              | available                              |
| |- b7s14              |                                        |
| | |- nova-compute     | enabled :-) 2016-05-11T04:03:56.000000 |
| |- b7s6               |                                        |
| | |- nova-compute     | enabled :-) 2016-05-11T04:04:00.000000 |
| vmware1-az            | available                              |
| |- b7s7               |                                        |
| | |- nova-compute     | enabled :-) 2016-05-11T04:03:59.000000 |
+-----------------------+----------------------------------------+
root@b7s16:/var/log/nova#

root@b7s16:/var/log/nova#