Open Stack

Hi Razique,

Did you synchronize clock of all the servers?

I saw similar issue when clock of nova servers were not synchronized well.
In this case, compute nodes are recognized as down and up (smiley) in turn
repeatedly.

Setting up an NTP server is a good idea, and please check using ntpq command
if all nova nodes are synchronized.

Regards,
Masanori

From: Razique Mahroua <razique.mahroua at gmail.com>
Subject: Re: [Openstack] Four compute-node, everytime the 1st and 2nd are choosen
Date: Wed, 9 Nov 2011 16:14:35 +0100

> Hi Akira, 
> I did, 4 nodes are here, up and smiling :-)
> Like I said, I explicitly disable the first three nodes in order to force the scheduler, and it worked ; the last node was choosen for the new instance I spawned, without any issue.
> 
> 
> 
> Le 9 nov. 2011 à 16:03, Akira Yoshiyama a écrit :
> 
> > Hi,
> > 
> > Did you try "nova-manage --flagfile=/etc/nova/nova.conf service list"?
> > 
> > Regards,
> > Akira Yoshiyama
> > 
> > 2011/11/09 18:52 "Razique Mahroua" <razique.mahroua at gmail.com>:
> > Hl all,
> > I've four compute-nodes, around 20 instances runing.
> > I've four nodes registered to nova-scheduler (nova-manage shows them)
> > but everytime I spawn a new instance, the 3rd an 4th node are never choosen for the instances.
> > the ressources are the same on the nodes (around 24gb of ram), they are idle, and available.
> > Can I force the scheduler to use them for an instance ?
> > Thanks
> > Razique - doc team -
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack at lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>