Tuesday, 2019-01-08

*** VW_ has quit IRC00:05
*** macza has quit IRC00:06
*** VW_ has joined #openstack-operators00:38
*** VW_ has quit IRC00:42
*** ircuser-1 has joined #openstack-operators00:43
*** macza has joined #openstack-operators01:55
*** jamesmcarthur has joined #openstack-operators01:58
*** jamesmcarthur has quit IRC02:03
*** eandersson has joined #openstack-operators02:11
*** macza has quit IRC02:30
*** macza has joined #openstack-operators03:32
*** macza has quit IRC03:36
*** bzhao__ has quit IRC04:26
*** dims has quit IRC04:47
*** dims has joined #openstack-operators04:48
*** dims has quit IRC04:56
*** dims has joined #openstack-operators04:56
*** VW_ has joined #openstack-operators05:40
*** gyee has quit IRC06:24
*** VW_ has quit IRC06:40
*** bzhao__ has joined #openstack-operators06:58
*** rcernin has quit IRC06:58
*** fragatina has joined #openstack-operators07:12
*** fragatina has quit IRC07:33
*** pcaruana has joined #openstack-operators07:42
*** jbadiapa has joined #openstack-operators07:43
*** dtrainor has quit IRC07:45
*** dtrainor has joined #openstack-operators07:46
*** gkadam has joined #openstack-operators07:48
*** slaweq has joined #openstack-operators07:50
*** gkadam is now known as gkadam-afk07:50
*** slaweq has quit IRC07:53
*** slaweq has joined #openstack-operators07:55
*** simon-AS559 has joined #openstack-operators08:08
*** priteau has joined #openstack-operators08:12
*** aojea has joined #openstack-operators08:16
*** gkadam-afk is now known as gkadam08:24
*** derekh has joined #openstack-operators09:33
*** fragatina has joined #openstack-operators10:14
*** priteau has quit IRC10:17
*** fragatina has quit IRC10:21
*** priteau has joined #openstack-operators10:44
*** iOllieN has joined #openstack-operators10:50
*** gkadam has quit IRC12:29
*** simon-AS5591 has joined #openstack-operators12:33
*** simon-AS559 has quit IRC12:37
*** simon-AS5591 has quit IRC12:38
*** trident has quit IRC13:41
*** jamesmcarthur has joined #openstack-operators13:42
*** trident has joined #openstack-operators13:42
*** trident has quit IRC14:03
*** trident has joined #openstack-operators14:03
*** jamesmcarthur has quit IRC14:28
*** mihalis68_ has joined #openstack-operators14:33
*** priteau has quit IRC14:33
mihalis68_reminder : ops meetups team meeting in about 25 minutes14:34
mihalis68_@emcormick14:34
mihalis68_@smcginnis14:34
mihalis68_@spotz14:34
mihalis68_@mrhillsman14:34
mihalis68_@vw14:34
mihalis68_@shintaro14:35
smcginnisThanks mihalis68_14:36
mihalis68_is that how you ping people? I forget14:37
smcginnisYeah, pretty much just stating their nick in the channel works. Most clients will notify on any mentions I think.14:38
mrhillsmano/14:47
*** jamesmcarthur has joined #openstack-operators14:48
*** jamesmcarthur has quit IRC14:50
*** jamesmcarthur has joined #openstack-operators14:50
mihalis68_meeting starts in about 7 minutes. Most urgent item of business is to agree (if possible)  that the next meetup will be as offered by Deutsche Telekom : https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2019-berlin14:53
mihalis68_please review if you have not seen it14:54
*** shintaro has joined #openstack-operators15:00
mihalis68_#startmeeting ops-meetup-team15:01
openstackMeeting started Tue Jan  8 15:01:23 2019 UTC and is due to finish in 60 minutes.  The chair is mihalis68_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: ops-meetup-team)"15:01
openstackThe meeting name has been set to 'ops_meetup_team'15:01
shintarohi15:01
mihalis68_#link https://etherpad.openstack.org/p/ops-meetups-team15:01
mihalis68_hello everyone. Welcome to the first OpenStack Ops Meetups team of 201915:01
smcginniso/15:02
shintarohappy new year!15:02
mihalis68_the exciting news (and challenge) is we have an offer to host a meetup in March15:02
med_\o15:02
mihalis68_Deutsche Telekom proposed to host in Berlin March 6,7 or 7,815:02
mihalis68_Can everyone please look at the proposal if you have not done so already15:03
med_+115:03
shintarogreat!15:03
mihalis68_does everyone agree that the proposal is well-formed and in principle acceptable?15:04
med_nod15:04
smcginnisIt looks like a great offer to me.15:04
shintarothe venue looks great15:04
mihalis68_I'll note that we already established that the timing and region is good15:05
mihalis68_ok, seem non-controversial.15:05
mihalis68_informal vote to approve this as the official 1st ops meetup in 2019? Specifically march 7,8 (right next to the weekend)?15:05
mihalis68_o/15:05
med_o/15:06
* med_ assumes that's a "yea" vote15:06
mihalis68_yes.15:06
mihalis68_no would be15:06
mihalis68_o15:06
mihalis68_|\15:06
mihalis68_or something15:06
med_ah, #startvote15:06
* med_ is pretty sure no one has dissented.15:07
mihalis68_#startvote berlin yes, no15:07
openstackUnable to parse vote topic and options.15:07
mihalis68_yes15:07
mihalis68_dammit15:07
smcginnis#vote yes15:07
mihalis68_#startvote (berlin), yes, no15:08
openstackUnable to parse vote topic and options.15:08
mihalis68_#startvote (berlin) ? yes, no15:08
openstackBegin voting on: (berlin) ? Valid vote options are yes, no.15:08
openstackVote using '#vote OPTION'. Only your last vote counts.15:08
mihalis68_#vote yes15:08
smcginnis#vote yes15:08
med_#vogte yes15:08
shintaro#vote yes15:08
med_#vote yes15:08
med_The former “Central Imperial Telegraph Office” in Berlin-Mitte is the largest and oldest preserved15:08
med_building from the earliest period of telecommunication and therefore part of the city’s identity.15:08
spotzHey all sorry I'm late dogs slipped out the gate and had to call them back15:08
mihalis68_we're voting on whether to formally accept the berlin offer15:09
med_spotz. voting on Berlin DT offer shown here: https://etherpad.openstack.org/p/ops-meetup-venue-discuss-1st-2019-berlin15:09
mihalis68_link above, it seems perfectly cromulent to everyone that has (so far) expressed an opinion15:09
spotzcool15:09
mihalis68_"hash vote yes" or "hash vote no"15:09
spotz#vote yes15:10
mihalis68_ping emccormick15:10
* med_ guesses there is an endvote15:10
mihalis68_ping vw15:10
mihalis68_ping mrhillsman15:10
med_ah, good call15:10
spotzVW did say he was going to try to make this morning15:11
mihalis68_whilst they *race* to respond to the bat signal, I'll note that I shared the link on the mailing list yesterday also15:11
med_yep. that's when I looked at the proposal.15:12
mihalis68_ok thanks, then it did actually land on the list15:12
med_for once, I did my homework and showed up.... That's a 2019 win.15:12
mihalis68_does anyone feel we need to prolong the vote here? It seems unanimous of those responding, and also well notified15:13
mihalis68_#endvote15:13
openstackVoted on "(berlin) ?" Results are15:13
openstackyes (5): shintaro, mihalis68_, med_, smcginnis, spotz15:13
mihalis68_cool, we have a venue15:13
mihalis68_ok. I brought this up to top of meeting in case people need to dash15:13
mihalis68_forgot a topic15:14
mihalis68_#topic actions15:14
*** openstack changes topic to "actions (Meeting topic: ops-meetup-team)"15:14
mihalis68_please self-report on outstanding actions you had (honor system)15:14
mihalis68_I had various actions to notify the community about this proposal : COMPLETE15:14
mihalis68_also stuff related to the ops docs initiative15:14
mihalis68_not quite there, but I did get myself a dev environment where I can build them!15:15
mihalis68_outstanding is to find a time for a monthly catch-up on those15:15
smcginnisMaybe an action... I updated https://wiki.openstack.org/wiki/Operations/Meetups but anyone feel free to improve that.15:15
mihalis68_ah, important point : #action mihalis68 to notify the host (DT) that we accepted the proposal15:15
mihalis68_oh, nice, thanks smcginnis15:16
mihalis68_I feel sure I said I'd do it ... then didn't :(15:16
mihalis68_any more action talk?15:16
mihalis68_#topic berlin15:16
*** openstack changes topic to "berlin (Meeting topic: ops-meetup-team)"15:16
* med_ scrolled through the etherpad a ways looking for med_ actions but didn't see any (none, and none outstanding)15:17
mihalis68_#agreed it's going to be berlin, March 7th, 8th (as per irc poll just now)15:17
med_fyi, I haven't made this meeting in a while, just a shout that it was great to  see y'all in Berlin last year.15:17
mihalis68_out of interest, who here expects to be able to make it?15:17
mihalis68_likewise!15:17
med_I can't get sponsorship and will likely not send myself to this one.15:18
mihalis68_I expect to go to berlin. i happen to have heard that it's difficult to make, also, for emccormick and smcginnie15:18
mihalis68_smcginnis, sorry for typo15:18
spotzI'm always doubtful until you see me15:18
mihalis68_heh15:19
mihalis68_so I'll volunteer to get the necessary planning documents started15:19
shintaroI need to check my schedule but I will try to go.15:19
mihalis68_they are the topic planning etherpad, the agenda google doc and perhaps a list of items to sponsor (that's up to DT largely)15:19
smcginnisI haven't entirely given up hope on going, but will still try to help however I can if I am not able to be there in person.15:19
mihalis68_#action mihalis68 to start the ops meetups planning docs and to share their links with the community15:20
mihalis68_#action with the docs avaiable, mihalis68 to invite the UC to bring material into them from previous events15:20
spotzLike Sean will help plan and stuff no matter what15:20
mrhillsmanapologies I'm back15:20
mihalis68_(this was a plan agreed in Denver to aim for better program quality, usefulness, continuity etc)15:21
med_mrhillsman, berlin site approved.15:21
mihalis68_welcome back15:21
mrhillsmanok cool, I'll still help with wrangling moderators15:21
med_ah, he probably has scrollback.15:21
mihalis68_from past events, the difficult part is achieving a high quality technical agenda with agreed moderators that will actually attend15:21
mrhillsmanin the same boat as sean on travel approval15:21
mihalis68_so even though we have two months, we're once again not blessed with a ton of time15:21
mihalis68_(Xmas/NYE break being 3 weeks this time!)15:22
mihalis68_this is why I'm going to do a frontal assault on easy doc chores and try to get this moving way faster at this stage than past events15:22
smcginnisProbably the sooner we get registration going and start finalizing attendee numbers and agenda items, the better.15:22
mihalis68_yeah15:22
mihalis68_could someone own liaising with foundation on next steps? They may be able to help with an eventbrite for this since we do plan to charge the $20 again I believe15:23
spotzmihalis68_: I can hit them up15:23
mihalis68_thank you!15:23
spotzNP15:23
*** markvoelker has joined #openstack-operators15:23
mihalis68_#action spotz to let the foundation know we agreed the berlin proposal and that we'd like an eventbrite where they charge the nominal fee ($20) which is normally put into some signage15:24
mihalis68_any more for now on berlin?15:25
mihalis68_another thing we normally do get into discussing is: possible social in the evening on day 115:25
mihalis68_can wait to get into that until more people know whether they will go15:26
med_+115:26
mihalis68_I think that's enough about berlin15:26
mihalis68_#topic meetup 2, 201915:26
*** openstack changes topic to "meetup 2, 2019 (Meeting topic: ops-meetup-team)"15:26
mihalis68_brief update: we (Bloomberg) are hoping to make a proposal to host a meetup some time approx midway between denver and china summits in NYC15:26
*** markvoelker has quit IRC15:26
mihalis68_it will most likely be at Bloomberg global HQ, 731 Lexington Avenue15:27
med_+10015:27
*** markvoelker has joined #openstack-operators15:27
shintarogreat news!15:27
*** markvoelker has quit IRC15:27
smcginnisThat should be great!15:27
mihalis68_the proposal anticipates a room for about 100, with lunch provided as well as a big screen, wifi, power (the usual amenitied)15:27
* med_ will make that one with FFMiles if necessary15:28
mihalis68_one thing I'll have to work out is we have our own conference attendee management system, can't use Eventbrite15:28
mihalis68_I've asked Sean and Erik to hold us to normal no-BS standards here, and to not hold back15:28
mihalis68_so if you need to call me or us full of it, say it out loud or rely on sean's mad diplomacy skills15:29
med_I think the line posted at 8:28 by mihalis68 is a complete proposal.15:29
smcginnis:)15:29
med_8:28 MST15:29
mihalis68_I can't officially confirm it yet15:29
mihalis68_funnily enough, the community based no-vendor stance is the only way we could possibly get this into a bloomberg office15:29
med_curious.15:30
med_but makes some sense.15:30
mihalis68_there's by-laws about what can be done on-prem and they are particularly strictly against anything which looks like approving of a particular vendor15:31
med_nod, paper/news/reporting needs to stay independent15:31
mihalis68_bloomberg is a big news org, buys a lot of gear and has some political sensitivies in some places. I think it does make sense personaly, but you can rely on sean to keep us in line!15:32
med_probably even more so if you influence stock prices15:32
mihalis68_I'd like people to think about a possible dedicated track for that meetup15:32
mihalis68_we might like openstack in financial institutions (or we may not, hard to say, wouldn't be up to just me)15:33
smcginnisGood point - with how we've been trying to have themes based on the region, what should we do for the NY theme?15:33
mihalis68_I do have some interest in meetups from some companies in that sphere (other than us) already15:33
smcginnis+1 for financial. That would make a lot of sense.15:33
mihalis68_yeah15:33
med_FiServ Ops Meeetup, +115:33
mihalis68_excellent. Appreciate the feedback15:34
mihalis68_I think that's enough about a possible event in september15:34
mihalis68_we can be brief on the rest15:34
med_I suspect vm-ified containers (ala Kata) to be a big Ops topic throughout the year. My crystal ball has a giant crack though, ymmv.15:34
mihalis68_for ops docs (not solely an item for the ops meetups team) I got a dev env up on a misc ubuntu install, but it was harder than the docs imply15:35
mihalis68_should I write that up somewhere? the tox toolchain has more dependencies than it claims15:35
smcginnismihalis68_: Would be great to at least get your notes captured somewhere.15:35
mihalis68_alright15:35
med_sure, write up somewhere and send out to openstack-discuss (or whatever the new maillist name is)15:35
mihalis68_#action mihalis68 to capture a "how-to" on ops docs dev env15:35
mihalis68_I pretty much wiped my chromebook 10 times before I got it15:36
med_not to try and change topics, but we also need to discuss if we're having anything at PTG May 2-415:36
mihalis68_(not a big deal given how slick chromebooks are at that)15:36
med_mihalis68_, holy crap. That's bad.15:36
mihalis68_part of it is me not being a python person15:36
mihalis68_PTG is a fine topic15:37
mihalis68_#topic ops involvement at PTG, May 2-415:37
*** openstack changes topic to "ops involvement at PTG, May 2-4 (Meeting topic: ops-meetup-team)"15:37
mihalis68_admission: have not given it any thought15:37
med_brb, doorbell15:37
mihalis68_PTG is quite near in time to the summit, right?15:38
mihalis68_is it immediately after? Or partially overlapping?15:38
mihalis68_looks like immediately afterwards15:39
spotzI think the 3 days right after15:39
shintaroright, but we have the Forum during the Summit so Ops topics could go there15:39
spotzyes15:39
med_it's summit adjacent15:39
med_summit is 29-1may15:39
med_so not sure where Ops Topics and Ops Meetup should go/get distributed15:40
med_fwiw, the Fdn has asked me about groups/teams/etc in Denver for summit planning.15:40
med_but also note, I'm not a denver native. If the "social" time at the brewpub/brewery worked last time, should just be repeated.15:41
mihalis68_summit April 29-may 1 inclusive, PTG May 2-4 incl.15:41
med_mihalis68_, I'm not sure about the overlap. The dates are technically separate.15:41
med_yep15:41
smcginnisSeparate events. It's going to be a long week.15:41
med_so not sure what time/space/etc we need to plan for.15:41
med_yes.15:41
mihalis68_I'd like people to state their own opinions on ops attendance at PTG15:41
mihalis68_I think people know my feelings15:41
mihalis68_could color the debate15:42
med_I'm fine with OPS at some point in DEN in Apr/May timeframe. Not too particular on which end of the week.15:42
med_I will likely be on-site for most/all of that week unless I get strongly re-directed by work.15:42
* med_ got pulled away last time mid week due to "re-directed-ness"15:43
mihalis68_I'll rehash the context briefly15:43
smcginnisProbably hard for folks attending to plan. Would it be better to stick to the Forum during the Summit? Or maybe a day or two at the forum, a day or two at the PTG to try to get different folks involved?15:43
mihalis68_originally ops meetups were for operators. PTG was for dev teams. Little overlap15:43
mihalis68_the most recent PTG saw a change to its definition to be inclusive of operators but also to try to serve as a traditional ops meetup15:44
mihalis68_it was good at the firs thing, mixed at the second (my opinion)15:44
mihalis68_now however it's back in the same time of year as summit15:44
smcginnisSome conversations benefitted from having more dev focused folks in the room, but not sure it would be worth the extra travel time for everyone.15:44
shintaro+1 to stick to the Forum if its still there.15:45
mihalis68_yeah, my own opinion is precisely "not sure" about staying for PTG (assuming I'm at the summit, which is a good bet)15:45
smcginnisI have a feeling just focusing on having a few good sessions during the Summit/Forum will be better than trying to coordinate something along with the PTG.15:45
mihalis68_yeah15:45
mihalis68_strongly agree15:45
mihalis68_my only hesitation is I feel like we agreed with a plan to try to get ops to ptg15:46
smcginnisGetting dev attention while they are trying to work out their own stuff was a challenge too, so focusing on the PTG has a lot of risk of not paying off.15:46
mihalis68_are we saying that that didn't really work out and we're back to the old separation (but we do have forum nowadays)15:46
smcginnisI think it was a good experiment to see if it could work. Maybe it still could have as a stand alone event.15:46
mihalis68_alright. This will continue to be discussed at future ops meetups, no doubt15:47
smcginnisWe could maybe have one option day the first day of the PTG for an ops focused track for those that are able to stick around for it?15:47
mihalis68_regarding the social: we'll be even nearer the craft bar/pool hall15:47
smcginnisYeah, we might have to let this simmer a bit15:47
med_nod.15:47
mihalis68_it was fine from my POV15:47
mihalis68_time's moving along, so15:48
mihalis68_#topic any other business15:48
*** openstack changes topic to "any other business (Meeting topic: ops-meetup-team)"15:48
smcginnisNothing from me.15:48
spotzI do like the idea of doing just the first day if folks thought it a good idea15:48
mihalis68_is day 1 of that PTG officially the more cross-group-focused period?15:48
mihalis68_SIGs for example?15:49
med_no idea15:49
spotzI don't think it's planned that far yet hence asking for who will be there and what they need15:49
shintaroSIGs had a session at the Forum also, so it may depend on how the Foundation will organize the whole event15:50
mihalis68_alright - leave that to a later discussion15:50
mihalis68_if it is, however, then I also like the idea of suggesting ops consider PTG day 115:50
mihalis68_however will they need a full PTG ticket for that?15:50
mihalis68_I just nipped into the PTG FAQs and they will need a cleanup, they are out of date, e.g.15:51
mihalis68_https://www.irccloud.com/pastebin/u144f4VL/15:51
mihalis68_who can own taking this back to the owners?15:51
mihalis68_ok I'll email jimmy M then I guess15:52
mihalis68_#action mihalis68 to email foundation staff about outdated language in PTG FAW15:52
mihalis68_FAQ, darnit15:52
mihalis68_any more input from anyone? (we've achieved a lot!)15:53
mihalis68_seems like I've lost the audience, jokes not working, people leaving out the back :)15:53
mihalis68_thanks all!15:53
mihalis68_#endmeeting15:53
*** openstack changes topic to "Topics related to operating OpenStack infrastructure | Mailing list: http://lists.openstack.org/pipermail/openstack-discuss/"15:53
openstackMeeting ended Tue Jan  8 15:53:43 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_team.2019-01-08-15.01.html15:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_team.2019-01-08-15.01.txt15:53
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2019/ops_meetup_team.2019-01-08-15.01.log.html15:53
smcginnisTHanks!15:53
med_heh15:54
med_sorry, multi tasking.15:54
med_Thanks mihalis68_15:54
shintarothank you15:54
mihalis68_had my own motivations, have another GD meeting to scurry to15:54
*** shintaro has quit IRC15:55
spotzThanks all15:57
*** pcaruana has quit IRC16:20
*** gyee has joined #openstack-operators16:38
*** VW_ has joined #openstack-operators16:44
*** macza has joined #openstack-operators16:59
*** VW_ has quit IRC17:08
*** iOllieN has quit IRC17:13
*** jamesmcarthur has quit IRC17:15
*** jamesmcarthur has joined #openstack-operators17:19
*** jamesmcarthur has quit IRC17:32
*** jamesmcarthur has joined #openstack-operators17:45
*** jamesmcarthur has quit IRC17:56
*** derekh has quit IRC18:00
*** jamesmcarthur has joined #openstack-operators18:02
*** elenalind has joined #openstack-operators18:19
*** VW_ has joined #openstack-operators18:20
*** VW_ has quit IRC18:21
*** mihalis68_ has quit IRC18:23
*** VW_ has joined #openstack-operators18:28
*** VW_ has quit IRC18:34
*** VW_ has joined #openstack-operators19:37
*** jamesmcarthur has quit IRC19:41
*** jamesmcarthur has joined #openstack-operators19:42
*** VW_ has quit IRC19:44
*** VW_ has joined #openstack-operators19:45
*** VW_ has quit IRC19:49
*** VW_ has joined #openstack-operators19:50
*** jamesmcarthur has quit IRC19:52
*** jamesmcarthur has joined #openstack-operators19:55
*** VW_ has quit IRC20:06
*** jamesmcarthur_ has joined #openstack-operators20:23
*** jamesmcarthur has quit IRC20:26
*** elenalind has quit IRC20:27
*** fragatina has joined #openstack-operators20:41
*** fragatina has quit IRC20:41
*** fragatina has joined #openstack-operators20:41
*** fragatina has quit IRC20:45
*** fragatina has joined #openstack-operators20:51
*** fragatina has quit IRC20:59
*** jbadiapa has quit IRC21:10
*** slaweq has quit IRC21:28
*** aojea_ has joined #openstack-operators21:42
*** aojea_ has quit IRC21:43
*** aojea__ has joined #openstack-operators21:43
*** aojea__ has quit IRC21:54
*** fragatina has joined #openstack-operators21:56
*** aojea_ has joined #openstack-operators21:56
*** fragatina has quit IRC21:56
*** fragatina has joined #openstack-operators21:57
*** fragatina has quit IRC22:08
*** slaweq has joined #openstack-operators22:23
*** rcernin has joined #openstack-operators22:53
*** aojea_ has quit IRC23:29
*** jamesmcarthur_ has quit IRC23:43
*** jamesmcarthur has joined #openstack-operators23:45
*** jamesmcarthur has quit IRC23:50

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