[Openstack-operators] Multiple Nova Schedulers causing failures of VM spawns
Aydelott, Ryan M.
ryade at mcs.anl.gov
Wed Mar 12 17:34:11 UTC 2014
Sure enough - that’s what it was - turns out things were not consistent and there was an egregrious typo leaving the ’s’ off of scheduler in nova.conf. I would have hoped that some config sanity check would have caught this at startup, is there any such command one can use to verify nova.config?
If not - perhaps a programmatic way to do so might be useful.
On Mar 12, 2014, at 12:28 AM, Allamaraju, Subbu <subbu at subbu.org> wrote:
> Perhaps there is some configuration issue. It is a common pattern to use multiple scheduler instances.
> On Mar 11, 2014, at 3:12 PM, Aydelott, Ryan M. <ryade at mcs.anl.gov> wrote:
>> We are running 3 nova schedulers against a rabbitmq cluster of 3, it would appear that only 1 of every three requests to boot a vm fail. Stopping two of the three schedulers brings us back to 100% spawn rate, whereas with all three it goes:
>> Is this something that is a known good configuration to use, or should we be trying something else here (HA/VIP’s). Perhaps I’m missing something obvious as well?
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the OpenStack-operators