Tuesday, 2018-06-19

*** chyka has joined #openstack-operators00:35
*** masber has joined #openstack-operators01:27
*** jamesmcarthur has joined #openstack-operators01:30
*** dbecker has quit IRC01:30
*** jamesmcarthur has quit IRC01:30
*** jamesmcarthur has joined #openstack-operators01:31
*** gyee has quit IRC01:33
*** jamesmcarthur has quit IRC01:35
*** dbecker has joined #openstack-operators01:48
*** mvenesio has joined #openstack-operators02:21
*** vijaykc4 has joined #openstack-operators02:24
*** vijaykc4 has quit IRC02:35
*** liverpooler has joined #openstack-operators02:44
*** blake has joined #openstack-operators02:57
*** mriedem has quit IRC03:02
*** vijaykc4 has joined #openstack-operators03:04
*** dtrainor has quit IRC03:09
*** dtrainor has joined #openstack-operators03:09
*** jiteka- has quit IRC03:09
*** jiteka- has joined #openstack-operators03:10
*** mvenesio has quit IRC03:11
*** liverpooler has quit IRC03:15
*** vijaykc4 has quit IRC03:26
*** vijaykc4 has joined #openstack-operators03:27
*** vijaykc4 has quit IRC03:44
*** blake has quit IRC04:03
*** blake has joined #openstack-operators04:04
*** germs has quit IRC04:07
*** vijaykc4 has joined #openstack-operators04:16
*** vijaykc4 has quit IRC04:17
*** VW has joined #openstack-operators04:20
*** vijaykc4 has joined #openstack-operators04:28
*** vijaykc4 has quit IRC04:29
*** simon-AS559 has joined #openstack-operators04:35
*** pontusf has joined #openstack-operators04:37
*** arnewiebalck_ has joined #openstack-operators04:46
*** arnewiebalck has quit IRC04:46
*** arnewiebalck_ is now known as arnewiebalck04:46
*** VW_ has joined #openstack-operators04:46
*** pontusf3 has quit IRC04:47
*** VW has quit IRC04:50
*** arnewiebalck has quit IRC04:53
*** chyka has quit IRC04:53
*** chyka has joined #openstack-operators04:54
*** arnewiebalck has joined #openstack-operators04:57
*** chyka has quit IRC04:59
*** AlexeyAbashkin has joined #openstack-operators05:01
*** markvoelker has quit IRC05:01
*** iranzo has joined #openstack-operators05:08
*** VW_ has quit IRC05:15
*** AlexeyAbashkin has quit IRC05:34
*** VW has joined #openstack-operators05:38
*** AlexeyAbashkin has joined #openstack-operators05:39
*** VW has quit IRC05:43
*** pvradu has quit IRC06:00
*** blake has quit IRC06:02
*** lvdombrkr has joined #openstack-operators06:05
*** AlexeyAbashkin has quit IRC06:07
*** lvdombrkr89 has joined #openstack-operators06:10
*** dmibrid has quit IRC06:12
*** lvdombrkr has quit IRC06:13
*** pontusf1 has joined #openstack-operators06:29
*** pontusf1 has quit IRC06:30
*** simon-AS559 has quit IRC06:38
*** markvoelker has joined #openstack-operators07:01
*** slaweq has joined #openstack-operators07:02
*** tesseract has joined #openstack-operators07:02
*** martin_85 has joined #openstack-operators07:04
*** rcernin has quit IRC07:05
*** damien_r has joined #openstack-operators07:13
*** simon-AS559 has joined #openstack-operators07:13
*** damien_r has quit IRC07:17
*** racedo has joined #openstack-operators07:24
*** damien_r has joined #openstack-operators07:26
*** blake has joined #openstack-operators07:28
*** vijaykc4 has joined #openstack-operators07:31
*** shananigans has quit IRC07:33
*** logan- has quit IRC07:35
*** martin_85 has quit IRC07:36
*** markvoelker has quit IRC07:36
*** martin_85 has joined #openstack-operators07:36
*** shananigans has joined #openstack-operators07:38
*** logan- has joined #openstack-operators07:39
*** vijaykc4 has quit IRC07:44
*** pcaruana has joined #openstack-operators07:50
*** gkadam has joined #openstack-operators07:54
*** vijaykc4 has joined #openstack-operators08:04
*** blake_ has joined #openstack-operators08:05
*** blake has quit IRC08:08
*** blake_ has quit IRC08:09
*** gkadam has quit IRC08:13
*** gkadam has joined #openstack-operators08:13
*** chyka has joined #openstack-operators08:13
*** chyka has quit IRC08:18
*** AlexeyAbashkin has joined #openstack-operators08:25
*** markvoelker has joined #openstack-operators08:33
*** rmart04 has joined #openstack-operators08:36
*** derekh has joined #openstack-operators08:44
*** simon-AS559 has quit IRC08:46
*** gkadam has quit IRC08:54
*** vijaykc4 has quit IRC09:02
*** simon-AS5591 has joined #openstack-operators09:05
*** bauruine has quit IRC09:06
*** markvoelker has quit IRC09:06
*** VW has joined #openstack-operators09:14
*** VW has quit IRC09:18
*** simon-AS559 has joined #openstack-operators09:57
*** simon-AS5591 has quit IRC10:00
*** chyka has joined #openstack-operators10:01
*** markvoelker has joined #openstack-operators10:03
*** simon-AS559 has quit IRC10:04
*** chyka has quit IRC10:06
*** simon-AS559 has joined #openstack-operators10:17
*** simon-AS5591 has joined #openstack-operators10:21
*** admin0 has joined #openstack-operators10:22
*** simon-AS559 has quit IRC10:22
*** markvoelker has quit IRC10:37
*** electrofelix has joined #openstack-operators10:42
*** simon-AS5591 has quit IRC10:49
*** vijaykc4 has joined #openstack-operators11:13
*** vijaykc4 has quit IRC11:26
*** markvoelker has joined #openstack-operators11:34
*** simon-AS559 has joined #openstack-operators11:42
*** jamesmcarthur has joined #openstack-operators11:51
*** jamesmcarthur has quit IRC11:55
*** markvoelker has quit IRC12:01
*** markvoelker has joined #openstack-operators12:02
*** liverpooler has joined #openstack-operators12:07
*** liverpooler has quit IRC12:12
*** liverpooler has joined #openstack-operators12:12
*** d0ugal has quit IRC12:24
*** simon-AS559 has quit IRC12:33
*** d0ugal has joined #openstack-operators12:44
*** Mantorok has quit IRC12:49
*** Mantorok has joined #openstack-operators12:50
*** mvenesio has joined #openstack-operators12:52
*** VW has joined #openstack-operators12:52
*** mriedem has joined #openstack-operators12:53
*** VW has quit IRC12:58
*** bauruine has joined #openstack-operators13:04
*** VW has joined #openstack-operators13:10
*** simon-AS559 has joined #openstack-operators13:15
*** simon-AS5591 has joined #openstack-operators13:20
*** simon-AS559 has quit IRC13:20
*** vijaykc4 has joined #openstack-operators13:21
*** vijaykc4 has quit IRC13:45
*** vijaykc4 has joined #openstack-operators13:45
*** blake has joined #openstack-operators13:59
*** shintaro has joined #openstack-operators14:02
*** vijaykc4 has quit IRC14:02
*** vijaykc4 has joined #openstack-operators14:03
*** mihalis68 has joined #openstack-operators14:03
mihalis68anyone around?14:04
blakeyes14:05
shintarohi14:05
mihalis68we're due an openstack ops meetups team meeting now14:05
mihalis68#startmeeting ops-meetup-team14:05
openstackMeeting started Tue Jun 19 14:05:51 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
smcginnisHey!14:06
mihalis68agenda https://etherpad.openstack.org/p/ops-meetups-team14:06
mihalis68please add your name to the attendees list if you're here for the meeting14:06
shintaroo/14:06
mihalis68#topic actions14:07
*** openstack changes topic to "actions (Meeting topic: ops-meetup-team)"14:07
mihalis68I was due to reawaken the debate about the way forward on docs14:07
mihalis68for those who weren't in Vancouver or not in the session, there was strong support for a change of plan on the three docs that look most relevant to operators14:08
spotzo/14:08
mihalis68the docs are the operators Guide, the HA guide and Arch guide14:08
*** germs has joined #openstack-operators14:08
*** germs has quit IRC14:08
*** germs has joined #openstack-operators14:08
blakeo/14:08
mihalis68the operators guide was converted to wiki with the intent that it would be community edited, however there's no enthusiasm for that approach it seems14:08
mihalis68compared to reverting to the source code method of maintinaing it and simply moving it to a different repo where it can have new owners14:09
mihalis68meanwhile the arch guide is also in a similar state of being due for removal from the core openstack doc set and arguably needing the same ownership change14:09
mihalis68same for HA guide14:09
mihalis68for HA guide there's even an offer to rewrite14:09
mihalis68adam speirs IIRC14:10
mihalis68I haven't done this action, but I'll try to get to that this week - on the mailing list14:10
spotzIf it's a matter of tooling, I'm willing to run the Git and Gerrit Lunch and Learn at the Ops Meetup14:10
mihalis68yes I think the tooling is a concern for those who might like to jump in14:11
shintarothat sounds great idea14:11
mihalis68at least, it is a concern for me14:11
smcginnisAdam seemed keen to get that rewritten, so he may just need a poke to get going on that.14:11
mihalis68I think we need to show it will land somewhere welcoming. The mailing list thread faltered over the exact details of the plan14:12
smcginnisIf I remember right, there was some confusion about the scope of what this team would be taking on there.14:12
mihalis68yes agreed14:13
*** jamesmcarthur has joined #openstack-operators14:13
mihalis68I didn't understand some of the jargon in that thread about where the code should be kept and what the process should be14:13
smcginnisSorry, I think I was catching up on other things then. If we get that started again and there are any issues like that, just let me know and I can try to clarify things.14:14
mihalis68#action mihalis68 to try to reawaken the ops docs thread on the operators mailing loist14:14
mihalis68that assistance will be much appreciated smcginnis!14:14
spotzAnd one last point I think was how the repo needed to be set up without agreements?14:15
mihalis68any other actions from past meetings people care to  update us on. We have to use the honor system for actions these days14:15
*** germs has quit IRC14:15
jamesmcarthurTotal of 15 operators registrar14:16
jamesmcarthurFor ptg14:16
jamesmcarthurWhich is a little less than 10% of total14:16
smcginnisjamesmcarthur: I forget, was there a registration option where they could identify themselves as that?14:16
mihalis68There will most likely be two of us from Bloomberg and we're not registered. In fact I only just mentioned it to my boss14:17
jamesmcarthurYeah. Expecting late registrants14:17
mihalis68seems like that's it for actions updates.14:17
mihalis68#topic PTG14:17
*** openstack changes topic to "PTG (Meeting topic: ops-meetup-team)"14:17
mihalis68#info 15 registered operators so far14:17
mihalis68#info operators seem to always register fairly late on14:17
jamesmcarthurS smcginnis  no. We are counting based on names of registrants14:18
jamesmcarthurSorry all. In my car.14:18
smcginnisjamesmcarthur: I hope you're not driving and IRCing. :D14:19
shintaroI should be one of those 15 :)14:19
spotzIf he's back in Austin he's sitting in traffic:)14:19
jamesmcarthurIn traffic. Trim g to type at lights14:20
smcginnisHah14:20
mihalis68is there any concept of defined days for operators within the PTG?14:20
mihalis68We're on the hook for a big release of our openstack product for a big infra project at my employer and that time (september 10-14th) is likely to be fraught14:21
spotzI think the thought was to allow it to run as normal with the ability to have merged days?14:21
mihalis68it was proposed as a co-located ops meetup, but I don't see any sign of that14:21
spotzmihalis68: How would you like to see that impression fixed?14:22
*** germs has joined #openstack-operators14:22
smcginnisYeah, last I heard specific format was still being worked out dependent on attendance and space arrangements.14:22
spotzI know I can do git and the folks who did the suse troubleshooting session at summit are willing to do it at the ops meetup if content is needed14:23
mihalis68well I'm not sure I'm right, as i haven't really explored the PTG website, but if it's true, then a way forward would be to decide which days should be considered if you can do 2 days but not 514:23
smcginnisBut I believe the plan (or at least hope) was to have a separate clearly identified Ops Meetup portion that would be there.14:23
smcginnismihalis68: ++14:23
mihalis68I will try and be there for the entire thing, but it might be possible to send additional people from my team for specific ops meetups stuff whereas the full 5 days is a long time14:24
spotzmihalis68: Ok so a big thing would be to pick dates, that makes sense so folks can get travel approval before buying tickets14:24
apriceyes, that is still the plan and the team is trying to plan so that it doesnt overlap with other sessions that would benefit from operator participation. I think it's still a work in progress.14:24
mihalis68ok, good to hear.14:24
smcginnisSomewhere Wed-Fri?14:24
mihalis68I was present for a discussion on this somewhere at the summit and there wasn't a clear consensus14:25
smcginnisI think there was some talk of making it when the project teams are more silo'd so ops can attend some of the cross project on Mon-Tue if desired.14:25
spotzmihalis68: yeah I think that was Mondayy I was there for that14:25
mihalis68some said have ops and devs meetup separately then join together at the end to exchange findings14:25
smcginnisSeparate Wed-Thurs, join back up Friday?14:26
mihalis68I like this for sure14:26
spotzI think the one downside of wed-fri is folks leaving on Friday14:26
shintarosmcginnis +114:26
mihalis68it also seems to be in line with the very original impetus for the "merger" in that days 1-2 are very appropriate for operators to join in, but days 3,4 less so (in the previous definition of PTG)14:27
*** germs has quit IRC14:27
smcginnisThat could work well. Mon-Tue for cross project things that could use operator input, Wed-Thur everyone goes to their corners, then Fri (if able to stay the whole time) get back for any kind of follow up activities and discussions.14:27
apricei can share this concept with our team as they are working on space planning and scheduling now14:28
spotzaprice jamesmcarthur - would that work you think?14:28
apricewe should be able to provide an update before the next meeting, but I dont want to say yay or nay until I have had a chance to talk to them since they're much closer to it14:28
shintarothank you aprice14:29
jamesmcarthurSorry. Finally stopped. Yeah there was a lot of debate at the forum whether Monday-Tuesday would be better or We’d-Thur14:29
jamesmcarthurSome folks thought it would be best to meet early in the week so they could deliver operator opinions to the projects ahead of their meeting14:30
jamesmcarthurOthers thought it would be better to listen in to project goals and then discuss during operator meetings14:30
*** germs has joined #openstack-operators14:31
*** germs has quit IRC14:31
*** germs has joined #openstack-operators14:31
jamesmcarthurWe would love to hear a consensus from the Ops and then. We will do our best to try to make that happen14:31
mihalis68sounds like a job for the meetups team :)14:32
smcginnis:)14:32
mihalis68what should we do? email threads don't really connect14:32
mihalis68maybe email and a poll?14:32
mihalis68(ok now I'm starting to recall prior discussion of a poll, maybe I was already supposed to be polling them about PTG)14:32
smcginnisOr informal with the team here? Any preferences?14:32
spotzPolls are good:)14:32
shintaromihalis68 that poll was meant to find out how many ops would attend ptg14:33
mihalis68we don't even have all the meetups team here, so I hardly think we can decide - no Van Winkle, no Hillsman, no McCormick14:33
mihalis68oh right, thanks for jogging my memory14:33
smcginnisYeah, we need input from the whole team.14:34
spotzvw is finally back online and is catching up14:34
*** jamesmca_ has joined #openstack-operators14:34
VWoh hai!  sorry -was cleaning out the inbox and didn't see the tie14:34
VWtime14:34
mihalis68we could expand it to "1. Are you interested in PTG  2. If so would you prefer ops focused days on days 1,2 or on days 3,4?"14:34
spotz:)14:35
VWlove it14:35
spotzmihalis68: Just make sure they understand PTG is also Ops Meetup?14:35
VWactually, wait14:35
shintaro1. Are you interested in OpsMeetup at PTG? isn't it?14:36
mihalis68we'd have to preview any survey to make sure both the wording and the overall message is proper14:36
VWno no no. it's more do the want to attend the Ops meetup (TBD as days 1,2 or 3,4 above) or do they want to attend the PTG AND Ops mid-cycle14:36
mihalis68the even in Denver is a done deal. It's both14:36
spotzBut don't we want them to pick days to?14:36
VWargh -no - BOTH are there, but they are two events14:36
VWit is perfectly fine for someone to come for just two days of ops14:37
VWat least that is how I have understood it to date14:37
spotzvw correct14:37
*** kendallwaters has joined #openstack-operators14:38
VWbut to an underlying point in mihalis68's comments, we need to understand if cost is an issue blocking people from even coming to at least that14:38
smcginnisI think we do need to see which days work best for those that can't do the full week.14:38
mihalis68the poll mentioned previously (and not yet done) was to ascertain ops community interest in the 5 days, in the 2 days14:38
VWtotally agree14:38
VWawesome - that's a huge data point, mihalis6814:38
smcginnisThe ship has kind of sailed on whether they are interested in it being colocated.14:38
*** antosh has joined #openstack-operators14:38
mihalis68yes that's a done deal for September14:39
*** vijaykc4 has quit IRC14:39
*** vijaykc4 has joined #openstack-operators14:39
VWyeah - I'm not saying we ask about co-location.  I'm curious if A. folks are coming and B. if they might do both and c. what blockers/misconceptions might be out there still14:40
mihalis68https://www.irccloud.com/pastebin/xZWOcpvl/14:40
spotzAnd I think add which days they would prefer as it sounds like we still might have the option to shift around14:40
*** paul122345 has joined #openstack-operators14:41
smcginnisspotz: ++14:41
mihalis68hope people can see my snippet there, it covers that14:41
smcginnismihalis68: Yep, that looks good to me.14:42
jamesmca_OK - just a heads up, the big thing is we're trying not to schedule Ops during Cross-Project discussions so Ops people that are there for the full time can attend those events.14:42
mihalis68cross-project is mostly during days 1,2 right?14:42
spotz#link https://www.irccloud.com/pastebin/xZWOcpvl/14:42
spotzjust to get that logged right14:42
mihalis68thanks!14:42
jamesmca_The schedule is not yet fully formed, so we're looking for an Ops preference on days, but none of the days are guaranteed until we see how that matches up with the rest of hte schedule.14:42
kendallwatersmost likely cross-projects stuff will be day 1 & 2 but that is not set in stone yet14:43
kendallwaterswe are doing a lot of schedule build and space allocation this week14:43
jamesmca_That said, the sooner we can get the schedule together and communicate it to all the communities, the better it will be for folks planning travel.14:43
spotzIf I remember part of the talks in that one session was the need to have the first day atleast all ops to get things off their chest?14:43
spotzIn which case overlap on cross-project day wouldn't be awful14:43
mihalis68this got summarised as the need to "vent" or something like that14:44
mihalis68I no longer feel that as an operator I need to do that14:44
spotzyeah, nicer way of wording:)14:44
spotzI know things have come a long way since my first deployment14:45
mihalis68I think many things that used to be an issue that ops felt they needed to raise are now conversations - long-term support, release cadence, deletion of docs "too soon" etc14:45
*** vijaykc4 has quit IRC14:45
mihalis68anyway, should I put a poll together as above?14:45
mihalis68if someone really wants to do it, that'd be great, but if not I'm willing to14:45
spotzmihalis68: I say go for it14:46
jamesmca_I almost think it's best for this meetup group decided.14:46
jamesmca_Most people just want to know when to book travel.14:46
jamesmca_Personally, I think y'all would be best for Ops to plan Wed for venting, Thur-Fri for meetings. (or just Thursday)14:47
mihalis68we don't even have half the meetups team here today, no way can this be "just decide"d14:47
jamesmca_That would jive w/ cross-project work and would allow Ops in attendance to hit those days14:47
jamesmca_(sorry - I'm having a terrible time typing today)14:48
spotzjamesmca_: Just go get breakfast at Torchey's?:)14:48
jamesmca_mihalis68: understood. I was thinking maybe a vote/discussion by email14:48
jamesmca_spotz: that might be in order14:48
mihalis68I'll put it to the community. If there's no response, the ops meetups team can certainly do its best to decide a good itinerary working with the foundation14:49
spotzJust give it a deadline for responding14:49
mihalis68yeah. I understand we can't delay on this but there was quite good backing for at least trying to get input on the PTG, from the ops community, last time this team met14:49
shintaro+1 mihalis68 sending out the poll would raise awareness to the ops community about the event, too.14:50
mihalis68and, again, I'm not planning an event to start with "venting". We didn't do that in tokyo or mexico city14:50
shintaroI don't think we need "venting" either. we need specific topic to discuss which is more productive14:51
smcginnisThat might set the wrong tone. At least if it is positioned as that.14:51
smcginnisshintaro: ++14:51
mihalis68yeah. think we're good for now. I'll do a poll and we'll see if we can get a response. If not this team will work with foundation to try to make the ops part of PTG as good as possible. It's all we can do and as a first attempt we expect to learn adn improve for a followup14:52
mihalis68only 7 mintes left, so if I may...14:53
mihalis68#topic possible regional meetup14:53
*** openstack changes topic to "possible regional meetup (Meeting topic: ops-meetup-team)"14:53
mihalis68i've been researching the possibility of using Bloomberg facilities for a smaller regional ops meetup, after PTG14:53
*** slaweq has quit IRC14:53
mihalis68It may be possible for us to host something for NE USA14:53
mihalis68it's not easy to arrange any random event due to strict guidelines14:54
mihalis68however from my research, ops meetups fit entirely within them!14:54
spotzsweet14:54
*** slaweq has joined #openstack-operators14:54
mihalis68so I just wanted to mention this and see if there might be interest14:54
mihalis68as a reminder, openstack days east stopped happening14:54
smcginnisThat might be great.14:54
mihalis68that was our regional event for a bit14:54
mihalis68I think the multi--purpose room is 70 people14:55
mihalis68so it couldn't meet the guidelines for a global event where we expect 100-150 capacity14:55
smcginnisSingle room so one track?14:55
mihalis68might be able to get a much smaller second room14:55
mihalis68but only one full AV-wired "keynote" style room14:55
spotzOr if done right depending on the setup you could put different subject in corners?14:56
*** martin_85 has quit IRC14:56
mihalis68yes, although I don't think we can reconfigure it to anything other than cinema style seating (everyone facing the screen)14:56
mihalis68there are other more reconfigurable smaller rooms14:56
mihalis68it all depends on : if there's interest I can look into it and if I book far enough ahead maybe even get our events staff to helpp14:57
mihalis68*help14:57
mihalis68if there's interest, speak up or email me or ... smoke signals14:58
mihalis68#topic any other business14:58
*** openstack changes topic to "any other business (Meeting topic: ops-meetup-team)"14:58
mihalis682 minutes left!14:58
apricemihalis68: would this meetup be between the ptg and the forum?14:58
apriceand would it be for folks local to that city?14:58
mihalis68unknown at present14:58
mihalis68My tentative idea is a NE USA meetup14:59
apricewe have gotten feedback on too many events / too much travel so I want to take that into consideration before asking ops folks to attend another event.14:59
mihalis68there's people I know in DC area, for ecample14:59
mihalis68DC->NYC is just a train ride, so it's not the super expensive globetrotting that following summits and Ops midcycles has been, at least not for people in the region14:59
mihalis68the next ops meetup was going to be in NE USA before it merged into PTG and moved to Denver15:00
smcginnismnaser: If interested... ^15:01
spotzMaybe check with the OpenStack Ambassadors, maybe do a combined meeting day?15:01
mihalis68as mentioned above, I am saying upfront that it wouldn't be a global event15:01
* mnaser reads buffer15:01
*** racedo has quit IRC15:01
apricei understand, but I do want to encourage as many ops to attend the PTG and Forum if possible, but would love community feedback as well.15:01
*** racedo has joined #openstack-operators15:01
smcginnisI think a smaller regional event would be useful in that area. But knowing the PTG/Ops meetup is the "big event"/15:02
mihalis68yep.15:02
*** racedo has quit IRC15:02
mnaseras an operator, traveling all the way out to just meet with other ops is expensive.  colocating it is very useful15:02
shintaroagree. regional ops meetup works well for us15:02
mihalis68out of time15:02
mihalis68thanks everyone15:02
smcginnisThanks!15:03
mihalis68#endmeeting15:03
*** 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:03
openstackMeeting ended Tue Jun 19 15:03:08 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-06-19-14.05.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-06-19-14.05.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2018/ops_meetup_team.2018-06-19-14.05.log.html15:03
shintarothank you mihalis6815:03
VWshould we make a point to reconvene next week since there is still lots to figure out15:03
mihalis68works for me15:03
mnaseri'll try to attend the next one.  is there a meeting name under eavesdrop.openstack.org ?15:03
smcginnisVW: That might be good. We dropped back to ever other due to not having much, but I think right now we may want to go back to weekly until this is finalized.15:04
smcginnismnaser: http://eavesdrop.openstack.org/#OpenStack_Ops_Meetup_Team15:04
mnasersmcginnis: thank you15:04
*** paul122345 has quit IRC15:04
mihalis68I did calendar invites for the actual meetups team for today. Will update them to show next week on your  calendars15:04
spotzIf I forget just ping me, I'm now in this channel fulltime:)15:04
smcginnismnaser: Would be great if you could attend. Would love to have your input on some of these too since you have visibility on both sides too.15:04
shintaroI can't attend next week/ or will be late.15:04
smcginnisNote: all action items go to shintaro next week. :)15:05
mihalis68perfect15:05
shintarooops15:05
mnasersmcginnis: i've never attended an ops meet up because it's quite expensive in general15:06
mnaserin terms of travel cost, etc15:06
VWmihalis68: mvanwinkle@salesforce.com15:06
smcginnismnaser: They can be valuable I think. But probably not if you need to take a week away from work and travel half way around the world for it.15:09
mihalis68mnaser: we rotate them around the world to try and make one fairly near each regional community within every 3 events. North America, APAC, Europe are the three rotating target zones15:11
smcginnismnaser: Anyway, just thinking NY might be easier for you if it's an option.15:12
mnaserNY is easier, but i have to run to another meeting15:13
shintaroAlso regional ones are useful for people to understand how the event is valuable and would encourage some of the attendees to consider attending the global one15:13
smcginnis++15:13
smcginnisAnd different flavors to them too. It was kind of interesting having the NFV focus in Tokyo.15:13
shintaroYes I liked that one too15:14
*** shintaro has quit IRC15:16
*** pcaruana has quit IRC15:29
*** chyka has joined #openstack-operators15:48
*** belmoreira has quit IRC15:53
*** simon-AS5591 has quit IRC15:56
*** lvdombrkr89 has quit IRC15:58
*** damien_r has quit IRC16:04
*** iranzo has quit IRC16:09
*** VW_ has joined #openstack-operators16:21
*** rmart04 has quit IRC16:22
*** VW has quit IRC16:24
*** damien_r has joined #openstack-operators16:38
*** VW_ has quit IRC16:39
*** damien_r has quit IRC16:40
*** jamesmcarthur has quit IRC16:43
*** blake has quit IRC16:43
*** blake has joined #openstack-operators16:43
*** gyee has joined #openstack-operators16:46
*** blake has quit IRC16:48
*** AlexeyAbashkin has quit IRC16:52
*** blake has joined #openstack-operators16:54
*** blake has quit IRC16:55
*** blake has joined #openstack-operators16:55
*** jamesmca_ has quit IRC16:57
*** jamesmcarthur has joined #openstack-operators16:57
*** blake has quit IRC17:00
*** derekh has quit IRC17:00
*** jamesmcarthur has quit IRC17:02
*** pcaruana has joined #openstack-operators17:05
*** blake has joined #openstack-operators17:06
*** kendallwaters has quit IRC17:08
*** tesseract has quit IRC17:08
*** jamesmcarthur has joined #openstack-operators17:10
*** jamesmcarthur has quit IRC17:10
*** jamesmcarthur has joined #openstack-operators17:11
*** jamesmca_ has joined #openstack-operators17:12
*** jamesmcarthur has quit IRC17:16
*** jamesmca_ has quit IRC17:35
*** jamesmcarthur has joined #openstack-operators17:36
*** lvdombrkr has joined #openstack-operators17:38
*** jamesmcarthur has quit IRC17:41
*** VW has joined #openstack-operators17:56
*** jamesmcarthur has joined #openstack-operators18:00
*** VW_ has joined #openstack-operators18:05
*** VW has quit IRC18:07
*** lvdombrkr has quit IRC18:17
*** lvdombrkr has joined #openstack-operators18:24
*** simon-AS559 has joined #openstack-operators18:24
*** jamesmca_ has joined #openstack-operators18:26
*** electrofelix has quit IRC18:27
*** jamesmcarthur has quit IRC18:30
*** jamesmca_ has quit IRC18:44
*** iranzo has joined #openstack-operators18:45
*** mihalis68 has quit IRC18:53
*** AlexeyAbashkin has joined #openstack-operators19:26
*** AlexeyAbashkin has quit IRC19:37
*** blake has quit IRC19:41
*** blake has joined #openstack-operators19:42
*** slaweq has quit IRC19:43
*** slaweq has joined #openstack-operators19:44
*** iranzo has quit IRC19:44
*** blake has quit IRC19:47
*** aojea has joined #openstack-operators19:48
*** simon-AS5591 has joined #openstack-operators19:58
*** simon-AS559 has quit IRC20:02
*** simon-AS559 has joined #openstack-operators20:08
*** simon-AS5591 has joined #openstack-operators20:10
*** simon-AS559 has quit IRC20:13
*** pcaruana has quit IRC20:29
*** dmibrid has joined #openstack-operators20:32
*** mvenesio has quit IRC20:34
*** mvenesio_ has joined #openstack-operators20:34
*** mvenesio_ has quit IRC21:18
*** lvdombrkr has quit IRC21:22
*** aojea has quit IRC21:41
*** blake has joined #openstack-operators21:42
*** antosh has quit IRC21:55
*** simon-AS5591 has quit IRC22:03
*** slaweq has quit IRC22:04
*** rcernin has joined #openstack-operators22:12
*** vijaykc4 has joined #openstack-operators22:16
*** slaweq has joined #openstack-operators22:18
*** blake has quit IRC22:19
*** blake has joined #openstack-operators22:20
*** blake has quit IRC22:24
*** mvenesio has joined #openstack-operators22:30
*** slaweq has quit IRC22:33
*** antosh has joined #openstack-operators22:37
*** vijaykc4 has quit IRC22:42
*** vijaykc4 has joined #openstack-operators22:45
*** blake has joined #openstack-operators22:52
*** liverpooler has quit IRC23:09
*** slaweq has joined #openstack-operators23:11
*** slaweq has quit IRC23:15
*** antosh has quit IRC23:28
*** chyka has quit IRC23:34
*** vijaykc4 has quit IRC23:44
*** vijaykc4 has joined #openstack-operators23:49

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