openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #18072
Re: Scheduler issues in folsom
On Wed, Oct 31, 2012 at 3:53 PM, Vishvananda Ishaya
<vishvananda@xxxxxxxxx>wrote:
>
> On Oct 31, 2012, at 12:25 PM, Jonathan Proulx <jon@xxxxxxxxxxxxx> wrote:
> >
> > again despite:
> > scheduler_available_filters=nova.scheduler.filters.standard_filters
> >
> scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilter,RetryFilter
> > cpu_allocation_ratio=1.0
> > ram_allocation_ratio=1.0
>
> Is this set on both the scheduler and compute nodes?
>
I'd only been pushing these options to the host the scheduler runs on, is
it that simple? I'm delight if I'm an an idiot and just need a few line
in a config file, but puzzled why this was (seemingly at least) working
with Essex, certainly my users didn't start screaming till I dropped Folsom
on them...
-Jon
Follow ups
References
-
Scheduler issues in folsom
From: Jonathan Proulx, 2012-10-30
-
Re: Scheduler issues in folsom
From: Vishvananda Ishaya, 2012-10-30
-
Re: Scheduler issues in folsom
From: Huang Zhiteng, 2012-10-31
-
Re: Scheduler issues in folsom
From: Vishvananda Ishaya, 2012-10-31
-
Re: Scheduler issues in folsom
From: Huang Zhiteng, 2012-10-31
-
Re: Scheduler issues in folsom
From: Daniel P. Berrange, 2012-10-31
-
Re: Scheduler issues in folsom
From: Jonathan Proulx, 2012-10-31
-
Re: Scheduler issues in folsom
From: Huang Zhiteng, 2012-10-31
-
Re: Scheduler issues in folsom
From: Jonathan Proulx, 2012-10-31
-
Re: Scheduler issues in folsom
From: Vishvananda Ishaya, 2012-10-31