I would like to understand that too. When I was testing, in some cases, a 16 GB node were with no instance while a 2 GB host ran 3 or 4 instances. And, new instances were to the 2 GB node, even all the nodes 'smiling'.
Thanks! On Wed, Nov 9, 2011 at 1:14 PM, Razique Mahroua <razique.mahr...@gmail.com>wrote: > 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.mahr...@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@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > -- - MSc. Correa, J.L.
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
