Are you using Diablo or Trunk?

If you're using trunk the default scheduler is MultiScheduler, which uses 
Chance scheduler. I think Diablo uses Chance by default?


Unless you've explicitly selected the LeastCostScheduler (which only exists in 
Diablo now) I wouldn't worry about those settings.

Did you explicitly define a scheduler to use?

[] on behalf of 
Jorge Luiz Correa []
Sent: Thursday, November 10, 2011 6:27 AM
Subject: Re: [Openstack] Four compute-node, everytime the 1st and 2nd are 

Is there a flag in nova.conf that permits we configure that? In documentation 
we can see that exists some algorithms used by scheduler. But, I don't know how 
to choose that one best fit our requirements.


On Wed, Nov 9, 2011 at 1:36 PM, Ed Leafe 
<<>> wrote:
On Nov 9, 2011, at 7:51 AM, Razique Mahroua wrote:

> I use the default scheduler, in fact, I've never tunned it really.
> The hypervisors all run KVM

       This is where the flag is defined in<>:

 32 FLAGS = flags.FLAGS
 33 flags.DEFINE_list('least_cost_functions',
 34         ['nova.scheduler.least_cost.compute_fill_first_cost_fn'],
 35         'Which cost functions the LeastCostScheduler should use.')

       Since the default weighting function is 'compute_fill_first_cost_fn', 
which, as its name suggests, chooses hosts so as to fill up one host as much as 
possible before selecting another, the pattern you're seeing is expected. If 
you change that flag to 'nova.scheduler.noop_cost_fn', you should see the hosts 
selected randomly. The idea is that you can create your own weighting functions 
that will select potential hosts in a way that best fits your needs.

-- Ed Leafe

Mailing list:
Post to     :<>
Unsubscribe :
More help   :

- MSc. Correa, J.L.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to