Tuesday, 2018-12-04

*** emccormickva has quit IRC00:02
*** VW_ has quit IRC00:02
*** emccormick has joined #openstack-operators00:10
*** emccormickva has joined #openstack-operators00:16
*** emccormick has quit IRC00:19
*** jamesmcarthur has joined #openstack-operators00:26
*** VW_ has joined #openstack-operators00:30
*** jamesmcarthur has quit IRC00:31
*** VW_ has quit IRC00:35
*** VW_ has joined #openstack-operators00:43
*** VW_ has quit IRC00:48
*** jamesmcarthur has joined #openstack-operators01:24
*** jamesmcarthur has quit IRC01:34
*** jamesmcarthur has joined #openstack-operators01:35
*** takamatsu has quit IRC01:37
*** jamesmcarthur has quit IRC01:38
*** jamesmcarthur has joined #openstack-operators01:49
*** jamesmcarthur has quit IRC01:51
*** jamesmcarthur has joined #openstack-operators01:53
*** jamesmcarthur has quit IRC01:57
*** jamesmcarthur has joined #openstack-operators02:04
*** jamesmcarthur has quit IRC02:07
*** jamesmcarthur has joined #openstack-operators02:07
*** gyee has quit IRC02:14
*** jamesmcarthur has quit IRC02:42
*** jamesmcarthur has joined #openstack-operators02:45
*** mriedem_away has quit IRC03:58
*** jamesmcarthur has quit IRC04:11
*** jamesmcarthur has joined #openstack-operators04:39
*** emccormickva has quit IRC05:28
*** ahosam has joined #openstack-operators06:22
*** jamesmcarthur has quit IRC06:47
*** aojea has joined #openstack-operators06:50
*** takamatsu has joined #openstack-operators06:53
*** aojea has quit IRC07:04
*** pcaruana has joined #openstack-operators07:10
*** ahosam has quit IRC07:21
*** rcernin has quit IRC07:38
*** takamatsu has quit IRC08:15
*** gkadam has joined #openstack-operators08:22
*** trident has quit IRC08:31
*** trident has joined #openstack-operators08:32
*** jamesmcarthur has joined #openstack-operators08:44
*** takamatsu has joined #openstack-operators08:46
*** jamesmcarthur has quit IRC08:50
*** ahosam has joined #openstack-operators08:57
*** jamesmcarthur has joined #openstack-operators08:58
*** jamesmcarthur has quit IRC09:02
*** takamatsu has quit IRC09:14
*** takamatsu has joined #openstack-operators09:16
*** ahosam has quit IRC09:22
*** priteau has joined #openstack-operators09:31
*** aojea has joined #openstack-operators09:32
*** jamesmcarthur has joined #openstack-operators09:33
*** jamesmcarthur has quit IRC09:38
*** takamatsu has quit IRC09:49
*** takamatsu has joined #openstack-operators09:50
*** derekh has joined #openstack-operators09:51
*** takamatsu has quit IRC10:13
*** ahosam has joined #openstack-operators10:29
*** electrofelix has joined #openstack-operators10:34
*** jamesmcarthur has joined #openstack-operators10:34
*** takamatsu has joined #openstack-operators10:50
*** takamatsu has quit IRC11:04
*** takamatsu has joined #openstack-operators11:05
*** ahosam has quit IRC11:05
*** ahosam has joined #openstack-operators11:07
*** vabada has joined #openstack-operators11:59
*** vabada has joined #openstack-operators12:00
*** ahosam has quit IRC12:19
*** jamesmcarthur has quit IRC12:39
*** ahosam has joined #openstack-operators12:47
*** ahosam has quit IRC13:01
*** mgariepy has quit IRC13:03
*** mgariepy has joined #openstack-operators13:08
*** aojea_ has joined #openstack-operators13:28
*** irclogbot_2 has quit IRC13:38
*** irclogbot_2 has joined #openstack-operators13:40
*** priteau has quit IRC13:40
*** priteau has joined #openstack-operators13:44
*** jamesmcarthur has joined #openstack-operators13:46
*** aojea_ has quit IRC13:47
*** jamesmcarthur has quit IRC13:51
*** aojea_ has joined #openstack-operators14:15
*** irclogbot_2 has quit IRC14:16
*** trident has quit IRC14:18
*** trident has joined #openstack-operators14:21
*** mriedem has joined #openstack-operators14:33
*** aojea_ has quit IRC14:33
*** aojea_ has joined #openstack-operators14:40
openstackgerritMerged openstack/arch-design master: Update repo name and links; remove obsolete options  https://review.openstack.org/62169714:51
*** irclogbot_2 has joined #openstack-operators14:53
*** VW_ has joined #openstack-operators15:01
*** mihalis68_ has joined #openstack-operators15:03
mihalis68_o/15:03
mihalis68_anyone around?15:03
*** emccormickva has joined #openstack-operators15:04
emccormickvao/15:04
mihalis68_#startmeeting ops-meetup-team15:05
openstackMeeting started Tue Dec  4 15:05:01 2018 UTC and is due to finish in 60 minutes.  The chair is mihalis68_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:05
*** openstack changes topic to " (Meeting topic: ops-meetup-team)"15:05
openstackThe meeting name has been set to 'ops_meetup_team'15:05
mihalis68_#link https://etherpad.openstack.org/p/ops-meetups-team15:05
mihalis68_please add your name to the attendees list15:05
mihalis68_#topic actions15:05
*** openstack changes topic to "actions (Meeting topic: ops-meetup-team)"15:05
mrhillsmano/15:05
mihalis68_I fwded the proposal from DT to the mailing list earlier today15:05
emccormickvasaw it thanks!15:06
mihalis68_and I have finally got word that my employer Bloomberg can't make any offer for that time slot (our frankfurt facility will still be in renovation)15:06
*** emccormickva is now known as emccormick15:06
mihalis68_so I think we are in the happy position of having just one good proposal for the next meetup15:06
emccormickstupid thing changing my nic all willy nilly15:06
emccormickHow long do we want to let the RFC sit out there before finalizing it?15:07
mrhillsmani think we said one or two more weeks for alternate proposals before giving DT the green light?15:07
mihalis68_yes we were talking about a cut-off date15:07
mrhillsmani did not remember the exact day but pretty sure it was before the end of the year15:07
mihalis68_end of year seems reasonable (and so much closer than even a week ago!)15:07
mrhillsmanso DT or anyone else for that matter has plenty of time to get things together15:07
mihalis68_in my email I asked for feedback here, or via contacting the meetups team and shared the link to our team wiki page15:08
emccormickJanuary 8th would be our first meeting of next year. It feels kind of overly close to the event, but I dunno.15:09
mihalis68_the other action I had was to set up a regular meeting for ops docs SIG. Did not get that done yet15:09
mihalis68_I'd prefer to lock it in ASAP to allow some time for the prep work - topics, moderators, sponsors15:10
mrhillsmanyeah, i think waiting too long will put us in a tailspin we do not want15:10
mihalis68_smcginnis had an action to look into moving the arch guide into the ops docs sig. I see lots of activity there, it's definitely happening15:10
mrhillsmanespecially if there is no alternate in the next couple weeks15:10
mrhillsmani think that is plenty of time for someone to at least propose an alternate15:11
mihalis68_far from a tailspin, I have a goal to do much better this time than we did for Denver15:11
mrhillsmanagreed15:11
mrhillsmanor even before denver ;)15:11
mihalis68_How about this: we tell the mailing list that we currently expect to confirm the DT offer by end of year unless there's a reason not to15:11
mihalis68_yeah, stretch goal of best meetup ever15:12
mihalis68_however some of the past ones were really good, so that's not so easy15:12
mihalis68_how do people feel about the tentative deadline of end of year?15:12
mihalis68_note that DT has offered two sets of dates15:12
mrhillsmanjust my opinion of course - two weeks :)15:12
spotzhey all15:13
mrhillsmanthere is a lot to make it successful15:13
mihalis68_morning!15:13
mrhillsmano/ spotz15:13
emccormicko/15:13
emccormickI think 2 weeks from now is sufficient honestly15:13
mihalis68_spotz we're discussing how quickly to lock in the deutsche telekom offer15:13
mrhillsmanhopefully with VW_ suggestion of getting thread re etherpads from Forum we can have some good session seeding15:13
emccormickWe put out the call for proposals like a month ago15:13
*** jamesmcarthur has joined #openstack-operators15:14
mrhillsmanbut wrangling moderators and giving folks enough time to get approval/visa/etc is key too15:14
mihalis68_so confirm official in this meeting on 2018-12-18 unless there's a good reason not to (like a  new competing offer)15:14
emccormickcall it at the meeting on 12/1815:14
mrhillsmanagain, just my opinions15:14
emccormick*nod*15:14
mrhillsman++15:14
spotzThat sounds good.15:15
mihalis68_#agreed everyone present seemingly likes the plan to finish venue selection 12/18 unless new facts appear15:15
mrhillsmanvote mihalis68_ ?15:15
mrhillsmannvm hehe15:15
mihalis68_oh I haven't heard any opposition15:15
emccormickAlso it gives people the chance to talk their significant others into letting them go while plying them with eggnog and expensive gifts :D15:15
mrhillsmanno no, you're good, much easier :)15:15
mihalis68_any more updates on topic: actions?15:15
mihalis68_ok15:15
mihalis68_#topic ops docs15:15
*** openstack changes topic to "ops docs (Meeting topic: ops-meetup-team)"15:15
mrhillsmansmcginnis may still be out15:16
*** mriedem is now known as mriedem_afk15:16
mihalis68_as mentioned, smcginnis has been busy on this and is appropriating the arch guide into the ops docs sig15:16
emccormickI've been slowly reading and trying to take notes15:16
mrhillsmanhe had to travel yesterday15:16
mrhillsmanbut has been doing things15:16
mihalis68_yep. i don;t think there are any more updates on ops docs except to say that looks like splitting off from ops meetups team15:16
mihalis68_I'm going to be working on that when I can15:16
mihalis68_(when not fixing angry ceph clusters :)15:17
emccormickhehe15:17
mihalis68_#topic 2019 meetups15:17
emccormickOne docs question on the ops guide for you15:17
*** openstack changes topic to "2019 meetups (Meeting topic: ops-meetup-team)"15:17
mihalis68_oops, go ahead15:17
emccormickwe talked at one of the forum sessions a while ago about lopping off a large chunk of the beginning that had to do with deployment tools and replacing it with a short list of references15:17
mihalis68_yes15:18
emccormickI am trying to figure out exactly what that would look like, but before I spend time on it, are there any objections?15:18
mihalis68_I'm in favor, as how to deploy has become a huge topic15:18
emccormickit would be a fairly large patch15:18
mihalis68_and intertwined with architecture now15:18
emccormickIt's just always seemed bizarre to have a doc specifically stated to be about day 2 ops have a giant, and out of date, section about deployment15:19
mihalis68_since if you want to deploy on k8s you have some choices, if you want containerized but not full k8s it's these other things (with some overlap) and then there's non-containerized, traditional, triple-O etc15:19
mihalis68_you kind of have to make a big upfront "how will my openstack run" choice before you can choose your installation stuffs now15:19
mihalis68_I agree15:19
emccormickI intend to cross-reference to install guides, architecture guide, etc15:19
mihalis68_sounds good to me15:19
emccormickbut just as a pointer to where to go for that info15:19
emccormickk15:20
*** VW_ has quit IRC15:20
mihalis68_I'm itching to write the opinionated guide on building you an openstack for great good15:20
emccormickI'm going to work on it over the holiday I think since I'll be bored at my in-laws for days on end ;)15:20
mihalis68_excellent15:20
mihalis68_ok, on to 2019 meetups for real now15:20
mihalis68_summary of #1:15:21
mihalis68_DT has proposed two dates. We need to pick one set of dates, but otherwise we are likely to accept that offer officially on 12/1815:21
mihalis68_this means travelling to berlin again15:21
mihalis68_which is not quite ideal15:21
mihalis68_however, Europe is the expected region for the next meetup, and berlin is the only offer on the table15:21
mihalis68_it works for me, but I'll be hoping for no snow-related travel chaos on the way home this time15:22
mihalis68_how should we proceed on the question of which date?15:22
mihalis68_I thought about doing a poll, however the last poll we did had a tiny response15:23
emccormickI'm scanning air fares for one15:23
mihalis68_I think we might do better to study the two time slots and see if one has reasons to be better15:23
mihalis68_for example: adjacency to any other vaguely related event15:23
mihalis68_I don't think we can nor should we try to decide today, but how about we all take an action to look into which set of dates is better?15:24
mihalis68_yes? No?15:24
mrhillsman++15:24
mihalis68_<tap> <tap> this thing on?15:24
emccormicksounds good15:25
spotzI'd need a sponsor to go:( But I'll help plan15:25
emccormickdo eet15:25
mihalis68_ok. emccormick is looking, mrhillsman says ++ and I suggested it15:25
mihalis68_#action everyone look into pros and cons of the two date proposals from Deutsche Telekom15:25
mihalis68_meetup #2 will be (potentially) a single-day at CERN15:26
mihalis68_Belmiro Moreira is the contact there15:26
mihalis68_I forget what the next steps are there15:26
shubjeroAny operators here turn off intel's hyperthreading because of spectre/meltdown concerns?15:26
mihalis68_hello shubjero: we don't turn it off yet, we're probably jumping to new cpus once our security people decide15:27
mihalis68_and by the way we're having a meeting here, but it's fine! :)15:27
shubjerooh sorry15:27
emccormickshubjero No, never15:27
emccormick:)15:27
mihalis68_the second official meetup ("midcycle" as we used to call them) is aimed at North America15:27
mihalis68_I am formally proposing internally to host it in NYC15:27
emccormickOne thing on the DT meetup, we need to make sure to get a DT person in these meetings once they're approved15:27
mihalis68_most likely at Bloomberg headquarters15:27
spotzAny luck with that?15:28
mihalis68_yes, agreed15:28
mihalis68_luck with which?15:28
spotzInternal saying yes:)15:28
spotzemccormick: Reach out to Frank15:29
mihalis68_if the question is about Bloomberg, at this stage I have a ticket in suggesting it, and approval to mention that we are working on it, however I don't have a booking on the mega "multi-purpose room" yet15:29
mihalis68_I'm due to follow-up with the authorities on all that soon15:29
emccormickspotz will do.15:29
mihalis68_#action mihalis68 to email fkloeker that we aim to agree the DT proposal on 12/18 and also that we are currently looking at which dates work best15:30
mihalis68_#action mihalis68 to push forward on bloomberg-internal paperwork for a possible hosting offer for meetup 2 201915:31
mihalis68_Another action I forgot to mention was regarding a SuperUser article about the mailing list merger15:31
mihalis68_a mailing list thread happened and AFAIK it was agreed and will happen15:32
shubjeroWhat's involved in hosting ops meetups? We have been hosting openstack toronto meetups for all of 201815:32
mihalis68_fungi noted that the two announcements already have all the technical info such an article would need15:32
mihalis68_shubjero there's a page listing how it works, let me dig it out15:32
mihalis68_#link https://wiki.openstack.org/wiki/Operations/Meetups it's here "how meetups are planned"15:33
mihalis68_this team mostly focuses on a couple of international meetups for the entire community15:33
shubjeromihalis68_: thanks15:34
mihalis68_so far it's run ones in : NYC, Milan, Mexico City, Denver and Tokyo15:34
mihalis68_the question of does the meetups team have involvement in regional ones is fairly open15:34
mihalis68_but one thing we'd love to do is connect more with regional groups, as the old openstack-operators mailing list really started to go deathly quiet recently15:35
mihalis68_we're hoping that the new unified openstack-discuss list will work better15:35
mihalis68_are your community members subscribed to that?15:35
shubjeroLooks like the venue criteria on the openstack site is too much for our particular venue. Toronto typically has a pretty low turnout for meetups unfortunately. What drives attendance is flashy titles like kubernetes and ai :).15:37
mihalis68_if you have any thoughts on that shubjero feel free to get in touch with us (ops meetups team). Contact details here: https://wiki.openstack.org/wiki/Ops_Meetups_Team or this meeting every week at 10am EST here15:37
shubjeroSome are, yes and the merging of mailing lists was smart because lots of ops questions made it to openstack mailing list instead of openstack-operators and visa versa15:37
mihalis68_ok that's good to know15:38
mihalis68_I feel sure the meetups team could help out a little with regional ones, getting the word out if nothing else, and perhaps you might see one or two travel (Toronto is not THAT far from here!)15:38
mihalis68_I can sense that this meeting is nearly over. I know everyone's busy15:39
mihalis68_so15:39
mihalis68_#topic any other business15:39
*** openstack changes topic to "any other business (Meeting topic: ops-meetup-team)"15:39
emccormickNothing from me.15:39
mihalis68_as usual i'd like to know if this time slot still works for everyone15:39
spotzI'm good15:39
mihalis68_it's kind of a self-defeating question, as I'm asking *only those who attend* :)15:40
mihalis68_so if you hear rumors that VW or Shintaro need to move the slot, pass it on!15:40
spotzhehe, I periodically do a doodle poll for D&I15:40
emccormickshubjero our names and emails are on here if you have questions in the interim15:40
emccormickhttps://wiki.openstack.org/wiki/Ops_Meetups_Team15:40
mihalis68_maybe I should put this to the new combined mailing list?15:40
emccormickHappy to help ops events ideas however we can15:41
mihalis68_#action mihalis68 to ask for confirmation of ops meetups team meeting frequency and cadence on new openstack-discuss list15:41
mihalis68_ok final call15:41
mihalis68_a good chair always finishes at first opportunity15:41
mihalis68_#endmeeting15:42
*** openstack changes topic to "Topics related to operating OpenStack infrastructure | Mailing list: http://lists.openstack.org/pipermail/openstack-discuss/"15:42
openstackMeeting ended Tue Dec  4 15:42:16 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:42
mihalis68_thanks all!15:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-12-04-15.05.html15:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-12-04-15.05.txt15:42
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-12-04-15.05.log.html15:42
*** pcaruana has quit IRC16:12
*** electrofelix has quit IRC16:27
*** gkadam has quit IRC16:28
openstackgerritFilippo Inzaghi proposed openstack/osops-tools-monitoring master: Change openstack-dev to openstack-discuss  https://review.openstack.org/62241616:35
*** gyee has joined #openstack-operators16:47
*** mriedem_afk is now known as mriedem16:50
*** VW_ has joined #openstack-operators17:05
*** takamatsu has quit IRC17:06
*** pcaruana has joined #openstack-operators17:12
*** VW_ has quit IRC17:13
*** aojea_ has quit IRC17:23
*** derekh has quit IRC17:46
*** pcaruana has quit IRC17:56
*** ahosam has joined #openstack-operators18:56
*** ahosam has quit IRC19:19
*** ekcs has joined #openstack-operators19:49
*** jamesmcarthur has quit IRC19:58
*** aojea has quit IRC19:59
*** ahosam has joined #openstack-operators20:36
*** aojea has joined #openstack-operators20:39
*** takamatsu has joined #openstack-operators20:44
*** aojea has quit IRC21:43
*** aojea has joined #openstack-operators22:17
*** ahosam has quit IRC22:19
*** slaweq has quit IRC22:20
*** blake has joined #openstack-operators22:27
*** takamatsu has quit IRC22:29
*** emccormick has quit IRC22:33
*** rcernin has joined #openstack-operators22:34
*** slaweq has joined #openstack-operators22:36
*** slaweq has quit IRC22:42
*** mriedem has quit IRC22:44
*** rcernin_ has joined #openstack-operators22:45
*** rcernin has quit IRC22:45
*** aojea has quit IRC22:50
*** slaweq has joined #openstack-operators22:53
*** priteau has quit IRC23:03
*** slaweq has quit IRC23:10
*** rcernin_ has quit IRC23:12
*** etp has quit IRC23:12
*** etp has joined #openstack-operators23:13
*** rcernin has joined #openstack-operators23:13
*** aojea has joined #openstack-operators23:42

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