*** catintheroof has joined #openstack-operators | 00:08 | |
*** ducttape_ has joined #openstack-operators | 00:09 | |
*** Apoorva has quit IRC | 00:28 | |
*** liverpooler has quit IRC | 00:46 | |
*** Apoorva has joined #openstack-operators | 01:00 | |
*** piet has quit IRC | 01:04 | |
*** liverpooler has joined #openstack-operators | 01:37 | |
*** mriedem has joined #openstack-operators | 01:38 | |
*** liverpooler has quit IRC | 01:48 | |
*** Apoorva has quit IRC | 02:16 | |
*** catintheroof has quit IRC | 02:16 | |
*** catintheroof has joined #openstack-operators | 02:16 | |
*** catintheroof has quit IRC | 02:20 | |
*** liverpooler has joined #openstack-operators | 02:23 | |
*** liverpooler has quit IRC | 02:37 | |
*** VW has joined #openstack-operators | 02:47 | |
*** sudipto has joined #openstack-operators | 03:01 | |
*** sudipto_ has joined #openstack-operators | 03:01 | |
*** VW has quit IRC | 03:07 | |
*** VW_ has joined #openstack-operators | 03:16 | |
*** catintheroof has joined #openstack-operators | 03:25 | |
*** udesale has joined #openstack-operators | 03:32 | |
stupidnic | Does anybody know if openstack service config files support the ability to include files? | 03:37 |
---|---|---|
stupidnic | I would like to steal a page from debian and do something like /etc/nova/conf.d/ and then have various files in there | 03:37 |
*** armax has quit IRC | 04:16 | |
jlk | not really | 04:20 |
jlk | some do in some various ways, but it's not a general or generic thing | 04:21 |
*** catinthe_ has joined #openstack-operators | 04:23 | |
*** catintheroof has quit IRC | 04:26 | |
*** catinthe_ has quit IRC | 04:26 | |
*** catintheroof has joined #openstack-operators | 04:27 | |
stupidnic | jlk: alright... thanks for the info | 04:27 |
*** catintheroof has quit IRC | 04:27 | |
*** sudipto has quit IRC | 04:59 | |
*** sudipto_ has quit IRC | 04:59 | |
*** ecrehar has joined #openstack-operators | 05:29 | |
*** sudipto has joined #openstack-operators | 05:29 | |
*** sudipto_ has joined #openstack-operators | 05:29 | |
*** VW_ has quit IRC | 06:13 | |
*** saneax-_-|AFK is now known as saneax | 06:42 | |
*** Apoorva has joined #openstack-operators | 06:43 | |
*** Apoorva has quit IRC | 06:46 | |
*** pcaruana has joined #openstack-operators | 07:21 | |
*** simon-AS559 has quit IRC | 07:26 | |
*** makowals has joined #openstack-operators | 07:28 | |
*** simon-AS559 has joined #openstack-operators | 07:42 | |
*** jsheeren has joined #openstack-operators | 07:56 | |
*** jsheeren has quit IRC | 07:56 | |
*** jsheeren has joined #openstack-operators | 08:05 | |
*** matrohon has joined #openstack-operators | 08:08 | |
*** VW has joined #openstack-operators | 08:13 | |
*** rmart04 has joined #openstack-operators | 08:16 | |
*** VW has quit IRC | 08:18 | |
*** beddari has joined #openstack-operators | 08:31 | |
*** ecrehar has quit IRC | 08:45 | |
*** ecrehar has joined #openstack-operators | 08:47 | |
*** paramite has joined #openstack-operators | 08:53 | |
*** rcernin has joined #openstack-operators | 08:56 | |
*** zioproto has joined #openstack-operators | 09:13 | |
*** derekh has joined #openstack-operators | 09:18 | |
*** openstackgerrit has quit IRC | 09:48 | |
*** makowals_ has joined #openstack-operators | 09:48 | |
*** openstackgerrit has joined #openstack-operators | 09:49 | |
*** makowals has quit IRC | 09:51 | |
*** racedo has joined #openstack-operators | 09:52 | |
*** electrofelix has joined #openstack-operators | 09:55 | |
*** racedo has quit IRC | 10:47 | |
*** udesale has quit IRC | 10:58 | |
*** sudipto_ has quit IRC | 11:03 | |
*** sudipto has quit IRC | 11:03 | |
*** catinthe_ has joined #openstack-operators | 12:37 | |
*** jsheeren has quit IRC | 12:47 | |
*** dbecker has joined #openstack-operators | 12:49 | |
zioproto | mfisch: hello Matt, during my upgrade I got stuck into this https://bugs.launchpad.net/puppet-openstacklib/+bug/1612093 | 13:24 |
openstack | Launchpad bug 1612093 in puppet-openstacklib "creating multiple databases with same db username is not possible with puppet-openstacklib" [Wishlist,Confirmed] | 13:24 |
zioproto | mfisch: there is any testing beta patch around for this ? | 13:24 |
zioproto | mfisch: I dont see any openstack review yet, right ? | 13:25 |
*** dtrainor has joined #openstack-operators | 13:39 | |
*** sudipto has joined #openstack-operators | 13:45 | |
*** sudipto_ has joined #openstack-operators | 13:45 | |
*** udesale has joined #openstack-operators | 13:47 | |
*** VW has joined #openstack-operators | 13:57 | |
*** mihalis68 has joined #openstack-operators | 13:58 | |
*** dc_mattj has joined #openstack-operators | 14:00 | |
dc_mattj | afternoon | 14:00 |
mihalis68 | morning | 14:01 |
VW | hola | 14:01 |
mihalis68 | I remembered my action and just sent the email :) | 14:02 |
mihalis68 | dc_mattj will you run the meeting today? | 14:02 |
dc_mattj | yes | 14:02 |
dc_mattj | anyone else here ? | 14:02 |
mihalis68 | no, it's just Matts | 14:03 |
mihalis68 | oh, and me | 14:03 |
mihalis68 | I get the feeling this time of the day isn't working very well | 14:04 |
dc_mattj | ok | 14:04 |
dc_mattj | #startmeeting Ops Meetups Team | 14:04 |
openstack | Meeting started Tue Nov 29 14:04:18 2016 UTC and is due to finish in 60 minutes. The chair is dc_mattj. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:04 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:04 |
openstack | The meeting name has been set to 'ops_meetups_team' | 14:04 |
*** rmart04_ has joined #openstack-operators | 14:04 | |
*** rmart04 has quit IRC | 14:04 | |
*** rmart04_ is now known as rmart04 | 14:04 | |
dc_mattj | Hello all, and welcome to the Ops Meetups Team meeting :) | 14:05 |
dc_mattj | NB: If you're new, or just idling in the channel, be sure to have read: | 14:05 |
dc_mattj | #link https://wiki.openstack.org/wiki/Ops_Meetups_Team | 14:05 |
dc_mattj | for background. | 14:05 |
dc_mattj | Check out our agenda items at: | 14:05 |
dc_mattj | # link https://etherpad.openstack.org/p/ops-meetups-team | 14:05 |
dc_mattj | As always: please write your name down on the agenda etherpad as a way of introduction. | 14:05 |
dc_mattj | Secondly, if there's something else burning to put on the agenda, please add it to that same etherpad. | 14:05 |
dc_mattj | #topic Review of action items from the previous meeting | 14:05 |
dc_mattj | First up, a quick run-through of our action items from the previous meeting. | 14:05 |
dc_mattj | so on our action items from the last meeting, I haven't added the regional meeting discussion for today | 14:06 |
dc_mattj | to be honest I think that needs more of a quorum to discuss | 14:06 |
VW | I would agree | 14:07 |
dc_mattj | I'd vote that we put that back for a face to face, perhaps in Milan ? | 14:07 |
dc_mattj | I do have some updates on Milan - I had a video conference with Mariano from Enter this morning | 14:07 |
VW | That could work - just know you might have a limited perspective there - regionally speaking | 14:07 |
dc_mattj | VW, true | 14:08 |
dc_mattj | we could also put back until the Boston summit | 14:08 |
VW | e.g. - I probably won't make Milan | 14:08 |
dc_mattj | where we would have wider participation | 14:08 |
VW | ideally, we could have some more conversation about it, but yes, I think the OPs Meetup session(s) in Boston should explore it in detail | 14:08 |
dc_mattj | +1 | 14:08 |
dc_mattj | mihalis68, do you have anything else to add to that point or shall we park that for the minute | 14:10 |
dc_mattj | I've made a note on the ether pad | 14:10 |
mihalis68 | Nothing to add | 14:10 |
dc_mattj | ok, so on Milan | 14:10 |
dc_mattj | Mariano and I went through the basics of the logistical stuff | 14:11 |
mihalis68 | how is the venue looking? | 14:11 |
dc_mattj | venue looks good - main room 120+, room 2 30+, room 3 and 4 20ish | 14:11 |
dc_mattj | depending if we need all of them | 14:12 |
mihalis68 | very good | 14:12 |
dc_mattj | you can see some of the space at http://www.coworkinglogin.it/ | 14:12 |
mihalis68 | Do we require the possibility of an all-hands meeting? | 14:12 |
mihalis68 | Just thinking about capping the max attendance | 14:12 |
dc_mattj | when ? | 14:12 |
mihalis68 | in Milan. Is 120 the de facto maximum number of attendees? | 14:13 |
mihalis68 | I'm asking as I don't recall if that's a rule | 14:13 |
zioproto | hello all | 14:13 |
mihalis68 | hello | 14:13 |
dc_mattj | we discussed this previously, with 120 as a guideline IIRC | 14:13 |
dc_mattj | hello zioproto | 14:13 |
dc_mattj | so Enter are finding someone to sit in on these meetings | 14:14 |
mihalis68 | #info 120 is the likely maximum attendance in Milan as it is the size of the biggest room | 14:14 |
*** nemesis-ninux has joined #openstack-operators | 14:14 | |
dc_mattj | I have asked Mariano to get some rough costings for the event, so they can decide how much sponsorship they can carry, and if we need to get additional sponsors | 14:15 |
dc_mattj | that will take them a couple of weeks to do | 14:15 |
dc_mattj | they are happy to handle the logistical side, but have requested that we drive the content and moderators piece | 14:15 |
mihalis68 | right... precisely why a benevolent dictator is needed on that side | 14:16 |
mihalis68 | well done, dc_mattj :) | 14:16 |
dc_mattj | I have explained that is driven via a community process anyway so I don't particularly see any issues with that | 14:16 |
dc_mattj | and I am happy to liaise with them | 14:16 |
zioproto | if Mariano needs a sponsor I can try asking here at SWITCH, but I need to know what kind of cost we are talking about | 14:16 |
dc_mattj | zioproto, great idea | 14:17 |
dc_mattj | when we get the rough costings we will know what sponsorship we need to raise | 14:17 |
*** jamesdenton has joined #openstack-operators | 14:17 | |
dc_mattj | as a guideline, for MCR each sponsor put in around €1000 | 14:17 |
dc_mattj | but smaller or larger amounts are also possible | 14:17 |
mihalis68 | I have no idea if Bloomberg would stump up again, however I know we are strongly considering sponsoring the first PTG, therefore if you cc: me on the costs and "funding gap" I could find out | 14:17 |
zioproto | that should be something I can ask at SWITCH | 14:17 |
*** zul has quit IRC | 14:18 | |
dc_mattj | so lets park this until Enter have done the costings, and can say how much they can contribute | 14:18 |
dc_mattj | then we can work out what additional sponsorship we need | 14:18 |
mrhillsman | o/ | 14:18 |
mrhillsman | sorry i'm tardy | 14:18 |
VW | +1 dc_mattj | 14:19 |
VW | howdy mrhillsman | 14:19 |
mihalis68 | dc_mattj agreed. I can't say officially but I would think Bloomberg could go at least up to the $1k mentioned | 14:19 |
dc_mattj | hi mr | 14:19 |
dc_mattj | hi mrhillsman | 14:19 |
mihalis68 | morning mrhillsman | 14:19 |
dc_mattj | Enter are also going to look at discount hotel rates locally | 14:19 |
mihalis68 | I have now added two things to today's agenda | 14:20 |
mihalis68 | so let's move on | 14:20 |
dc_mattj | I saw | 14:20 |
dc_mattj | so basically on agenda item 2, we are waiting on Enter to provide a liaison person and rough costings | 14:21 |
dc_mattj | anything more on item 2 ? | 14:21 |
zioproto | #agreed we are waiting on Enter to provide a liaison person and rough costings | 14:21 |
dc_mattj | ty :) | 14:21 |
dc_mattj | #topic Follow on from session structure review | 14:22 |
dc_mattj | has anyone got any input on the session analysis I circulated ? | 14:22 |
mihalis68 | nice work pulling all the ether pad links together and roughing out the popular topics | 14:22 |
mihalis68 | I haven't reviewed it more than a brief look, sorry | 14:22 |
zioproto | should we post the link to the google excel doc ? | 14:22 |
mihalis68 | have been away since last meeting, so buried in work | 14:22 |
mihalis68 | https://docs.google.com/spreadsheets/d/1-WEsEmwms2SLyjt2jtCMvpepmiHwoiDkMWMWk37rkRA/edit#gid=0 | 14:22 |
zioproto | #link https://docs.google.com/spreadsheets/d/1-WEsEmwms2SLyjt2jtCMvpepmiHwoiDkMWMWk37rkRA/edit#gid=0 | 14:23 |
VW | I'm still going through it, dc_mattj | 14:23 |
*** vijaykc4 has joined #openstack-operators | 14:23 | |
mihalis68 | my observation is this work will be extremely valuable to the specific milan itinerary work | 14:23 |
*** jamesdenton has quit IRC | 14:23 | |
zioproto | how do we read this ? is the color a topic ? | 14:23 |
dc_mattj | sorry - colours are a bit confusing, just my shorthand for trying to link things together | 14:23 |
zioproto | the idea is to merge those ones on the same color ? | 14:24 |
dc_mattj | bottom of the coloured section is the summary | 14:24 |
dc_mattj | I suggested a couple of the ways we could look at the data in the email I circulated | 14:24 |
zioproto | I think that upgrades, patches and packaging can go together with config management. These two I think should be merged | 14:25 |
dc_mattj | just some food for thought really when we start to do the session planning | 14:26 |
dc_mattj | not really any definitive take aways, but we can definitely pre-load some sessions which come up repeatedly | 14:26 |
dc_mattj | and we also might consider allocating time slots against a 'track' rather than a specific topic, and we can then add to the tracks more fluidly in the run up to the event | 14:27 |
*** ducttape_ has quit IRC | 14:27 | |
zioproto | this makes sense | 14:27 |
zioproto | making the tracks | 14:27 |
mihalis68 | You mention nova, neutron, logging and monitoring as the popular ones. I would add scaling and containerization (two) | 14:27 |
dc_mattj | +1 | 14:27 |
zioproto | +1 | 14:27 |
dc_mattj | those were just examples really | 14:27 |
*** ducttape_ has joined #openstack-operators | 14:27 | |
zioproto | making tracks we make sure that people interested in a specific area dont miss talks that happen in parallel | 14:28 |
dc_mattj | I think there's a set of clearly defined topics, plus a set of fairly clearly defined 'tracks', then we can also reach out to the wider community to fill in content under the 'tracks', and to add any other topics not covered already | 14:28 |
zioproto | +1 | 14:29 |
zioproto | Should we try to make this track skeleton in the Milano etherpad ? | 14:29 |
*** mriedem has quit IRC | 14:29 | |
mrhillsman | #link https://etherpad.openstack.org/p/MIL-ops-meetup | 14:30 |
dc_mattj | I don't have time for the full hour today so I suggest we aim to start populating the Milano ether pad in next weeks meeting ? | 14:30 |
*** jamesdenton has joined #openstack-operators | 14:30 | |
VW | so, I have one higher level meta observation we should keep in the back of our minds when digesting dc_mattj's work and using it for future meetups | 14:31 |
zioproto | okay | 14:31 |
VW | in theory, the structure of the "Ops" stuff is going to change at the forums | 14:31 |
mihalis68 | Tracks seem popular, certainly that seems a good idea, however I think we need some ground rules before people start filling up the ether pad or it will get hopelessly confusing | 14:31 |
*** ducttape_ has quit IRC | 14:31 | |
VW | since sessions will be much more focused on dev and ops together discussing features, needs, etc | 14:32 |
VW | so, that will put a lot of pressure on what the more general topics are at the meetups | 14:32 |
VW | and should force us to push working group time/meetings back to the forum - where the Foundation seems to be taking over the scheduling of that (at least they did in BCN) | 14:32 |
VW | we should follow up on those assumptions | 14:32 |
VW | but the data in this sheet has meetups where all these kinds of activities took place, and it's worth thinking about the fact that some of that focus may shift around from one event type to another | 14:33 |
dc_mattj | ok, lot of unknown unknowns in that area at the minute but I think I follow your logic | 14:33 |
mihalis68 | the forum is the new thing at the summit now that the design summit is no more? | 14:33 |
mihalis68 | the Yin to the PTG Yang? | 14:34 |
dc_mattj | yes | 14:34 |
VW | yes, but, as I understood, it it's a melding of the design and ops summit | 14:35 |
mihalis68 | VW are you suggesting that for Milan we remove things from that meet up that can be done in Boston? | 14:35 |
VW | the $100,000 question is where there still be an Ops "meetup" at the forum | 14:35 |
mihalis68 | Sorry, i'm finding this all hard to follow | 14:35 |
VW | I know - text is hard | 14:35 |
VW | more that we should confirm what the intent is for "ops" activities at the forum | 14:35 |
VW | and then make sure we are maximizing what goes on at the mid-cycles based on that | 14:36 |
VW | in case there aren't opportunities for general sessions in Boston (and beyond) | 14:36 |
dc_mattj | teasing out cross project issues from the ops perspective, which can then inform session schedules at the forum, will be important | 14:36 |
zioproto | so we should avoid WG presentations and updates at the ops meetup, and keep focused on ops discussion, bugs, and features ? But not talking on stuff like update from the XYZ WG .. Did I understand ? | 14:36 |
dc_mattj | and some of that comes out of the more general ops discussions | 14:36 |
VW | I would think so zioproto, but we need to confirm if the Foundation will continue to manage the WGs like they did in BCN | 14:37 |
VW | but I think we decided after NYC, that we can really focus the mid-cycles on topics/discussion | 14:37 |
dc_mattj | agreed | 14:37 |
zioproto | is any operator going also to the PTG in Atlanta ? | 14:38 |
VW | and let the WG/teams meet up at the forums - where they will likely be driving various session topics along with devs | 14:38 |
dc_mattj | zioproto, I think that's our next topic | 14:38 |
mihalis68 | I've added PTG to agenda... I can't see how it makes sense for anyone from my team to attend PTG | 14:38 |
dc_mattj | anything else on this topic ? | 14:38 |
VW | none for this one, dc_mattj | 14:38 |
VW | sorry if I confused | 14:38 |
dc_mattj | no, important input | 14:38 |
mihalis68 | I think I agree but I would need a clearer statement to be sure, honestly | 14:38 |
dc_mattj | and it is somewhat confusing | 14:38 |
dc_mattj | until we do one cycle I don't think it will get less confusing | 14:39 |
mihalis68 | I was confused before BCN, and also after BCN | 14:39 |
mihalis68 | maybe having only one person from Bloomberg Engineering attempt to "do" Barcelona was a mistake! :) | 14:39 |
VW | well, we'll just blame Tom till he returns :D | 14:39 |
dc_mattj | #topic Weekly meeting time-slot? | 14:40 |
dc_mattj | #topic Weekly meeting time-slot? | 14:40 |
dc_mattj | #topic Weekly meeting time-slot? | 14:40 |
dc_mattj | #topic weekly meeting time-slot | 14:40 |
dc_mattj | whoops | 14:40 |
mihalis68 | Yes that's actually the next item, not that I mind | 14:40 |
dc_mattj | so time slot - who has thoughts on this ? | 14:40 |
mihalis68 | 9am for me is doable, but Tom comments it's not doable for him | 14:40 |
* VW thinks dc_mattj really wants to talk about the time slot | 14:40 | |
VW | I think that was just this week | 14:40 |
mihalis68 | it's even earlier for VW and mrhillsman, right? | 14:40 |
mrhillsman | 8am for me | 14:41 |
mrhillsman | for VW as well | 14:41 |
mrhillsman | unless he is earth exploring | 14:41 |
zioproto | what timezone are we talking avout ? | 14:41 |
mihalis68 | trouble with this agenda item: everyone for whom this slot is impossible is ... not here | 14:41 |
VW | yep - I can do 8am - it's not as easy as 9 because of school drop offs and such, but I can make it work | 14:41 |
mrhillsman | lol | 14:41 |
mihalis68 | i'm in EST | 14:41 |
dc_mattj | if you mean Tom's email, I thought he was saying that he's currently in a bad time zone | 14:41 |
dc_mattj | unless someone knows different | 14:41 |
mihalis68 | I thought he was always in a bad timezone, no? Korea? | 14:42 |
mrhillsman | yeah, looks like it is just today | 14:42 |
VW | yeah, it's his current location. His normal time zone, it would be 10:00pm | 14:42 |
mihalis68 | bad meaning "for this meeting", obviously | 14:42 |
dc_mattj | is it better at 1500 ? | 14:42 |
zioproto | anything that is in the morning in the US usually works for me | 14:42 |
mrhillsman | we don't need to change it | 14:42 |
dc_mattj | for most folks | 14:42 |
dc_mattj | I am happy with either | 14:42 |
mihalis68 | I notice that attendance has been worse since the end of DST here | 14:42 |
mihalis68 | can't prove cause and effect | 14:42 |
VW | yeah, I'd hate to push it further back | 14:42 |
VW | it's already 10:00pm for Tom | 14:43 |
VW | and 11:00pm for shintaro | 14:43 |
VW | both of whom we all value | 14:43 |
VW | :D | 14:43 |
mrhillsman | +2 | 14:43 |
mrhillsman | one for each :) | 14:43 |
mihalis68 | ok, sounds like it's fine | 14:43 |
mihalis68 | not easy for me but I was worried that it had become a bad time for too many | 14:43 |
dc_mattj | do we want to vote ? | 14:44 |
VW | I just may be late some weeks - until daylight savings - if I can't get the younger VW's moving in the morning ;) | 14:44 |
mihalis68 | we can move on as far as I'm concerned | 14:44 |
VW | +1 | 14:44 |
*** dc_mattj has quit IRC | 14:44 | |
zioproto | +1 | 14:44 |
zioproto | Matt left the room ? | 14:44 |
mihalis68 | uh-oh, the chair quit | 14:44 |
mihalis68 | he said he can't do the whole hour today | 14:44 |
*** dc_mattj has joined #openstack-operators | 14:45 | |
mihalis68 | last item was PTG. Bloomberg is sponsoring the first one and sending people from our CTO office | 14:45 |
dc_mattj | sorry | 14:45 |
dc_mattj | wifi dropped | 14:45 |
mihalis68 | and they encouraged me to go or send someone, and yet I still can't see it being appropriate for me | 14:45 |
dc_mattj | #topic Operators at PTG? | 14:45 |
mihalis68 | the writeup emphasizes you should go if you have a specific speciality | 14:45 |
mihalis68 | yes | 14:46 |
VW | I think we need to encourage all Operators to look at the ops mid-cycle in the same light a dev would look at PTG | 14:46 |
mihalis68 | none of my guys are interested in the slightest | 14:46 |
zioproto | mihalis68: on the web page they say that should go "Operators that are specialists on a given project (and are willing to spend their time giving feedback on their use case and contributing their usage experience to the team)" | 14:46 |
dc_mattj | Thierry's view on the list was that the sessions are definitely work sessions | 14:46 |
zioproto | I will try to be there to give feedback about Neutron stuff mostly | 14:46 |
VW | Think of it like this. We want the conversation at the forums to be about the 'What' - bugs needing fixing, features, gaps, etc | 14:46 |
mihalis68 | There' nothing there for me | 14:46 |
dc_mattj | so unless you want to get involved in development it's probably not that useful | 14:46 |
VW | and the PTG gets in to the "how" | 14:46 |
dc_mattj | zioproto, I think the idea is that the feedback bit is for the forum | 14:47 |
dc_mattj | VW, +1 | 14:47 |
mihalis68 | i wish Tom were here. I believe he said that some operators need to go to the PTG | 14:47 |
zioproto | dc_mattj: I did cut and paste from here https://www.openstack.org/ptg/ | 14:47 |
VW | so, in a perfect world, general discussions at an Ops mid-cycle lead to WG's and others generating propsoals for forum sessions (ideally with co-opration from some devs | 14:47 |
VW | at those forum sessions, decisions get made on what to do | 14:47 |
VW | and at the PTG, the devs dive in to all the messy bits of how to do them | 14:48 |
dc_mattj | that's my understanding too | 14:48 |
VW | while the Ops folks are back to have general discussions on the next thing on the pile | 14:48 |
VW | simple - right :D | 14:48 |
zioproto | please look at this https://www.openstack.org/ptg/ and there is a section "https://www.openstack.org/ptg/" | 14:48 |
zioproto | section "who should attend" | 14:48 |
zioproto | it says operatios | 14:48 |
zioproto | am I wrong ? | 14:48 |
zioproto | we are referred as "downstream" | 14:48 |
zioproto | is that about the forum > | 14:49 |
zioproto | ? | 14:49 |
mihalis68 | yes I've read that repeatedly. It's a qualified set of operators "who are specialists on a given project" | 14:49 |
mrhillsman | not sure why they put upstream and downstream -_- confuse-stream | 14:49 |
mihalis68 | I run a team where my guys do quite a bit of nova, cep, cinder, glance, keystone | 14:49 |
mihalis68 | but they STILL don't really qualify | 14:49 |
mrhillsman | i agreep on VWs perspective | 14:50 |
mrhillsman | i do not think any operator is "discouraged" from going, if they want | 14:50 |
zioproto | mihalis68: do your guys send patches upstream with the review platform ? | 14:50 |
zioproto | if yes I think they should go | 14:50 |
mrhillsman | but should expect the focus to be on how to accomplish the what | 14:50 |
*** dminer has joined #openstack-operators | 14:50 | |
mrhillsman | vs what to accomplish | 14:50 |
dc_mattj | guys, I'm going to have to drop off in a minute | 14:50 |
mihalis68 | we've tried a couple of times. It's really off-putting. Lots of minutiae | 14:50 |
mihalis68 | not sure if we got anything merged | 14:51 |
dc_mattj | I'm not sure this particular topic has a definitive outcome ? | 14:51 |
mrhillsman | i think general consensus is, if you want to go, go :) | 14:51 |
*** rmart04 has quit IRC | 14:51 | |
dc_mattj | other than we're still somewhat confused :) | 14:51 |
mihalis68 | Seems like there's only minimal interest in going from people on this chat, emirate? | 14:51 |
mihalis68 | amirite | 14:51 |
mihalis68 | yet Tom thinks some of us "should" go | 14:51 |
zioproto | mihalis68: that exactly the point. After meeting devs in person it is easier to get stuff merged upstream | 14:51 |
VW | the tl;dr is - if a n Operator has a reason to go to PTG , then go | 14:51 |
mrhillsman | there's not hard rule to not go | 14:51 |
dc_mattj | mihalis68, +1 from me unless I had someone in my team who was contributing to upstream code significantly | 14:52 |
mrhillsman | pretty sure we should bury this :) | 14:52 |
VW | but if someone is just trying to decide what is best - mid-cycle for OPs should be encouraged | 14:52 |
zioproto | 8 minutes to the end of the meeting | 14:52 |
mihalis68 | ok. I'm going to let tom and my CTO colleagues know that it' s not a fit for us, despite us running all the openstack here | 14:52 |
*** rmart04 has joined #openstack-operators | 14:52 | |
dc_mattj | I have to go, so I'm going to end this meeting here unless anyone has anything else urgent | 14:53 |
mrhillsman | pretty sure after the first or second iteration of the changes things will settle where appropriate | 14:53 |
mihalis68 | I know I could go, but I was surprised to hear from two sources that operators should go and make their voices heard. I think not, unless as you say they are deep specialists on a particular chunk of openstack tech | 14:53 |
dc_mattj | next week we will start putting together the agenda | 14:53 |
mrhillsman | nothing urgent here | 14:53 |
dc_mattj | #endmeeting | 14:53 |
openstack | Meeting ended Tue Nov 29 14:53:31 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:53 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-11-29-14.04.html | 14:53 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-11-29-14.04.txt | 14:53 |
openstack | Log: http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-11-29-14.04.log.html | 14:53 |
zioproto | thanks for the meeting :) | 14:53 |
dc_mattj | thank you all for coming :) | 14:53 |
zioproto | bye | 14:53 |
mrhillsman | thx everyone | 14:53 |
mihalis68 | I wasn't actually done | 14:53 |
mrhillsman | lol | 14:53 |
mihalis68 | no really | 14:53 |
mihalis68 | I was typing | 14:54 |
mrhillsman | it's matt's fault | 14:54 |
mihalis68 | I don't think we should shut down the meeting because someone has to go | 14:54 |
mrhillsman | i don't think anyone could have ended it | 14:54 |
zioproto | hey | 14:55 |
*** ducttape_ has joined #openstack-operators | 14:55 | |
mrhillsman | hey | 14:55 |
zioproto | anyone had problems with DJANGO and south python library | 14:55 |
zioproto | when upgrading from liberty to Mitaka ? | 14:55 |
zioproto | there is nothing in the release notes | 14:55 |
zioproto | and I am getting crazy to get this working | 14:55 |
mrhillsman | mihalis68 unless you know moderator can be changed | 14:55 |
mrhillsman | don't think we had a choice | 14:55 |
zioproto | I can believe it worked at the first shot for everyonelese ? :) | 14:56 |
mihalis68 | We're only getting to Liberty in production here | 14:56 |
mrhillsman | i can ask but do not think that was an issue | 14:56 |
zioproto | mrhillsman: on Ubuntu ? | 14:56 |
*** pilgrimstack1 has quit IRC | 14:56 | |
mrhillsman | yeah, 14.04 | 14:56 |
mihalis68 | ok the meeting's over, but can I ask : who is actually planning to attend PTG? | 14:56 |
mrhillsman | not me mihalis68 | 14:56 |
dc_mattj | sorry | 14:56 |
zioproto | mihalis68: I still have to decide, it could be | 14:56 |
dc_mattj | :( | 14:56 |
dc_mattj | thought everyone was done | 14:56 |
mihalis68 | no | 14:57 |
mihalis68 | but it's ok | 14:57 |
zioproto | mihalis68: I will decide beginning of January | 14:57 |
*** mriedem has joined #openstack-operators | 14:57 | |
mihalis68 | think I'm not going to PTG and I'll have to let Tom know because he specifically encouraged us to attend and represent | 14:57 |
mrhillsman | i missed that then | 14:58 |
mrhillsman | was this during bcn meeting? | 14:58 |
mihalis68 | It feels that the PTG is tightly defined by devs for devs so there's no forum for us to say our piece | 14:58 |
*** dc_mattj has quit IRC | 14:58 | |
zioproto | mrhillsman: I would like to know if you guys had problem upgrading the ubuntu package openstack-dashboard from liberty to mitaka on trusty :) thanks ! | 14:58 |
*** ecrehar has quit IRC | 14:58 | |
mrhillsman | zioproto i did not run into an issue | 14:59 |
mrhillsman | but i use openstack-ansible project | 14:59 |
mrhillsman | s/i/we | 14:59 |
zioproto | mrhillsman: thanks | 14:59 |
mrhillsman | liberty > mitaka / mitaka > newton | 14:59 |
*** dc_mattj has joined #openstack-operators | 14:59 | |
mrhillsman | let me ask osa folks | 14:59 |
mihalis68 | mrhillsman it could have been in-person, sorry, I don't recall | 15:00 |
mrhillsman | ok | 15:00 |
logan- | I didn't have that problem zioproto (osa managed deployment here). however I did run into that dogpile cache issue w/ nova that you posted in here last week zioproto :P | 15:01 |
mrhillsman | zioproto no issues | 15:01 |
mrhillsman | thx logan- | 15:01 |
*** dc_mattj has quit IRC | 15:01 | |
mrhillsman | zioproto | 15:02 |
mrhillsman | custom dashboard? | 15:02 |
zioproto | no, ubuntu dashboard | 15:02 |
zioproto | openstack-dashboard 2:9.1.0-0ubuntu1~cloud0 | 15:03 |
zioproto | logan-: Oh ! I have short memory, what did I paste about logpile ? | 15:04 |
zioproto | was it with nova ? | 15:05 |
logan- | https://bugs.launchpad.net/nova/+bug/1615582 | 15:05 |
openstack | Launchpad bug 1615582 in OpenStack Compute (nova) "Error: Unable to create the server. Unexpected API Error." [Undecided,New] | 15:05 |
logan- | yep | 15:05 |
mrhillsman | zioproto your dashboard has ubuntu logo or openstack logo by default? | 15:05 |
zioproto | by dashboard has the SWITCH logo :D | 15:06 |
zioproto | but we remove the ubuntu customization package | 15:06 |
zioproto | and we just replace the jpg logo with puppet | 15:06 |
logan- | it only happened in our env during the middle of the upgrade where the controllers were on mitaka and the computes were moving to liberty. once everything was on mitaka it disappeared | 15:06 |
zioproto | logan-: did you use the upgrade levels in your nova.conf ? | 15:07 |
logan- | no during the post mortem of it all I suspected that might be part of the cause | 15:07 |
mrhillsman | there was a jump in angular version, not sure if that is your problem, but upstream horizon untouched works | 15:07 |
logan- | have not validated whether that would have prevented it | 15:08 |
zioproto | logan-: ah yes now I remember ! thanks for the link :) I fixed so quickly that it did not stick into my mind | 15:08 |
zioproto | mrhillsman: as soon as I fill fix it I will let you know :) | 15:08 |
zioproto | the angular stuff is in the release notes | 15:09 |
mrhillsman | ok cool | 15:09 |
zioproto | need coffee ! see you guys later | 15:09 |
mrhillsman | l8r | 15:09 |
logan- | cya | 15:10 |
*** slaweq_ has quit IRC | 15:11 | |
*** slaweq_ has joined #openstack-operators | 15:12 | |
*** saneax is now known as saneax-_-|AFK | 15:23 | |
*** pilgrimstack has joined #openstack-operators | 15:23 | |
*** pilgrimstack has left #openstack-operators | 15:23 | |
*** chlong has joined #openstack-operators | 15:27 | |
*** mriedem is now known as mriedem_meeting | 15:29 | |
*** sfrode has joined #openstack-operators | 15:34 | |
*** vijaykc4 has quit IRC | 15:35 | |
*** zul has joined #openstack-operators | 15:38 | |
*** udesale has quit IRC | 15:55 | |
*** mriedem_meeting is now known as mriedem | 16:00 | |
*** _ducttape_ has joined #openstack-operators | 16:00 | |
*** rcernin has quit IRC | 16:03 | |
*** ducttape_ has quit IRC | 16:03 | |
*** ckonstanski has quit IRC | 16:05 | |
*** vijaykc4 has joined #openstack-operators | 16:06 | |
*** chlong has quit IRC | 16:07 | |
*** _ducttape_ has quit IRC | 16:11 | |
*** ducttape_ has joined #openstack-operators | 16:12 | |
*** chlong has joined #openstack-operators | 16:20 | |
*** armax has joined #openstack-operators | 16:32 | |
*** pcaruana has quit IRC | 16:36 | |
*** akanksha__ has joined #openstack-operators | 16:38 | |
*** ducttape_ has quit IRC | 16:39 | |
*** ducttape_ has joined #openstack-operators | 16:39 | |
*** akanksha__ is now known as ApheleiaS | 16:41 | |
*** _ducttape_ has joined #openstack-operators | 16:41 | |
*** ducttape_ has quit IRC | 16:41 | |
*** jamesdenton has quit IRC | 16:45 | |
*** rmart04 has quit IRC | 16:47 | |
zioproto | mrhillsman: it ended up we had a django extension in our horizon based on the south library, that was removed in django 1.8.7 | 16:49 |
*** dbecker has quit IRC | 16:54 | |
*** jamesdenton has joined #openstack-operators | 16:54 | |
*** ckonstanski has joined #openstack-operators | 17:00 | |
*** chlong has quit IRC | 17:10 | |
*** zioproto has quit IRC | 17:22 | |
*** chlong has joined #openstack-operators | 17:24 | |
*** makowals_ has quit IRC | 17:25 | |
*** matrohon has quit IRC | 17:26 | |
*** vijaykc4 has quit IRC | 17:27 | |
stupidnic | I am wondering if somebody can point me in the right direction here. I am trying to change the path that horizon uses from /horizon to / but when I login I am getting redirected to /identity which isn't found. I thought I fixed the local_settings.py correctly but I must be missing something. | 17:38 |
*** nemesis-ninux has quit IRC | 17:40 | |
*** matrohon has joined #openstack-operators | 17:42 | |
*** vijaykc4 has joined #openstack-operators | 17:44 | |
*** markvoelker has quit IRC | 17:45 | |
*** markvoelker has joined #openstack-operators | 17:50 | |
*** derekh has quit IRC | 17:51 | |
*** Apoorva has joined #openstack-operators | 18:02 | |
*** simon-AS559 has quit IRC | 18:11 | |
*** vijaykc4 has quit IRC | 18:12 | |
*** sudipto_ has quit IRC | 18:13 | |
*** sudipto has quit IRC | 18:13 | |
*** zul has quit IRC | 18:13 | |
mdorman | stupidnic: we have these settings in local_settings: WEBROOT = '/dashboard/' , LOGIN_REDIRECT_URL = '/dashboard' , LOGIN_URL = '/dashboard/auth/login/' , LOGOUT_URL = '/dashboard/auth/logout/' | 18:13 |
stupidnic | mdorman: Thanks. I have determined that I can access other endpoints /project /admin, etc just not identity, so something else might be going on here. | 18:14 |
mdorman | stupidnic: i vaguely remember some problem with using / as the root from a while back. there was some other setting inside horizon taht would cause the css and other resources to get path’d incorrectly if the root was set to / but i think that has since been fixed | 18:14 |
mdorman | ah ok | 18:14 |
stupidnic | mdorman: yeah I am trying this on Newton, so I would hope that was addressed. We have no problem using / in Liberty | 18:15 |
*** zul has joined #openstack-operators | 18:21 | |
stupidnic | sigh... switching it back to /horizon/ makes it work. | 18:23 |
stupidnic | mdorman: so it looks like you are correct... | 18:23 |
mdorman | i would have to go dig a little bit to find the bug again. unfortunately i don’t remember all the details off the top of my hea | 18:27 |
mgagne | used to be $webroot variable in _variables.scss | 18:28 |
mdorman | yes, that sounds very familiar | 18:28 |
mgagne | you will need to recompress static files after changing it | 18:28 |
stupidnic | mgagne: I did so. The other areas display correctly (no CSS issues or missing images) it's only the /identity endpoint | 18:29 |
stupidnic | /project and /admin both work | 18:29 |
mgagne | ok, can't help you more on that one. Do you happen to host Keystone service on the same server under the /identity path? | 18:29 |
stupidnic | Keystone is on the same server, but keystone runs under a different port | 18:30 |
mgagne | ok | 18:30 |
stupidnic | let me follow that thread though | 18:30 |
*** makowals has joined #openstack-operators | 18:30 | |
mgagne | other than checking horizon logs, I have no idea. enabling debug too | 18:30 |
stupidnic | mgagne: damn it... you are spot on | 18:31 |
stupidnic | mgagne: there is an alias endpoint in the keystone defintion for /identity that is clrearly conflicting with horizon's when you move it to the root url | 18:31 |
mgagne | =) | 18:32 |
stupidnic | Alias /identity /usr/bin/keystone-wsgi-public | 18:32 |
mgagne | glad you found it | 18:32 |
stupidnic | Any clue what that is used for? | 18:32 |
*** VW has quit IRC | 18:32 | |
mgagne | keystone auth? | 18:32 |
stupidnic | shouldn't that occur on the keystone ports? | 18:33 |
mgagne | looks like it imo (the service running on 5000 tcp port) | 18:33 |
david-lyle | stupidnic: the problem is horizon has /identity as one of the dashboards and it's keystone's default endpoint | 18:33 |
david-lyle | so when you log into horizon at / the default dash is /identity if you have access to that dashboard | 18:33 |
stupidnic | david-lyle: what is that keystone endpoint actually used for? doesn't most stuff auth with the keystone ports? | 18:33 |
david-lyle | no, no special port under apache | 18:34 |
david-lyle | that's the actual endpoint now | 18:34 |
mgagne | depends on your setup, could be some installer moved all services under path (/identity, /volume, etc.) instead of ports. Moving horizon at root increases the risk of conflicts. | 18:34 |
david-lyle | what you can do is put a redirect in apache for / to got to horizon/ | 18:35 |
stupidnic | Yeah, I hate that (personal style issue) | 18:35 |
david-lyle | and then you won't see the conflict and still can hit / for horizon | 18:35 |
david-lyle | sure | 18:35 |
david-lyle | not very elegant for sure | 18:35 |
stupidnic | So, just help me understand this here... | 18:35 |
stupidnic | what exactly is the purpose of the http://controller/indentiy and http://controller/identity_admin endpoints? | 18:36 |
stupidnic | is that just public aliases to the keystone service? | 18:36 |
*** VW has joined #openstack-operators | 18:37 | |
stupidnic | so that users don't have to hit 5000 or 35357 | 18:37 |
stupidnic | As near as I can tell that looks to be the purpose of those two endpoints | 18:39 |
david-lyle | https://github.com/openstack/keystone/blob/master/httpd/wsgi-keystone.conf#L52 is the config, maybe just for HEAD ? | 18:41 |
david-lyle | oh, it's just another alias, pasted without looking :( | 18:42 |
stupidnic | Yeah. It's cool. I believe that nothing native in Openstack is hitting those endpoints... they are just a helper aliases for users that might be behind a firewall that would block access to port 5000 or 35357 | 18:43 |
david-lyle | I think the idea was to hide the need for magic ports | 18:43 |
david-lyle | but the keystone room would know better | 18:44 |
stupidnic | Yeah I am not going to stress over it too much. Horizon is what 99% of our users use, so getting that to parity with our current Liberty install is more important | 18:45 |
stupidnic | Thanks for the help in getting to the bottom of this. | 18:45 |
*** electrofelix has quit IRC | 18:55 | |
*** mihalis68 has quit IRC | 19:11 | |
*** matrohon has quit IRC | 19:14 | |
*** VW_ has joined #openstack-operators | 19:20 | |
*** VW_ has quit IRC | 19:21 | |
*** racedo has joined #openstack-operators | 19:22 | |
*** racedo has quit IRC | 19:23 | |
*** racedo has joined #openstack-operators | 19:23 | |
*** VW has quit IRC | 19:24 | |
*** racedo has quit IRC | 19:25 | |
*** paramite has quit IRC | 19:30 | |
*** VW has joined #openstack-operators | 19:39 | |
*** paramite has joined #openstack-operators | 19:43 | |
*** paramite has quit IRC | 19:49 | |
*** slaweq_ has quit IRC | 19:57 | |
*** slaweq_ has joined #openstack-operators | 19:58 | |
*** rockyg has joined #openstack-operators | 20:02 | |
*** rockyg has quit IRC | 20:04 | |
*** rockyg has joined #openstack-operators | 20:04 | |
*** slaweq_ has quit IRC | 20:16 | |
*** slaweq_ has joined #openstack-operators | 20:17 | |
*** VW has quit IRC | 20:18 | |
*** slaweq_ has quit IRC | 20:22 | |
*** slaweq_ has joined #openstack-operators | 20:23 | |
*** VW has joined #openstack-operators | 20:24 | |
*** VW has quit IRC | 20:32 | |
*** VW has joined #openstack-operators | 20:32 | |
*** catinthe_ has quit IRC | 20:35 | |
*** slaweq_ has quit IRC | 20:42 | |
*** slaweq_ has joined #openstack-operators | 20:44 | |
*** VW has quit IRC | 20:54 | |
*** matrohon has joined #openstack-operators | 20:57 | |
*** rocky_g has joined #openstack-operators | 20:59 | |
*** rockyg has quit IRC | 21:00 | |
*** VW has joined #openstack-operators | 21:02 | |
*** VW has quit IRC | 21:04 | |
*** VW has joined #openstack-operators | 21:05 | |
*** liverpooler has joined #openstack-operators | 21:27 | |
*** catintheroof has joined #openstack-operators | 21:34 | |
*** catintheroof has quit IRC | 21:38 | |
*** catintheroof has joined #openstack-operators | 21:47 | |
*** matrohon has quit IRC | 21:54 | |
*** matrohon has joined #openstack-operators | 21:54 | |
*** dtrainor has quit IRC | 22:00 | |
*** simon-AS559 has joined #openstack-operators | 22:00 | |
*** slaweq_ has quit IRC | 22:03 | |
*** racedo has joined #openstack-operators | 22:05 | |
*** rocky_g has quit IRC | 22:10 | |
*** chlong has quit IRC | 22:12 | |
*** jamesdenton has quit IRC | 22:15 | |
*** matrohon has quit IRC | 22:22 | |
*** dminer has quit IRC | 22:24 | |
*** rcernin has joined #openstack-operators | 22:31 | |
*** mriedem has quit IRC | 22:48 | |
*** racedo has quit IRC | 22:59 | |
*** racedo has joined #openstack-operators | 23:01 | |
*** rcernin has quit IRC | 23:01 | |
*** rcernin has joined #openstack-operators | 23:03 | |
*** catinthe_ has joined #openstack-operators | 23:03 | |
*** rcernin has quit IRC | 23:04 | |
*** rcernin has joined #openstack-operators | 23:04 | |
*** catintheroof has quit IRC | 23:06 | |
*** ducttape_ has joined #openstack-operators | 23:14 | |
*** mriedem has joined #openstack-operators | 23:14 | |
*** _ducttape_ has quit IRC | 23:17 | |
*** ducttape_ has quit IRC | 23:19 | |
mdorman | is it possible to delete multiple floating IPs in a single neutron call? i have a large number (~1000) that i want to delete as simultaneously as possible, and if i just have to for loop that it’s going to take a while. | 23:31 |
yankcrime | anyone know if it's possible to remove a neutron lbaas (v1) pool from an agent and then add it to another? | 23:33 |
*** rcernin has quit IRC | 23:41 | |
*** ckonstanski has quit IRC | 23:48 | |
*** VW_ has joined #openstack-operators | 23:51 | |
*** VW has quit IRC | 23:55 | |
*** VW_ has quit IRC | 23:56 | |
yankcrime | doesn't look like it is | 23:58 |
yankcrime | to the database! | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!