Hi Huang: You can use the simple scheduler, allocates new instances to hosts that have the fewest instances currently running.
--scheduler_driver=nova.scheduler.simple.SimpleScheduler More sophisticated schedulers are currently under active development, but they haven't made it to the trunk yet. Take care, Lorin -- Lorin Hochstein, Computer Scientist USC Information Sciences Institute 703.812.3710 http://www.east.isi.edu/~lorin On May 23, 2011, at 10:00 PM, Huang Zhiteng wrote: > Hi all, > > In my setup of Cactus, I found Nova scheduler would place newly created > instance to a compute node that is already full occupied (in terms of memory > or # of virtual processors), which lead to swapping and VP overcommitting. > That would cause serious performance issue on a busy environment. So I was > wondering if there's some kinda mechanism to limit to resource one compute > node could use, something like the 'weight' in OpenNebula. > > I'm using Cactus (with GridDynamic's RHEL package), default scheduler policy, > one zone only. > > Any suggestion? > -- > Regards > Huang Zhiteng > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
