Re: [Openstack] unexpected distribution of compute instances in queens

> > > 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: [Openstack] unexpected distribution of compute instances in queens

> > > 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

Re: [Openstack] unexpected distribution of compute instances in queens

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,

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

> > > \o/ - care to add the links on the doc? Would be really helpful for > others I guess :). > Doc? What doc? -- MC __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [tripleo][tripleoclient] No more global sudo for "stack" on the undercloud

> > > > In regards to your suggested positions within python code such as the > > client, its worth looking at oslo.privsep [1] where a decorator can be > > used for when needing to setuid. > > hmm yep, have to understand how to use it - its doc is.. well. kind of > sparse. Would be good to get

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

Hi OSA peeps. I apologise in advance for what may seem like an impertinent question. And for those playing along at home, I was just getting the hang of contributing to OSA when last year my employer decided that some of us were no longer needed, and OpenStack lost quite a few full time employed

Re: [openstack-dev] [openstack-ansible][security] Rename openstack-ansible-security role?

I think that a rename is a good idea. Ansible-host-security, Ansible-host-hardening, Ansible-server-security, etc... all good options. -- MC __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

On Sat, Jan 28, 2017 at 1:29 AM, Alexandra Settle wrote: > Hi OpenStack-Ansible team, > > > > I would like to propose Amy Marrich for the core team for > OpenStack-Ansible. > > > +1I wholeheartedly agree. -- MC

Re: [openstack-dev] [all] Using \ for multiline statements

I note that it was rejected as PEP-3125 back in 2007: https://www.python.org/dev/peps/pep-3125/ -- MC __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [openstack-ansible] Debugging slow Xenial gate

Major, I bounced this off my 'distro differences' goto guy, Chris Smart. Here are his thoughts: "Run the 14.04 kernel on 16.04 system and re-run the tests to see if it's kernel related. If 16.04 userland with 14.04 kernel is as fast as Ubuntu 14.04, then compare the kernel .config files to see

Re: [openstack-dev] Project mascots update

On Thu, Aug 4, 2016 at 4:26 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > It would be really awesome if, in true OSt and OSS spirit this work > happened in an OpenStack repository with an open, text based format like > SVG. This way people could contribute and review. > >

Re: [openstack-dev] [Openstack] Naming polls - and some issues

On Thu, Jul 14, 2016 at 9:35 PM, Neil Jerram wrote: > Not sure what the problem would be with 'Quay' or 'Street' - they both > sound like good options to me. > A possible issue with 'Quay' is that it's pronounced 'Key' which may case phonetic confusion wherein it's mistaken for

Re: [openstack-dev] [Aodh] Ordering Alarm severity on context

Hi Sanjana and welcome to openstack-dev. Having sent all of us your 'Hitachi1' password, you may want to change that. :) In general, fishing for code reviews via the openstack-dev mailing list is a poor strategy. You may be better served by discovering the preferred communication channel(s) for

Re: [openstack-dev] How to add a periodic check for typos?

So since requirements usually has an 's' on the end, would you make my cheque for $1.00 payable to the Campaign Against Smog Hazard please? Just use our initials. -- MC __ OpenStack Development Mailing List (not for usage