[Openstack-operators] mysql crash during Juno upgrade when using Galera

We were remiss for not mentioning this during our talk on Monday since apparently its happening to other folks as I found out last night at dinner. During the Juno database migrations we saw mysql crash. This ended up delaying our move to Juno by a few weeks while the bug was being worked. There

[Openstack-operators] Operators Summit: Packaging

Greeting Operators: I have been given the honor or moderating the packaging session at the operators meet-up next week. I think that this could be a big and interesting topic. I know many of us are rolling our own packages and we’ve had discussions on what can be done to avoid everyone having t

Re: [Openstack-operators] Rolling upgrades and Neutron

We did this for our I to J move. Control nodes first, setting the nova compat flag, then compute nodes, then removing the flag. Things worked along the way but when the compat flag was set live-migration was disabled (by nova). Our larger concerns were dealing with a clustered DB that was being up

Re: [Openstack-operators] Migrating keystone from MySQL to LDAP

What are you going to use LDAP for? Identity/Assignment/both? Do you have unfettered write access into your LDAP? We use a hybrid driver that will auth against mySQL and LDAP so we can setup service accounts (like nova, neutron, etc). AFAIK LDAP Assignment is being deprecated because nobody uses

Re: [Openstack-operators] cinder v2 and cinder-client

On 2/24/15, 12:54 PM, "Jesse Keating" wrote: >On 2/23/15 8:13 PM, Fischer, Matt wrote: >> What does everyone else do here? > >I've been trying to get this to work as well. I thought I had it going >with just putting the v2 path into the volume endpoint url,

Re: [Openstack-operators] cinder v2 and cinder-client

ent? On Monday, February 23, 2015, Fischer, Matt mailto:matthew.fisc...@twcable.com>> wrote: I’m in the process of trying to cleanup all the deprecations we have after moving some services in Juno. One I have outstanding is this warning about cinder. "The v1 api is deprecated and will be re

[Openstack-operators] cinder v2 and cinder-client

I’m in the process of trying to cleanup all the deprecations we have after moving some services in Juno. One I have outstanding is this warning about cinder. "The v1 api is deprecated and will be removed after the Juno release. You should set enable_v1_api=false and enable_v2_api=true in your c

Re: [Openstack-operators] Voting for entries in OpenStack Vancouver Summit

I don’t know if we have an official policy but I’d like to avoid everyone announcing all their talks on here unless it’s in response to a specific question or thread. The talks already all over social media and I know we all have talks to try and get votes for so let’s just avoid the arms race o

Re: [Openstack-operators] [Keystone] Deprecation of Eventlet deployment in Kilo (Removal for "M"-release)

Nevermind, I re-read it and missed the M portion of dropped. Sorry for the confusion. I have opened a puppet bug for this so we can switch the default value, it’s still eventlet. https://bugs.launchpad.net/puppet-keystone/+bug/1423685 From: , Matt Fischer mailto:matthew.fisc...@twcable.com>>

Re: [Openstack-operators] [Keystone] Deprecation of Eventlet deployment in Kilo (Removal for "M"-release)

Can you clarify if the feature is being deprecated – as in still usable but not recommended with a warning, or dropped, as-in, won’t work at all? You mention both in the first two sentences. From: Morgan Fainberg mailto:morgan.fainb...@gmail.com>> Date: Thursday, February 19, 2015 at 12:32 PM T

Re: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea?

From: Morgan Fainberg mailto:morgan.fainb...@gmail.com>> Date: Thursday, January 29, 2015 at 12:26 PM To: openstack-operators mailto:openstack-operators@lists.openstack.org>> Subject: [Openstack-operators] [all] SQL Schema Downgrades: A Good Idea? >From an operator perspective I wanted to get i

Re: [Openstack-operators] Packaging sample config versions

On 1/28/15, 4:45 PM, "Mathieu Gagné" wrote: >On 2015-01-28 6:30 PM, Tom Fifield wrote: >> On 29/01/15 07:28, Thomas Goirand wrote: >>> On 01/27/2015 11:00 PM, Tom Fifield wrote: Hi all, Based on Gustavo's excellent work below, talking with many ops, and after a brief chats wit

Re: [Openstack-operators] [openstack-dev][openstack-operators]flush expired tokens and moves deleted instance

On 1/27/15, 10:21 AM, "gustavo panizzo (gfa)" wrote: > > >On 01/28/2015 01:13 AM, Fischer, Matt wrote: >> Our keystone database is clustered across regions, so we have this job >> running on node1 in each site on alternating hours. I don¹t think you¹d >> wan

Re: [Openstack-operators] [openstack-dev][openstack-operators]flush expired tokens and moves deleted instance

Our keystone database is clustered across regions, so we have this job running on node1 in each site on alternating hours. I don’t think you’d want a bunch of cron jobs firing off all at once to cleanup tokens on multiple clustered nodes. That’s one reason I know not to put this in the code. Ar

Re: [Openstack-operators] How to allow users to list services by modifying the policy.json file of Keystone

On 1/26/15, 8:46 AM, "Christian Berendt" wrote: >On 01/26/2015 04:02 PM, Fischer, Matt wrote: >> Is there any reason that the user can¹t just run keystone catalog which >> does not require admin permissions? > >Matt, this is just an example. We tried it with di

