<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Akira, <div>I did, 4 nodes are here, up and smiling :-)</div><div>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.</div><div><br></div><div><br></div><div><br><div><div>Le 9 nov. 2011 à 16:03, Akira Yoshiyama a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Hi,</p><p>Did you try "nova-manage --flagfile=/etc/nova/nova.conf service list"?</p><p>Regards,<br>
Akira Yoshiyama</p>
<div class="gmail_quote">2011/11/09 18:52 "Razique Mahroua" <<a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hl all,<br>
I've four compute-nodes, around 20 instances runing.<br>
I've four nodes registered to nova-scheduler (nova-manage shows them)<br>
but everytime I spawn a new instance, the 3rd an 4th node are never choosen for the instances.<br>
the ressources are the same on the nodes (around 24gb of ram), they are idle, and available.<br>
Can I force the scheduler to use them for an instance ?<br>
Thanks<br>
Razique - doc team -<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote></div>
</blockquote></div><br></div></body></html>