15:00:20 #startmeeting Ops Meetup Team 15:00:21 Meeting started Tue Feb 6 15:00:20 2018 UTC and is due to finish in 60 minutes. The chair is mihalis68. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:24 The meeting name has been set to 'ops_meetup_team' 15:00:33 #link https://etherpad.openstack.org/p/ops-meetups-team 15:00:41 #topics actions from previous meetings 15:00:47 o/ 15:00:51 heya 15:00:52 o/ 15:00:55 o/ 15:01:01 hi 15:01:43 I had 3 actions. Read up about OpenStack Days: no progress. Notify community about ops guide wiki conversion : done/in-progress. Notify community about meeting time change - could do better 15:02:13 anyone else wish to comment on prior actions? (we now use the honor system, if you get an action and don't do it, nobody chases you) 15:02:42 ok! 15:02:45 #topic Tokyo 15:03:00 Shintaro has added more detail to the agenda (link above) 15:03:17 31 registraion so far. expect more NTT people to come 15:03:20 estimated attendance ~60 (31 register, ~30 more expected from NTT) 15:03:37 o/ and Jimmy is also here. Having trouble getting online 15:03:42 I will try to promote more 15:03:45 we can all tweet and otherwise get the word out since there's still plenty of time to make travel and accommodation plans 15:03:53 hello and welcome 15:03:59 Anne from the Foundation team is also attending 15:04:16 also on the agenda, the ether pad. We need more moderators. I have volunteered for two sessions 15:04:20 great news! 15:04:22 *etherpad link 15:04:31 We will continue to support on social media, tweeting the Superuser link 15:04:37 great! Thanks so much 15:04:45 #link https://etherpad.openstack.org/p/TYO-ops-meetup-2018 15:04:54 Nice. Full house :) 15:05:43 Looks like we picked up a moderator. We need to blat out another request. 15:05:43 who here is attending tokyo? 15:05:51 o/ 15:05:51 o/ 15:05:59 o/ 15:06:01 o/ 15:06:25 I will wait to put my name down as a moderator, but am willing to fill in where needed. 15:06:34 sean you could probably handle openstack contributor in your sleep (1st session)? 15:06:48 "contribution workflow" 15:06:50 Oh yeah, I'll put my name down for that one for now. 15:06:55 cool, thanks 15:07:38 Now I know this is keeping shintaro busy but surely you can moderate one of the telecom track sessions, Shintaro? 15:07:41 Do we have enough sessions there to fill a schedule? 15:08:17 yes! but I'm trying to put some other NTT guys ,better than me 15:08:32 Could I ask you to maybe enter your name with * ? 15:08:40 ok 15:08:46 implying you or someone you find? 15:08:56 it looks less forbidding when it's fuller 15:09:19 mrhillsman are you moderating? 15:10:49 guess he's looking at something else right now. I think we just need to publicize the event a bit more and drum up more moderators 15:10:51 not sure if he's even coming 15:11:00 oh that's right, yes, my mistake. Thanks! 15:11:12 anything else for Tokyo in particular? 15:11:16 mihalis68: mrhillsman will not be able to attend, unfortunately. 15:11:17 I'll send out a request for moderators to the list 15:11:31 should we put in a freeze on topics or do a last call? 15:11:33 I think maybe next week we should start dropping the popular sessions that have moderators onto the schedule 15:11:45 emccormick: Might be nice to have more topics than we can actually cover. 15:12:02 *nod* 15:12:06 Then if we can adjust as needed for audience and availability. 15:12:06 let's ask for final topics for next week so that we can do timetable? 15:12:16 OK will do a call for sessions and moderators 15:12:35 sounds good 15:12:40 #action mccormick to email the community for final topics and moderators 15:12:45 +1 15:12:57 honestly autocomplete ruins my typing of your name every single time 15:13:12 sorry about that 15:13:20 smcginnis are you also going to PTG? 15:13:29 #topic meetup #2 of 2018 15:13:42 emccormick: Yep. Back to back travel FTW! 15:14:05 last week it was discussed that perhaps Amrith (from verizon) could respond on whether they are still interested 15:14:15 I forget who is our link to him from this griup 15:14:17 group 15:14:20 amrith ^ 15:14:35 i thought you both got a "formal" intro and would work together? 15:14:47 smcginnis I need a person to convey LTS / Fast Forward Upgrade discussions from PTG to OPS. Can you manage that in your schedule? 15:14:51 like over a month or so ago 15:14:52 oink 15:14:55 hey 15:14:57 via this channel 15:14:58 hello mrhillsman 15:15:00 hey amrith 15:15:05 reading scrollback 15:15:11 thanks for spotting our smoke signal there 15:15:25 i think it was very much like this intro now lol, chris meet amrith, amrith meet chris 15:15:28 and then an email? 15:15:29 is Verizon still interested in co-hosting an ops meet up later this year? 15:15:31 iirc 15:15:32 amrith: Main question is whether Verizon is interesting in joining in the next ops meetup. 15:15:53 Interesting and willing/able. 15:16:01 *interested 15:16:01 :) 15:16:15 yeah we were "introduced" but then I was also referred to a verizon event planning rep, but that person didn't respond to a second email after the winter break 15:16:18 mihalis68 mrhillsman smcginnis hello. I'm not sure when the intro was but if I recall correctly, I'd connected someone with one of my colleagues in NJ area. yes, I think we are, not sure of the details. 15:16:28 ah, that's what happened. 15:16:40 we can take it up offline; you have my email. 15:16:52 last I know, we were interested in pursuing it. 15:17:29 Ah ok. Maybe I was discouraged too easily there. Someone mentioned they thought there'd been some kind of finance lockdown (not that I'm asking). I will email 15:17:33 thanks 15:17:42 thx 15:17:46 where's next meetup? 15:17:52 possibly NYC 15:17:53 tokyo 15:18:03 then after east coast 15:18:03 Oh yeah tokyo march, then possibly NYC in August 15:18:13 nyc is just a little bit closer than tokyo. but I understand that the japanse food is better in tokyo 15:18:18 that is the "plan" as of today :) 15:18:19 and they have 'real sushi' 15:18:23 hehe 15:18:35 it was good 15:18:46 managed some during the tokyo summit 15:18:48 :) 15:18:49 a gentle reminder that OpenStack Days Nordic is very keen to host your fall Ops meetup 15:19:12 Perhaps we could see if Verizon wants to sponsor that OpenStack Day / Ops Meetup 15:19:45 the procedural snag is that the meet up is "due" to be in north america due to the goal of balancing travel costs across the community 15:20:09 mihalis68: got it. was not aware of that. 15:20:13 but I don't think that is a cast-iron rule, it's just a guideline (someone correct me if I am wrong) 15:20:27 mihalis68: ++ 15:20:28 but travel costs are a pressing issue 15:20:35 Do they have dates yet? 15:20:56 We could change it and do east coast in the spring 15:21:14 Milan was extremely well attended. 15:21:19 I think that's a good idea, personally 15:21:34 anything less than strong encouragement of a willing host feels ... wrong 15:21:53 I think we'd have to put it to a public vote with notification 15:22:01 If you're interested, I could set up a meeting with the Nordic Days manager. 15:22:08 jamesmca_ As long as it's not too close to the summit dates it's doable 15:22:21 ISTR the dates are already known? 15:22:27 We need to keep it mid-wayish if possible 15:22:31 it's not on the site 15:22:32 they haven't announced yet 15:22:36 hey folks - sorry 15:22:40 just says 2018 15:22:42 that's also a good pint emc 15:22:46 looks like it's normally september or october 15:22:49 was dealing with phone failures 15:22:57 hey vw welcome. lively meeting today 15:23:07 we're discussing meet up 2 2018 15:23:28 Us vs Northern Europe ? 15:23:34 there's a proposal to look into OpenStack Days Nordic hosting that "slot" and move USA to spring 2019 15:23:43 I hope its not "versus" 15:23:44 Berlin is fairly late, so it's probably fine 15:23:51 September is better 15:24:15 yeah - it just puts it Europe for the meetup then Europe for the summit 15:24:16 Not like they can change dates for us. It's just a factor to consider for colocating 15:24:17 jamesmca_ we have an actual procedure for such hosting offers. There's an ether pad form to be filled out 15:24:26 true 15:24:32 then US for the next meetup and NA for the following summit 15:24:34 vw I did bring up the goal of balancing travel costs across the community 15:24:41 hmmm yeah 15:25:35 doesn't prevent this from happening 15:25:39 a willing host is a willing host 15:25:42 but it's worth pointing out 15:26:02 When we have solid proposals, let's do a poll 15:26:19 anyone have the boilerplate text ether pad on which proposals are filled out? 15:26:22 like we did with TYO / MIL 15:27:26 #link sample https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2018 15:27:42 its here #link https://etherpad.openstack.org/p/ops-meetup-venue-discuss-2nd-2018 15:27:54 I will start the venue selection ether pad for #2 2018 and we can see if we get acceptable offers 15:28:02 #link https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2018 15:28:06 ah ok 15:28:16 I'm checking with Özgur Bal on dates. Provided it doesn't fall too late in October, I will ask him to fill out the ehterpad form 15:28:20 #action mihalis68 to create the meet up #2 2018 etherpad 15:28:37 ^ its there already 15:28:46 shintaro pasted 15:29:00 ah cool ok 15:29:24 where is PTG going next? 15:29:32 jamesmca_ you copy all the text then paste a second copy and then fill in all the fields 15:29:50 The next PTG is still being decided. 15:29:56 mihalis68 - yes sir, got it :) 15:30:17 typically, the next PTG would be in North America 15:30:28 personally speaking, traveling to openstack days nordic sounds wonderful 15:30:42 but Bloomberg was/is interested in hosting this year 15:31:03 and as mentioned the rotation reaches NA as a "goal" this time, so we'll just have to see which way the community goes 15:31:07 (it's not up to this team!) 15:31:20 Yeah, I haven't set foot in one nordic country. I'm all for that part 15:31:24 well, not to complicate matters, but we've said all along we were open to regionalizing these things... 15:31:25 :) 15:32:36 true ... but you ARE complicating things if we get into that right now 15:32:37 We could do 2 I suppose. Given our recent numbers though, it may rather dilute things. 15:33:05 very valid concern that I share 15:33:06 On the plus side, there do seem to be a lot of OpenStack operators and users in Europe, so that may help raise the numbers there. 15:33:08 we'll see 15:33:15 Milan had really good turn out I thought. 15:33:16 any more on this topic for now? 15:33:17 also mihalis68's head might explode 15:33:23 ha ha 15:33:37 #topic Ops Guide Wiki Conversion 15:34:03 I've started reading it, but still trudging through making notes. 15:34:06 slow going 15:34:11 I'll be brief: we have agreed to move forward with this as a wiki now. I received a good set of initial comments from David Medberry and I am hereby volunteering to update it 15:34:19 yeah it's ... old :| 15:34:41 Sean you have edit rights should we perhaps just coordinate so as to not trample on each other? 15:35:19 for others who may not have openstack wiki edit privilege, you can email me or the operators list and if I see it I'll pick it up 15:35:42 and finally a blog on a bit more about the conversion process is expected soon on SuperUser.openstack.org 15:36:19 I guess that's it for that topic 15:36:21 what are you waiting for feedback to do with it at this point? 15:36:24 mihalis68: Sure, I can help coordinate updates. 15:36:40 ok cool 15:37:16 mrhillsman last week I just wanted a thumbs-up that we're done with the "code-like" source material and it's a good enough conversion to live on purely as a community edited wiki 15:37:20 we have this agreement 15:37:25 i ask because of course it will never be "done" so what state/things need to happen before it is "green lighted" 15:37:35 now the next bit of work is just that it's an old document, lots of out of date info 15:37:50 it's already green lighted a little bit. I think I mentioned it on the mailing list 15:38:08 I'd rather it was somewhat more useful before we really put the spotlight on it 15:38:13 so for now you are basically working out the announcement to be done via SU/ 15:38:27 ok, thx 15:38:36 an article that mentions it is submitted 15:38:54 it's up to the superuser editors as to when it actually posts 15:39:33 if you want to know when you could share it, the answer is now, go ahead! 15:39:51 but people might like to be told that yes we know it's outdated and we're going to update it (at least myself and Sean) 15:40:29 #topic weekly meeting timing 15:40:40 last week we agreed to try this slot for a while 15:40:55 before we send out more announcements on this anyone object? 15:41:03 the one-hour-earlier slot just was not working at all 15:41:44 to be clear, the suggestion was 10am EST always, which unfortunately will move around in UTC 15:41:56 1400 UTC during DST and 1500 UTC for other season, right? 15:42:11 Sean has updated the wiki now, but I think it's always a topic we can come back to to make the meeting maximally useful for those that want to contribute 15:42:25 for us, without DST, we don't really know when is the transit day 15:42:46 so please announce the date before switching 15:42:49 Should we try to use calendar technology? 15:43:16 I can send out Exchange-type invites if that would be helpful. Most systems accept those 15:43:50 but perhaps that's useless? no idea honestly 15:44:17 if the date is fixed, than just putting it on the wiki works 15:44:41 Ok let's aim for that for now. DST should be fixed for 2018 by now I would think 15:45:07 #topic any other business 15:45:18 I throw the floor open to whatever else you hve 15:45:46 nothing more? 15:45:51 I tossed out a request earlier. smcginnis or anyone else that can go to PTG LTS sessions 15:46:05 need someone to take notes to maybe communicate to us 15:46:15 can you take an action for that then Sean? 15:46:21 Sometimes it's difficult to get actual actions out of the etherpads 15:46:52 LTS / FFU 15:47:09 #action smcginnis to liaise between PTG and operators for LTS discussion 15:47:26 On it. 15:47:34 thanks! 15:47:36 Thanks! 15:47:40 ok las call, think we're done 15:47:56 #endmeeting