>
>
> Presuming you are deploying Rocky or Queens,
>
Yep, it's Queens.
>
> It goes in the nova.conf file under the [placement] section:
>
> randomize_allocation_candidates = true
>
In triple-o land it seems like the config may need to be somewhere like
nova-scheduler.yaml and laid down via a re
>
>
> Have you set the placement_randomize_allocation_candidates CONF option
> and are still seeing the packing behaviour?
>
>
No I haven't. Where would be the place to do that? In a nova.conf somewhere
that the nova-scheduler containers on the controller hosts could pick it up?
Just about to depl
I'm seeing a similar issue in Queens deployed via tripleo.
Two x86 compute nodes and one ppc64le node and host aggregates for virtual
instances and baremetal (x86) instances. Baremetal on x86 is working fine.
All VMs get deployed to compute-0. I can live migrate VMs to compute-1 and
all is well,
