Open Stack

On Wed, 5 Dec 2018, Mike Carden wrote:

> On Tue, Dec 4, 2018 at 9:58 PM Chris Dent <cdent+os at anticdent.org> wrote:
>
>>
>> * The 'randomize_allocation_candidates' config setting is used by
>>    the placement-api process (probably called nova-placement-api in
>>    queens), not the nova-scheduler process, so you need to update the
>>    config (in the placement section) for the former and restart it.
>
> I tried the same thing in the nova.conf of the nova_placement containers
> and still no joy.

Darn.

> A check on a fresh deploy of Queens with just a couple of x86 compute nodes
> proves that it can work without randomize_allocation_candidates being set
> to True. Out of the box we get an even distribution of VMs across compute
> nodes. It seems that somewhere along the path of adding Ironic and some
> baremetal nodes and host aggregates and a PPC64LE node, the scheduling goes
> awry.

Yeah, this sort of stuff is why I was hoping we could see some of
your logs, to figure out which of those things was the haymaker.

If you figure it out, please post about it.

-- 
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent