Re: [Openstack-operators] Managing quota for Nova local storage?

Thx for your stories, I think we are now all doing pretty much the same thing to get around the issue but it still looks like a very useful feature. So to share what we (eBay-ECG) are doing: We also started out with scaling the flavor disksize to either memory or cpu. (so e.g. large disk ==

Re: [Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

I tried switching the OS_TENANT_NAME for OS_PROJECT_NAME as a quick test , it didn't seem to fix it. However, I'll generate the openrc file from the class in openstack_extras just to make sure it's 100% correct, and report back. Cheers, Just On 10 November 2016 at 17:43, Alex Schultz

Re: [Openstack-operators] [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

I've added my blog to the OpenStack blog feed and I've published a post about switching/upgrading to Fernet [0]. I'm not sure when it will propagate to the OpenStack blog, but I published it yesterday. Hopefully this helps! [0]

Re: [Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

On Thu, Nov 10, 2016 at 10:28 AM, Justin Cattle wrote: > Hi Alex, > > > Thanks very much for the response. > > We're using python-openstackclient-2.3.0-2~cloud0, which is from ubuntu > cloud archive, trusty-updates/mitaka/main. > > What's the minimum version I need do you think? >

Re: [Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

Hi Alex, Thanks very much for the response. We're using python-openstackclient-2.3.0-2~cloud0, which is from ubuntu cloud archive, trusty-updates/mitaka/main. What's the minimum version I need do you think? Actually we haven't been using puppet-openstack_extras, but I'll look at that for the

Re: [Openstack-operators] [openstack-dev] [MassivelyDistributed] bi-weekly meeting - Timeslot - 15 UTC Wednesday (odd week)

Thanks Thierry @all: Massively distributed IRC meetings every Wednesday (odd week) at 15:00 UTC The first official meeting will be on Wednesday November, the 23rd. The agenda is available at https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2016 ++ ad_rien_ - Mail

Re: [Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

Hey Justin, On Thu, Nov 10, 2016 at 8:48 AM, Justin Cattle wrote: > Hi, > > > I was looking at this class in the keystone module: > > keystone::disable_admin_token_auth > > ..which suggests: > > # After this class is run, > # future puppet runs must have an openrc file with

Re: [Openstack-operators] Managing quota for Nova local storage?

This is what we have done as well. We made our flavors stackable, starting with our average deployed flavor size and making things a multiple of that. IE if our average deployed flavor size is 8GB 120GB of disk, our larger flavors are multiple of that. So if 16GB 240GB of disk is the

Re: [Openstack-operators] Managing quota for Nova local storage?

We didn't come up with one. RAM on our HVs is the limiting factor since we don't run with memory overcommit, so the ability of people to run an HV out of disk space ended up being moot. ¯\_(ツ)_/¯ Long term we would like to switch to being exclusively RBD-backed and get rid of local storage

[Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

Hi, I was looking at this class in the keystone module: keystone::disable_admin_token_auth ..which suggests: # After this class is run, # future puppet runs must have an openrc file with valid keystone v3 # admin credentials in /root/openrc available So when I change the openrc file from

Re: [Openstack-operators] Properties missing in Nova Scheduler Filter

Mario, If I remember right I had a similar issue with getting image_props when I was doing this to pull in custom properties. Through some trial and error and poking around with pdb I ended up with this: image_props = spec_obj.get('request_spec', {}).\ get('image',

Re: [Openstack-operators] [openstack-dev] Mirantis Fuel 9.1 slave node UEFI mode

Hi, you should use openstack or openstack-operators mailing list or ask.openstack.org [1] indicates that UEFI support in Fuel is not yet there. But I think your HW/BIOS/RAID vendor should allow configuration of RAID for Legacy mode as well. BR, Konstantin [1]

Re: [Openstack-operators] _member_ role clarification

Thanks all for the responses. I have seen both of those threads already, but I wasn't 100% sure what I was seeing was a design change or a bug. For now I've added a "me too" to the keystone bug and I'll see what the response is. Thanks. Cheers, Just On 9 November 2016 at 13:18, Mohammed