Re: [Openstack-operators] How to allow users to list services by modifying the policy.json file of Keystone

Is there any reason that the user can¹t just run keystone catalog which does not require admin permissions? On 1/26/15, 4:58 AM, "Christian Berendt" wrote: >Hello. > >We have an user 'user1' in the tenant 'tenant1' with the assigned role >'_member_'. > >We want to be able to list services with t

[Openstack-operators] no meeting this week

Michael and I agreed that we’ll skip the Operators meeting this week and let everyone focus on working on topics for the mid-cycle meetup in March: https://etherpad.openstack.org/p/PHL-ops-meetup I’d also invite anyone to reply to the discussion on sample configs which was sent before the holid

[Openstack-operators] Operators meeting - Wednesday Jan 7

As a reminder the next operators meeting is on Wednesday Jan 7 at 1800 UTC in #openstack-meeting-4. The agenda is here: https://etherpad.openstack.org/p/openstack-operators-meeting-070115-agenda As I suspect not much has happened on previous actions, the main discussion will likely be around t

[Openstack-operators] meeting tomorrow @ 1800 UTC

Our first official meeting is tomorrow Dec 17 at 1800 UTC in the #openstack-meeting-4 channel. The agenda is here: https://etherpad.openstack.org/p/openstack-operators-meeting-171214-agenda I think that this will also be our last meeting of 2014, so see you there. (sorry for the corporate junk

Re: [Openstack-operators] Packaging sample config versions

ct: Re: [Openstack-operators] Packaging sample config versions On Wed, Dec 10, 2014 at 11:16 AM, Fischer, Matt mailto:matthew.fisc...@twcable.com>> wrote: From: Anne Gentle mailto:a...@openstack.org>> Date: Wednesday, December 10, 2014 at 8:41 AM To: Michael Dorman mailto:mdor

Re: [Openstack-operators] Packaging sample config versions

From: Anne Gentle mailto:a...@openstack.org>> Date: Wednesday, December 10, 2014 at 8:41 AM To: Michael Dorman mailto:mdor...@godaddy.com>> Cc: "openstack-operators@lists.openstack.org" mailto:openstack-operators@lists.openstack.org>> Subject: Re

Re: [Openstack-operators] Weekly Irc meeting?

I’ve started some work on the agenda in the ether pad. Feel free to promote or demote topics. Two areas that I know are under active discussion are the sample config files or lack thereof and ansible mysql upgrades and I’d also like to talk about the mailing list some. Feel free to add or modif

Re: [Openstack-operators] Packaging sample config versions

>> >> I do know that some projects, like nova and cinder, still ship the file. > >Cinder I believe just kicked that out (for better or worse), > >https://github.com/openstack/cinder/commit/62a72a7574b18f7 > >One less. I don't think nova does either anymore... > Oops I meant keystone! Nova was one

Re: [Openstack-operators] Packaging sample config versions

I also find this issue really really annoying. Not only is the sample config a useful reference, but having it in a git repo allows me to see when new options were added or defaults were changed. Otherwise you have to rely on the docs which are generally wrong. When I was looking at some of the

[Openstack-operators] RabbitMQ TTL/queue configuration

What RabbitMQ optimizations are people making with respect to OpenStack? We’ve started looking into how we can optimize our rabbit cluster to make it more robust and less resource intensive. One thing that seems to happen is that the number of messages we have slowly grows over time because we h

Re: [Openstack-operators] Wrong URL returned on Keystone /v2.0

Making that call just returns some details on the API version you¹ve selected. It really doesn¹t have anything to do with the catalog URLs. The URL you¹re looking at is a reference to the server who returned you the info. Perhaps it¹s your load balancer if you don¹t recognize the IP? It should eith

Re: [Openstack-operators] Operations project: Packaging

I’m +1 with the time and I agree that we should move to the meetings channel as soon as is feasible. From: Michael Chapman mailto:wop...@gmail.com>> Date: Sunday, November 30, 2014 at 7:38 AM To: "openstack-operators@lists.openstack.org" mailto:o

Re: [Openstack-operators] Proposal for an 'Operations' project

On 11/8/14, 9:10 AM, "Jeremy Stanley" wrote: >On 2014-11-07 22:25:49 +0100 (+0100), Jonathan Proulx wrote: >[...] >> An "Ops Project" feels weird to me. >[...] > >To me as well. Perhaps this is the "operator community" coming to >the realization that they don't need to be separate from the >"deve

Re: [Openstack-operators] Keystone error

I don’t know what OS you have since you didn’t mention but I think you are missing a package. On Ubuntu it would be python-oslo.config. From: "mo...@qmail.com.bd" mailto:mo...@qmail.com.bd>> Date: Sunday, October 26, 2014 at 2:28 AM To: "openstack-operators@lists.open

Re: [Openstack-operators] Nodes and configurations management in Puppet

On 9/25/14 7:40 AM, "Mathieu Gagné" wrote: >Hi, > >Some of you use Puppet to manage your OpenStack infrastructure. > >- How do you manage your node definitions? > Do you have an external ENC? > Or plain site.pp, Puppet Enterprise, theforeman, etc. ? We manage node definitions using hostnam