[Openstack] unexpected distribution of compute instances in queens
Tobias Urdin
tobias.urdin at binero.se
Tue Dec 4 08:38:08 UTC 2018
Started a patch to include that option in puppet-nova as well based on
this thread
which perhaps can help the TripleO based world as well.
https://review.openstack.org/#/c/621593/
Best regards
On 12/04/2018 04:56 AM, Alex Schultz wrote:
> On Mon, Dec 3, 2018 at 7:06 PM Mike Carden <mike.carden at gmail.com> wrote:
>>
>> Having found the nice docs at:
>> https://docs.openstack.org/tripleo-docs/latest/install/containers_deployment/tips_tricks.html
>>
>> I have divined that I can ssh to each controller node and:
>> sudo docker exec -u root nova_scheduler crudini --set /etc/nova/nova.conf placement randomize_allocation_candidates true
>> sudo docker kill -s SIGHUP nova_scheduler
>>
> FYI protip, you can add the following to a custom environment file to
> configure this value (as we don't expose the config by default)
>
> parameters_defaults:
> ControllerExtraConfig:
> nova::config::nova_config:
> placement/randomize_allocation_candidates:
> value: true
>
>
> And then do a deployment. This will persist it and ensure future
> scaling/management updates won't remove this configuration.
>
>
>
>> ...and indeed the /etc/nova/nova.conf in each nova_scheduler container is updated accordingly.
>>
>> Unfortunately, instances are all still launched on compute-0.
>>
>> --
>> MC
>>
>>
>
More information about the openstack-discuss
mailing list