From jaypipes at gmail.com Mon Dec 3 13:59:13 2018 From: jaypipes at gmail.com (Jay Pipes) Date: Mon, 3 Dec 2018 08:59:13 -0500 Subject: [Openstack] unexpected distribution of compute instances in queens In-Reply-To: References: <815799a8-c2d1-39b4-ba4a-8cc0f0d7b5cf@gmail.com> Message-ID: On 11/30/2018 05:52 PM, Mike Carden wrote: > > 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 deploy for realz with about forty x86 compute nodes, so it > would be really nice to sort this first. :) Presuming you are deploying Rocky or Queens, It goes in the nova.conf file under the [placement] section: randomize_allocation_candidates = true The nova.conf file should be the one used by nova-scheduler. Best, -jay From mike.carden at gmail.com Mon Dec 3 20:43:04 2018 From: mike.carden at gmail.com (Mike Carden) Date: Tue, 4 Dec 2018 07:43:04 +1100 Subject: [Openstack] unexpected distribution of compute instances in queens In-Reply-To: References: <815799a8-c2d1-39b4-ba4a-8cc0f0d7b5cf@gmail.com> Message-ID: > > > 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-deploy. Or something. The nova_scheduler runs in a container on a 'controller' host. -- MC -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Mon Dec 3 23:53:36 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 3 Dec 2018 23:53:36 +0000 Subject: [Openstack] IMPORTANT: This list is retired Message-ID: <20181203235336.xajrwmycuov2w2jr@yuggoth.org> This mailing list was replaced by a new openstack-discuss at lists.openstack.org mailing list[0] as of Monday November 19, 2018 and starting now will no longer receive any new messages. The archive of prior messages will remain published in the expected location indefinitely for future reference. For convenience posts to the old list address will be rerouted to the new list for an indeterminate period of time, but please correct it in your replies if you notice this. See my original notice[1] (and the many reminders sent in months since) for an explanation of this change. [0] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [1] http://lists.openstack.org/pipermail/openstack/2018-September/047005.html -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: