Tuesday, 2018-08-28

*** gyee has quit IRC00:02
*** slaweq has joined #openstack-operators00:11
*** slaweq has quit IRC00:16
*** macza has quit IRC00:17
*** macza has joined #openstack-operators00:17
*** macza has quit IRC00:20
*** Caterpillar has quit IRC01:05
*** Caterpillar has joined #openstack-operators01:06
*** wvera has joined #openstack-operators01:07
*** wvera has quit IRC01:12
*** wvera has joined #openstack-operators01:14
*** wvera has quit IRC01:46
*** dtrainor_ has quit IRC01:51
*** dtrainor has joined #openstack-operators01:51
*** slaweq has joined #openstack-operators02:11
*** slaweq has quit IRC02:16
*** dtrainor has quit IRC02:40
*** dtrainor has joined #openstack-operators02:40
*** VW_ has quit IRC02:44
*** khyr0n has joined #openstack-operators02:58
*** dtrainor_ has joined #openstack-operators03:34
*** dtrainor has quit IRC03:34
*** gkadam has joined #openstack-operators03:36
*** dtrainor has joined #openstack-operators03:53
*** dtrainor_ has quit IRC03:54
*** slaweq has joined #openstack-operators04:11
*** slaweq has quit IRC04:15
*** Bhujay has joined #openstack-operators04:18
*** Bhujay has quit IRC04:19
*** dtrainor_ has joined #openstack-operators04:26
*** dtrainor has quit IRC04:26
*** macza has joined #openstack-operators05:00
*** slaweq has joined #openstack-operators05:11
*** slaweq has quit IRC05:16
*** dtrainor_ has quit IRC05:27
*** dtrainor has joined #openstack-operators05:27
*** slaweq has joined #openstack-operators05:28
*** slaweq has quit IRC05:33
*** slaweq has joined #openstack-operators06:11
*** macza has quit IRC06:12
*** slaweq has quit IRC06:16
*** pcaruana has joined #openstack-operators06:39
*** aojea has joined #openstack-operators06:40
*** rcernin has quit IRC07:02
*** slaweq has joined #openstack-operators07:02
*** dims has quit IRC07:08
*** dims has joined #openstack-operators07:10
*** macza has joined #openstack-operators08:11
*** macza has quit IRC08:16
*** electrofelix has joined #openstack-operators08:46
*** rcernin has joined #openstack-operators08:59
*** takamatsu has joined #openstack-operators09:15
*** saybeano has joined #openstack-operators09:44
*** rcernin has quit IRC09:47
*** saybeano has quit IRC09:56
*** saybeano has joined #openstack-operators10:04
*** wvera has joined #openstack-operators10:12
*** wvera has left #openstack-operators10:12
*** med_ has joined #openstack-operators12:03
*** wvera has joined #openstack-operators12:24
*** wvera has quit IRC12:32
*** wvera has joined #openstack-operators12:32
*** mriedem has joined #openstack-operators12:35
*** wvera has left #openstack-operators12:59
*** r-mibu has joined #openstack-operators13:03
*** gkadam has quit IRC13:05
*** med_ has quit IRC13:31
*** rtjure has quit IRC13:34
*** rtjure has joined #openstack-operators13:37
*** wvera has joined #openstack-operators13:43
*** kendallwaters has joined #openstack-operators13:50
*** wvera has quit IRC13:52
*** shintaro has joined #openstack-operators14:01
* smcginnis looks around14:02
shintaroo/14:02
smcginnisHey shintaro14:02
shintarohi smcginnis14:02
smcginnisshintaro: Looks like it's just us today.14:03
shintaro:(14:03
*** mihalis68_ has joined #openstack-operators14:04
mihalis68_o/14:04
shintarohi mihalis6814:04
smcginnisHe's alive!14:05
mihalis68_he he14:05
*** VW_ has joined #openstack-operators14:05
mihalis68_#startmeeting ops-meetup-team14:05
openstackMeeting started Tue Aug 28 14:05:50 2018 UTC and is due to finish in 60 minutes.  The chair is mihalis68_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:05
*** openstack changes topic to " (Meeting topic: ops-meetup-team)"14:05
openstackThe meeting name has been set to 'ops_meetup_team'14:05
mihalis68_how is everyone14:06
shintaroo/14:06
mihalis68_I think there's really only one topic, which is pulling together the technical agenda for the PTG14:07
smcginnisLast I looked at the planning etherpad, we were getting a good list of topics at least.14:07
shintaroI see 12 proposals14:07
smcginnis#link https://etherpad.openstack.org/p/ops-meetup-ptg-denver-201814:07
mihalis68_also #link https://etherpad.openstack.org/p/ops-meetups-team14:09
mihalis68_I'm hopelessly backlogged due to vacation and then production emergencies. I'm really pleased to see all this progress. What we need now, I would suggest, is a volunteer to map the proposals to slots14:10
mihalis68_well volunteered, Erik14:11
mihalis68_ok just kidding, he's not here14:11
smcginnisI would volunteer, but until we get the rocky release out and I catch up on some other things, I'm a little backlogged too.14:11
mihalis68_Ok I can have a go at this, but I would need people to give some feedback. If some names are put forward for that bit, I'll try to pull together the agenda and I would say we should review before this time next week14:12
mihalis68_anyone object?14:12
mihalis68_alright #action mihalis68 to convert the planning etherpad into a proposed agenda14:12
smcginnis+114:13
mihalis68_attendees here today please add your name to the team etherpad (second link above)14:13
shintaro#link https://docs.google.com/spreadsheets/d/1EUSYMs3GfglnD8yfFaAXWhLe0F5y9hCUKqCYe0Vp1oA/edit#gid=10234608614:13
shintaropast planning spreadsheets are here if you like to use it.14:13
smcginnisshintaro: Oh right, I forgot about that.14:13
mihalis68_Thanks Shintaro. I'll start there14:14
mihalis68_how would we gather to review? Here? email?14:14
*** emccormickva has joined #openstack-operators14:14
*** emccormickva has quit IRC14:14
mihalis68_hey emccormickva!14:15
smcginnismihalis68_: Maybe ops mailing list, then try to finalize here next week?14:15
mihalis68_yeah, that works for me14:15
*** emccormick has joined #openstack-operators14:15
mihalis68_at least email doesn't tell me I'm wrong every week and force me to fiddle with nicknames14:15
emccormicko/14:15
emccormicksorry, having a war with IRC this morning :(14:15
mihalis68_me too, me too14:16
emccormickwonder why it thought I was still logged on when my client had been closed for days :P14:16
mihalis68_so summarising what you missed, I'm going to try and put up a *proposed* agenda on the google docs sheet and then get people's feedback via operators mailing list14:16
emccormicksuper14:16
mihalis68_(note to self, maybe should book travel and accomodation to denver also :|14:17
mihalis68_we are sending just two people and the other guy already booked!14:17
emccormickjust bought my plane ticket yesterday. Last piece of the puzzle complete14:17
mihalis68_I mean already in the sense that I've had weeks and he had a day14:17
emccormickslacker14:17
mihalis68_totally14:18
mihalis68_I don't see any foundation folks here, so I guess we can't check on numbers etc14:18
emccormickI need to put it in the etherpad still, but I asked the Kayobe PTL to come talk to us.14:18
emccormickNeeds to be Tuesday sometime14:18
emccormickThought it'd be a good chance for him to get some feedback and people to ask him why his project is necessary ;)14:19
emccormickit's a new deployment project that bolts on to Kolla.14:19
smcginnisIn case anyone else had to look that up like me - https://kayobe.readthedocs.io/en/latest/14:19
emccormickMy first question is: Why isn't it part of Kolla14:19
emccormick:)14:19
mihalis68_I had to look it up, and I'm not ashamed to admit it!14:19
emccormickI did as well14:20
mihalis68_seems like a really good topic for Denver, emccormick!14:20
emccormickbut it looks interesting. I thought maybe others would like to know also14:20
emccormickHe clearly needs some PR14:20
mihalis68_We're still not containerised *hangs head in shame*14:20
mihalis68_what else should we discuss for Denver?14:20
mihalis68_make Kayobe the "keynote" for Tuesday?14:21
emccormickOther than agenda, I think Denver is pretty well good to go14:21
mihalis68_i.e. fun first substantive session?14:21
emccormickYeah sounds like a good plan.14:21
mihalis68_is there a plan for ops related monday night social?14:21
emccormickI told him he didn't have to get fancy with it or anything. Just an overview and Q&A14:21
mihalis68_sorry I'm so out of the loop, driving up mountains last week14:21
emccormickThere is desire for it, but no plan. I have a request out to a friend for local suggestions.14:22
mihalis68_Could you be point person for that then?14:22
emccormickSince we have no sponsor, it'll probably be an organic formation that day14:22
emccormickyeah ok14:22
mihalis68_and again I would say coordinate that via operators mailing list14:22
mihalis68_ok cool14:22
shintarosome proposals on the etherpad already.14:22
mihalis68_#action emccormick to pull together ideas for monday night ops related social in Denver14:23
mihalis68_the other topic I had in mind was the operators-related openstack docs14:24
mihalis68_#topic operators docs14:24
*** openstack changes topic to "operators docs (Meeting topic: ops-meetup-team)"14:24
mihalis68_smcginnis I see we had a patch proposed for the operators guide, and then lots of +1s, then he abandoned it, and now questions about having to sign something?14:25
mihalis68_Can you comment on whether that process is working? I am confused.14:25
mihalis68_I managed to get to the point of +1ing the change14:25
smcginnismihalis68_: We had a few patches go through. I didn't look at that abandoned one.14:25
smcginnismihalis68_: I think you should be able to +2 and approve as well.14:25
mihalis68_is it the low-drag process we hoped for?14:25
smcginnisThere was the question on the ML about whether contributors needed to sign the Contributor License Agreement and it was confirmed they do not for this repo.14:26
smcginnisWhich I think is good.14:26
mihalis68_I guess I'll watch it and learn more about how it works14:27
*** dtrainor has quit IRC14:27
mihalis68_It's still on my mind that we were considering pulling the HA guide into this process and encouraging Adam Speirs(?) to do the rewrite he offered14:27
emccormickspotz has agreed to help with getting people set up in Denver14:27
mihalis68_maybe it was speith?14:27
emccormickdefinitely going to avail myself of that14:27
mihalis68_me too14:27
smcginnismihalis68_: Adam Speirs (sp?) I believe.14:28
smcginnisNot in this channel at any rate.14:28
*** pcaruana has quit IRC14:29
mihalis68_I'm sure I had his name in prior meeting logs from these meetings14:29
shintaroHes Adam Spiers (aspires(14:29
mihalis68_I'm going to try and work on the document we have in this pipeline first to understand it better before contacting Adam14:30
mihalis68_Thanks shintaro14:30
shintaroaspieres14:30
shintarono14:30
*** pcaruana has joined #openstack-operators14:30
shintaroaspiers14:30
mrhillsmanDoes mihalis68_ not have +2 for the docs repo?14:31
mihalis68_I'm told I do. I thought it would be really presumptuous to +2 something as my first action14:31
mrhillsmanSorry catching up14:31
mihalis68_welcome back!14:32
mihalis68_I did +1 a patch and I think that worked.14:32
mrhillsmanNot at all :) especially since you're probably most familiar with how it is setup14:32
mrhillsmanthx14:32
mihalis68_oh other people did all the work (smcginnis in particular)14:32
smcginnismihalis68_: If you want to +2 but not approve, you can just ping me if you think something is ready to be approved for now until you're more comfortable.14:33
mihalis68_that's a good idea14:33
mihalis68_thanks!14:33
smcginnisGood to have real operator experience since I only play one on TV.14:33
mihalis68_ok I sense there's not much more to be had from this meeting14:33
mihalis68_so #topic any other business14:33
*** Bhujay has joined #openstack-operators14:33
mihalis68_oh yes early-bird pricing on Berlin expires soon14:34
emccormickWe shouldn't need it14:34
emccormickthough I'm not sure how we go about registering for Berlin with our PTG pass?14:34
*** Bhujay has quit IRC14:34
smcginnisAfter the PTG you will get a code to allow free registration.14:34
*** Bhujay has joined #openstack-operators14:35
shintaro+114:35
smcginnisIt's a little confusing with bad timing since they send out these emails saying "register now!" but really if you are going to the PTG you should wait.14:35
mihalis68_this is really good info!14:35
mihalis68_Ill probably try to make Berlin, can't say for sure14:36
mihalis68_I've gone from never travelling on business to like 5-6 times/year. Wife not thrilled14:36
*** dtrainor has joined #openstack-operators14:37
spotzsorry I'm late14:37
smcginnisI know how that goes.14:37
mihalis68_hi there14:37
mihalis68_how are PTG numbers?14:37
smcginnisemccormick did you want to pair up with spotz and PTG outing?14:37
emccormicksure!14:38
emccormickmihalis68_ bring wifey to Berlin with you :)14:38
mrhillsman++14:38
emccormickChristmas markets might even be started by then14:38
mihalis68_I think we're done here, work moves to mailing list for immediacy over the next week and hopefully in one weeks time we'll be able to confirm the agenda and tell everyone where the beer... I mean social event will be14:39
emccormickI put the Kayobe thing on the etherpad14:39
mihalis68_great, thanks!14:39
spotzI'm still trying to get confirmation from SUSE on whether they can do the troubleshooting session. We have a deadline to know by?14:39
emccormickspotz: we can always shuffle at the last minute14:40
mihalis68_well we can only do one more IRC meeting before being in Denver, so it would be nice at least to know by this time next week14:40
spotzOk I'll poke again14:40
emccormickI guess we need to determine how the agenda is getting printed, or if it is at all.14:41
emccormickMaybe the google doc is sufficient and more fluid14:41
spotzIf anyone'll be at Open Source Summit this week be happy totouch base on anything14:41
smcginnisWe could just put the agenda up on the screen at the start of the event and during breaks. That could allow us to be a little flexible if we need to shift things around.14:41
spotzemccormick: etherpad:)14:41
mihalis68_previously it was nicely designed and printed, that's a good point14:41
emccormick*nod*14:41
mihalis68_however that process was ... painful14:41
mihalis68_almost by definition the deadline for going to print is before when you know that all sessions really are going to happen14:42
mihalis68_(it was painful for the NYC one)14:42
emccormickspotz or etherpad ;)14:42
emccormickagreed14:42
emccormickkeep it electronic then14:42
mihalis68_works for me14:42
smcginnisWith past PTG sessions, it's worked well to have a rough agenda and just work our way through the topics. Then if something only ends up taking 10 minutes, we can take a break and move on. And if something ends up being a bigger discussion than planned we are flexible enough to not have to kill a productive conversation.14:43
mihalis68_we can at least break it out from the google doc when it's close to done. At least for me, google docs access is difficult14:43
mihalis68_(blocked entirely on my employers network)14:43
mihalis68_smcginnis I like that14:43
spotzI know some countries have trouble with google14:44
mihalis68_this again moves towards working sessions, not presentations14:44
emccormickkeeps from having a moderator standing up there talking to a dead room for 40 minutes also ;)14:44
mihalis68_although that would never happen, right? RIGHT?14:44
smcginnis:)14:44
emccormickno never14:45
*** markvoelker has joined #openstack-operators14:45
mihalis68_#agreed ops meetup agenda for PTG will be a) electronic b) more flexible14:46
smcginnisWorth a shot to see how it goes.14:46
shintaro+114:46
emccormick+114:46
emccormick:)14:46
mihalis68_oh ... darnit... just realised we're going to have to round up moderators for all these sessions and that's even harder than putting together a topic list on the sheet14:46
spotzheheh14:47
smcginnisAnother plea to the ML?14:47
emccormickyeah. There's a few volunteers on there at least14:47
mihalis68_yes, I think with a link to the rough draft agenda14:47
mihalis68_containers: erik14:48
mihalis68_ffwd upgrades: erik14:48
mihalis68_docs: erik14:48
mihalis68_I'm getting the hang of it already14:48
emccormick*snort*14:48
emccormickSimon volunteered for containers. One less for me. Wheeee!14:48
mihalis68_excellent14:49
mihalis68_alright, any more business?14:49
*** saybeano has quit IRC14:49
*** markvoelker has quit IRC14:49
emccormickfyi my intent is to just go down the hall monday afternoon for upgrades14:49
emccormickI see no reason we shouldn't just do that as a group since it's always the hot topic of the meetups14:49
emccormickif you think it's a terrible idea just say so, but I think that'd be most productive all around.14:50
spotzI think some of the projects like OSA might like to meet with OPs folks14:50
emccormickI think some of those were after our meetup is done?14:51
emccormicklost the damn schedule again.14:51
mihalis68_I can tell this is going to be like 9-D chess14:52
spotzemccormick: Yeah but if we don't have a full agenda, offering to meet with the deployment projects might not be a bad idea14:52
emccormickoh yeah14:52
mihalis68_two events side by side, related communities, variable length sessions14:52
emccormickspotz yes I'm all for it14:52
emccormickwe're going to need so run the agenda through CI14:53
emccormickok, Chris do the draft14:53
mihalis68_there's a tension here. A single track can compress some sessions and lengthen others14:53
emccormickwe'll see what it looks like and massage as needed14:53
mihalis68_but a multi-track event can't allow that, or nobody will be able to switch tracks14:53
emccormickwell, we can pull some folks in to our track14:54
emccormickand in the case of upgrades we'll take our track to them14:54
mihalis68_you wont be able to say "after ceph I'm going to designate" if ceph can run long and maybe overlap the other14:54
emccormickotherwise it'll be things after the meetup14:54
spotzWell we could time our sessions to the same lengths as PTG14:55
emccormickwe definitely should sync it as much as possible14:55
emccormickit's like half day blocks though, right?14:55
mihalis68_yeah, but sean was saying we can cut some sessions down in length if they're not working. That flexibility has a cost if nobody can actually know when later sessions will start14:55
smcginnisThe PTGbot helps with tracking cross-track things.14:55
emccormickmihalis68_ The flexibility is within a large block14:56
smcginnisSince most of them don't have set time blocks, there's a bot in the #openstack-ptg channel that folks can state their current topics and what they plan to talk about next.14:56
smcginnisThe bot takes care of updating that on the PTG web page.14:56
*** VW_ has quit IRC14:56
smcginnisThere's still some old data from the last PTG - http://ptg.openstack.org/ptg.html14:56
emccormickwhere is that web page btw?14:57
shintarocool14:57
mihalis68_maybe we should think about going "full PTG"? (you never go full ptg!)14:57
mihalis68_i.e. throw away the rigid scheduling style of previous independent ops meetups14:58
mihalis68_(although... I've never done PTG nor used PTGbot and there will be lots like me)14:58
emccormickmihalis68_ Let's at least do a draft the old way14:58
mihalis68_ok14:58
emccormickcall it a suggested guide if you want14:58
*** Bhujay has quit IRC14:58
emccormickwe need some structure. Maybe just not so much as before14:58
smcginnis++14:59
emccormickyou could say topics A - E Monday morning14:59
emccormickAFternoon is all upgrades with the upgrade SIG14:59
emccormickTuesday morning G - K, Tuesday afternoon L - P14:59
*** pcaruana has quit IRC15:00
spotzThat should work15:00
emccormickand then we can flex within those blocks if needed, or shift something to another block, but at least we make sure everything has a place and gets covered15:00
mihalis68_well, we're out of time! Thanks all and I suggest we carry this onwards on the mailing list15:00
smcginnisThanks!15:01
mihalis68_#endmeeting15:01
*** openstack changes topic to "Discussion of topics related to operating Openstack infrastructures at scale | Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators | Logs: http://eavesdrop.openstack.org/irclogs/"15:01
openstackMeeting ended Tue Aug 28 15:01:23 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-08-28-14.05.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-08-28-14.05.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-08-28-14.05.log.html15:01
shintarothank you all15:01
emccormicko/ tata15:01
*** shintaro has quit IRC15:01
spotzthanks!15:02
*** dtrainor_ has joined #openstack-operators15:03
*** dtrainor has quit IRC15:03
*** gkadam has joined #openstack-operators15:10
*** dtrainor_ has quit IRC15:26
*** gyee has joined #openstack-operators15:27
*** dtrainor_ has joined #openstack-operators15:27
*** etp has joined #openstack-operators15:36
*** macza has joined #openstack-operators16:03
*** Bhujay has joined #openstack-operators16:17
*** gkadam has quit IRC16:21
*** Bhujay has quit IRC16:22
*** Bhujay has joined #openstack-operators16:30
*** macza_ has joined #openstack-operators16:30
*** macza has quit IRC16:34
*** khyr0n has quit IRC16:39
*** Bhujay has quit IRC16:43
*** Bhujay has joined #openstack-operators16:44
*** aojea has quit IRC16:45
*** kendallwaters has quit IRC17:00
*** r-mibu has quit IRC17:12
*** Bhujay has quit IRC17:24
*** markvoelker has joined #openstack-operators17:51
*** electrofelix has quit IRC18:23
*** markvoelker has quit IRC18:32
*** markvoelker has joined #openstack-operators18:33
*** markvoelker has quit IRC18:37
*** markvoelker has joined #openstack-operators19:19
*** khyr0n has joined #openstack-operators19:35
*** slaweq has quit IRC20:40
*** slaweq has joined #openstack-operators20:40
*** mihalis68_ has quit IRC20:51
* jhebden is back from [afk] - 426524h:56m:12s away20:56
*** markvoelker has quit IRC21:05
*** rcernin has joined #openstack-operators21:46
*** macza_ has quit IRC23:00
*** threestrands has joined #openstack-operators23:54

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!