Tuesday, 2017-10-17

*** catintheroof has quit IRC00:00
*** catintheroof has joined #openstack-operators00:00
*** emagana has quit IRC00:02
*** emagana has joined #openstack-operators00:03
*** emagana_ has joined #openstack-operators00:04
*** emagana has quit IRC00:04
*** chyka has quit IRC00:04
*** catintheroof has quit IRC00:04
*** emagana_ has quit IRC00:08
*** markvoelker_ has quit IRC00:17
*** wasmum has quit IRC00:19
*** markvoelker has joined #openstack-operators00:25
*** shintaro has joined #openstack-operators00:28
*** markvoelker has quit IRC00:29
*** markvoelker has joined #openstack-operators00:34
*** markvoelker has quit IRC00:39
*** markvoelker has joined #openstack-operators00:43
*** Apoorva_ has joined #openstack-operators00:44
*** aojea has joined #openstack-operators00:47
*** markvoelker has quit IRC00:48
*** Apoorva has quit IRC00:48
*** AlexeyAbashkin has joined #openstack-operators00:48
*** Apoorva_ has quit IRC00:48
*** aojea has quit IRC00:52
*** AlexeyAbashkin has quit IRC00:52
*** markvoelker has joined #openstack-operators00:52
*** mriedem1 has joined #openstack-operators00:54
*** mriedem has quit IRC00:55
*** mriedem1 is now known as mriedem00:55
*** gkadam has quit IRC00:57
*** markvoelker has quit IRC00:57
*** gkadam has joined #openstack-operators00:58
*** markvoelker has joined #openstack-operators01:01
*** markvoelker has quit IRC01:06
*** gkadam has quit IRC01:06
*** markvoelker has joined #openstack-operators01:11
*** markvoelker has quit IRC01:15
*** catintheroof has joined #openstack-operators01:19
*** markvoelker has joined #openstack-operators01:20
*** catintheroof has quit IRC01:21
*** AlexeyAbashkin has joined #openstack-operators01:28
*** AlexeyAbashkin has quit IRC01:32
*** mriedem has quit IRC01:45
*** aojea has joined #openstack-operators01:48
*** chlong has joined #openstack-operators01:49
*** aojea has quit IRC01:52
*** markvoelker has quit IRC01:53
*** markvoelker has joined #openstack-operators01:59
*** VW has joined #openstack-operators02:02
*** markvoelker has quit IRC02:03
*** masber has quit IRC02:07
*** markvoelker has joined #openstack-operators02:08
*** markvoelker has quit IRC02:12
*** markvoelker has joined #openstack-operators02:17
*** trungnv has quit IRC02:18
*** emagana has joined #openstack-operators02:20
*** markvoelker has quit IRC02:21
*** markvoelker has joined #openstack-operators02:26
*** AlexeyAbashkin has joined #openstack-operators02:27
*** markvoelker has quit IRC02:30
*** AlexeyAbashkin has quit IRC02:31
*** LongyanG has quit IRC02:34
*** LongyanG has joined #openstack-operators02:34
*** markvoelker has joined #openstack-operators02:35
*** bradm has quit IRC02:37
*** markvoelker has quit IRC02:40
*** TuanLA has joined #openstack-operators02:44
*** markvoelker has joined #openstack-operators02:44
*** TuanLA has quit IRC02:44
*** bradm has joined #openstack-operators02:45
*** aojea has joined #openstack-operators02:49
*** masber has joined #openstack-operators02:49
*** markvoelker has quit IRC02:49
*** VW has quit IRC02:52
*** TuanLA has joined #openstack-operators02:52
*** VW has joined #openstack-operators02:52
*** markvoelker has joined #openstack-operators02:53
*** aojea has quit IRC02:53
*** VW has quit IRC02:57
*** emagana has quit IRC03:04
*** emagana has joined #openstack-operators03:05
*** emagana has quit IRC03:09
*** trungnv has joined #openstack-operators03:17
*** AlexeyAbashkin has joined #openstack-operators03:26
*** markvoelker has quit IRC03:27
*** AlexeyAbashkin has quit IRC03:31
*** gkadam has joined #openstack-operators03:33
*** TuanLA has quit IRC03:45
*** TuanLA has joined #openstack-operators03:46
*** masber has quit IRC03:46
*** aojea has joined #openstack-operators03:49
*** aojea has quit IRC03:54
*** trungnv has quit IRC04:10
*** markvoelker has joined #openstack-operators04:17
*** dbecker has quit IRC04:22
*** markvoelker has quit IRC04:22
*** AlexeyAbashkin has joined #openstack-operators04:26
*** markvoelker has joined #openstack-operators04:27
*** AlexeyAbashkin has quit IRC04:31
*** markvoelker has quit IRC04:33
*** markvoelker has joined #openstack-operators04:34
*** dbecker has joined #openstack-operators04:35
*** khyr0n has joined #openstack-operators04:40
*** khyr0n has quit IRC04:40
*** aojea has joined #openstack-operators04:50
*** yprokule has joined #openstack-operators04:52
*** aojea has quit IRC04:55
*** emagana has joined #openstack-operators05:03
*** emagana has quit IRC05:11
*** dmibrid_ has quit IRC05:22
*** slaweq has joined #openstack-operators05:35
*** slaweq has quit IRC05:47
*** dfflanders has joined #openstack-operators05:50
*** aojea has joined #openstack-operators05:51
*** slaweq has joined #openstack-operators05:52
*** slaweq has quit IRC05:54
*** markvoelker has quit IRC05:54
*** aojea has quit IRC05:56
*** Oku_OS-away is now known as Oku_OS06:08
*** chyka has joined #openstack-operators06:20
*** masber has joined #openstack-operators06:21
*** chyka has quit IRC06:25
*** slaweq has joined #openstack-operators06:37
*** aojea has joined #openstack-operators06:38
*** slaweq has quit IRC06:41
*** simon-AS559 has joined #openstack-operators06:44
*** pcaruana has joined #openstack-operators06:44
*** Oku_OS is now known as Oku_OS-away06:46
*** simon-AS5591 has joined #openstack-operators06:47
*** aojea has quit IRC06:47
*** simon-AS559 has quit IRC06:48
*** Oku_OS-away is now known as Oku_OS06:50
*** markvoelker has joined #openstack-operators06:50
*** arnewiebalck_ has joined #openstack-operators06:56
*** bjolo_ has joined #openstack-operators07:02
*** simon-AS5591 has quit IRC07:03
*** simon-AS559 has joined #openstack-operators07:05
*** slaweq has joined #openstack-operators07:11
*** slaweq has quit IRC07:15
*** arnewiebalck_ has quit IRC07:16
*** tesseract has joined #openstack-operators07:16
*** arnewiebalck_ has joined #openstack-operators07:32
*** AlexeyAbashkin has joined #openstack-operators07:34
*** arnewiebalck_ has quit IRC07:37
*** trungnv has joined #openstack-operators07:43
*** aojea has joined #openstack-operators07:44
*** aojea has quit IRC07:48
*** fragatina has joined #openstack-operators07:48
*** fragatina has quit IRC07:49
*** fragatina has joined #openstack-operators07:49
*** chyka has joined #openstack-operators08:10
*** chyka has quit IRC08:14
*** derekh has joined #openstack-operators08:34
*** Caterpillar has joined #openstack-operators08:42
*** aojea has joined #openstack-operators08:44
*** aojea has quit IRC08:49
*** electrofelix has joined #openstack-operators08:51
*** markvoelker has quit IRC09:03
*** simon-AS559 has quit IRC09:03
*** markvoelker has joined #openstack-operators09:04
*** sdague has joined #openstack-operators09:17
*** simon-AS559 has joined #openstack-operators09:23
*** simon-AS559 has quit IRC09:27
*** slaweq has joined #openstack-operators09:30
*** slaweq has quit IRC09:35
*** aojea has joined #openstack-operators09:45
*** aojea has quit IRC09:50
*** simon-AS559 has joined #openstack-operators09:51
*** simon-AS559 has quit IRC09:56
*** simon-AS559 has joined #openstack-operators09:57
*** shintaro has quit IRC09:58
*** TuanLA has quit IRC10:05
*** trungnv has quit IRC10:05
*** slaweq has joined #openstack-operators10:32
*** slaweq has quit IRC10:37
*** tesseract has quit IRC10:43
*** tesseract has joined #openstack-operators10:43
*** aojea has joined #openstack-operators10:46
*** aojea has quit IRC10:50
*** simon-AS5591 has joined #openstack-operators11:08
*** simon-AS559 has quit IRC11:09
*** simon-AS559 has joined #openstack-operators11:11
*** simon-AS5592 has joined #openstack-operators11:13
*** simon-AS5591 has quit IRC11:15
*** simon-AS559 has quit IRC11:15
*** dminer has joined #openstack-operators11:40
*** chyka has joined #openstack-operators11:46
*** yprokule has quit IRC11:49
*** chyka has quit IRC11:51
*** chlong has quit IRC12:01
*** liverpooler has joined #openstack-operators12:10
*** liverpooler has quit IRC12:16
*** liverpooler has joined #openstack-operators12:17
*** gkadam has quit IRC12:36
*** aojea has joined #openstack-operators12:47
*** mriedem has joined #openstack-operators12:49
*** aojea has quit IRC12:52
*** yprokule has joined #openstack-operators13:02
*** ansmith has joined #openstack-operators13:33
*** mihalis68 has joined #openstack-operators13:36
mihalis68ops meetup team meeting in 25 minutes or so13:36
*** fandrieu has joined #openstack-operators13:36
*** yprokule has quit IRC13:37
*** yprokule has joined #openstack-operators13:37
*** chlong has joined #openstack-operators13:42
*** med2 has joined #openstack-operators13:46
*** aojea has joined #openstack-operators13:48
*** smcginnis has joined #openstack-operators13:51
*** med2 has quit IRC13:53
*** aojea has quit IRC13:53
*** catintheroof has joined #openstack-operators13:53
*** mugsie has joined #openstack-operators13:54
mihalis68agenda for meeting in 5 minutes : https://etherpad.openstack.org/p/ops-meetups-team13:55
*** VW has joined #openstack-operators13:57
*** VW has quit IRC13:57
*** shintaro has joined #openstack-operators13:58
*** VW has joined #openstack-operators13:58
mihalis68#startmeeting Ops Meetup Team14:02
openstackMeeting started Tue Oct 17 14:02:20 2017 UTC and is due to finish in 60 minutes.  The chair is mihalis68. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
mihalis68hello everyone14:02
*** openstack changes topic to " (Meeting topic: Ops Meetup Team)"14:02
openstackThe meeting name has been set to 'ops_meetup_team'14:02
shintarohi14:02
VWo/14:02
mihalis68#link https://etherpad.openstack.org/p/ops-meetups-team today's agenda14:02
mihalis68please add your name to the attendees list if you are here for the meeting14:02
mihalis68#topic review last weeks actions14:03
*** openstack changes topic to "review last weeks actions (Meeting topic: Ops Meetup Team)"14:03
mihalis68no progress on a new article about Tokyo, but the Eventbrite will be done soon and then that can start14:03
mihalis68an older article was submitting a blog post about the document retention policy and upstream LTS releases discussion. I submitted that today!14:04
mihalis68shintaro I emailed you a question about that just now14:04
shintaroyes, I need to check if $20 is ok and 150 cap for registration is ok, too14:04
mihalis68$20 is just right in my opinion14:05
mihalis68and 150 is more than enough, again IMO14:05
mihalis68thoughts from others?14:05
shintaroonce they are fixed I can ask for Eventbrite14:05
shintaroI believe $20 would affect attendance from Japan14:06
shintarowould not14:06
mihalis68med_ was here a few minutes ago. He had an action to report back from the TC meeting14:06
mihalis68he is attending those for "surveillance" :)14:06
mihalis68I'll assume no progress there unless he pops up. Any other progress towards previous actions?14:06
*** slaweq has joined #openstack-operators14:06
smcginnisI can answer TC stuff if there are any specific questions.14:07
mihalis68thanks smcginnis. med was suggesting we lack interaction with those folks, he considered running for TC but settled on attending those meetings and these and forwarding essential info14:07
*** thingee has quit IRC14:07
smcginnisI was kind of hoping he would run.14:08
mihalis68so I guess the question is has TC been talking about things the operators community should know of?14:08
smcginnisBut we did get a lot of candidates this time around.14:08
mihalis68I think he just missed the deadline14:08
shintaroTC voting is now in progress14:08
mihalis68I did chase him but it was very close to submission deadline14:08
*** emccormick has joined #openstack-operators14:08
smcginnisNothing overly operator impacting the last week or so.14:08
emccormickhola14:08
emccormicksry for lateness14:08
mihalis68hello emc thanks for joining14:08
smcginnisDo any of you pay attention to the tags projects assert?14:09
mihalis68any actions progress to report?14:09
emccormicksort of related to one14:09
*** thingee has joined #openstack-operators14:09
mihalis68smcginnis I heard thierry announce that, it sounded insane14:09
mihalis68I understand what he's talking about but it sounded wildly unrealistic for small sites/teams14:10
smcginnisMaybe the only think from the TC side is removing things like tripleo from stable:follows-policy and maybe creating a new tag for deployment projects to follow as they have slightly different restrictions and expectations.14:10
mihalis68I count my team in the latter14:10
emccormickre: social planning stuff, I spoke with Lauren and Erin. Apparently there is a foundation effort to throw a little party for Tom on Wednesday night and once details are set I will be inviting Ops to attend14:10
emccormickI was trying to set up something myself and then it occurred to me to ask if they were doing something14:10
emccormickso we're joining forces14:10
mihalis68excellent. I am so disappointed I won't be there14:10
shintarothanks emccormick I want to join that too14:11
*** slaweq has quit IRC14:11
*** aprice___ has joined #openstack-operators14:11
VWI'm in for that one as well14:11
emccormickI'll be sending something out to the list once I have info from them.14:11
*** catintheroof has quit IRC14:11
mihalis68nice. Glad to hear of more cooperation between operators, foundation etc14:11
emccormicktentatively it's going to be in the club at the Star Casino. Karaoke night :D14:12
mihalis68smcginnis I'll go review that discussion and try to get more with it on tags14:12
smcginnismihalis68: Cool, let me know if you have any questions I might be able to answer.14:12
mihalis68someone buy tom drinks until he's captured on video doing Back in Black14:12
smcginnis:)14:12
mihalis68yeah I should review and then if I have specific confusions email14:12
mihalis68I will fund those drinks, and I am serious14:13
shintarosmcginnis which ML was that discussion on? openstack-dev?14:13
emccormickFoundation is funding drinks, at least to a point ;)14:13
mihalis68well deserved14:13
mihalis68I feel Tom contributed hugely14:13
emccormickbut I'm sure we will buy him many other drinks that week. He's gonna have a 3 day hangover14:14
mihalis68I miss his input here14:14
VWI'll make sure he has at least a couple on "your dime" throughout the week, mihalis6814:14
mihalis68it's a deal14:14
VWI'm sure he and I will cross paths a couple of times14:14
smcginnisshintaro: I'll see if I can find the link.14:14
*** emagana has joined #openstack-operators14:14
mihalis68#action smcginnis to point out where the tags policy discussion landed (re: deployment systems)14:15
shintarothanks smcginis14:15
mihalis68helle emagana14:15
mihalis68*hello14:15
emaganaHello!  Sorry, I am late.14:15
smcginnisshintaro: Starts here: http://lists.openstack.org/pipermail/openstack-dev/2017-October/123624.html14:15
mihalis68no worries. We are still covering any progress on previous actions14:15
smcginnisWith links in there to the proposed changes that are having ongoing discussion.14:15
shintaroI will check the thread14:16
smcginnisI am curious how much things like that really have meaning in the "real world". :)14:16
mihalis68#link https://etherpad.openstack.org/p/ops-meetups-team repeated for latecomer. Please sign up on attendees list14:16
mihalis68my initial reaction to Thierry's announcement was "they are out of their minds, if we can't even find the stable stuff without reviewing a whole bunch of legalistic definitions then it's going to be a shit show"14:17
mihalis68I will acknowledge this isn't very nuanced14:18
smcginnis:)14:18
mihalis68At the time I feel like the big tent was full to overflowing, now the picture seems very different14:18
mihalis68several projects just went away14:19
mihalis68is it really infeasible to have a core stable set of components?14:19
smcginnisI think the intent of the stable:* tags is just to see a list of projects that you can expect to handle stable updates in reasonable ways.14:19
smcginnisBut we know how the upstream stable support doesn't really work with the operator needs for stable releases at this point.14:19
med_\o very late14:20
mihalis68the whole thing depends on python and from what I hear that does not "handle stable updates in reasonable ways"14:20
mihalis68welcome med_14:20
med_sorry, trouble driving in.14:20
emccormickNo worries med_. We're on side topics ;)14:20
emccormicksnow?14:20
med_tc election is on-going.14:20
mihalis68specific feedback about "upstream LTS updates" states that they are near impossible without first doing something about the underlying python foundation14:21
med_emccormick, stupid android client flaking whilst I was commuting.14:21
mihalis68med_  you were actioned to report back from TC. Any news on that?14:21
med_nothing to report other than elections under way14:21
smcginnisI'm not sure if it's really a python issue. My stance is still what I was saying in Mexico that we need more vendor involvement to maintain those longer stable releases.14:21
* med_ can't grok how python foundation would be involved14:22
mihalis68ok, well I am not a python developer, so take this with a pinch of salt, but...14:22
mihalis68you can't maintain openstack components for 3 years if they depend on something that is not maintained for 3 years14:23
mihalis68right?14:23
mihalis68wel python itself doesn't have LTS, so you can't necessarily even rebuild the stuff 2 years later14:23
mihalis68this is from my canonical contacts, both my contractor and a bunch of other staff that I took out for dinner recenely14:24
med_curious14:24
mihalis68maybe someone who is a python developer can explain this in more detail14:24
smcginnismihalis68: There can be issues as far as required packages no longer being maintained, or things like distros moving from python 3.4 to 3.5 to 3.6.14:24
mihalis68the python that underpins OpenStack Liberty is no longer actively maintained14:24
mihalis68for example14:25
smcginnisThere are a lot of moving pieces with LTS. That's part of the need for maintenance, because even though something is working now, it doesn't mean something won't change in the runtime three years from now that breaks it.14:25
shintaroThat conversation reminded me of polling Allison Randal for Forum sesison from Suse14:25
mihalis68I realize many things underpin a "stack" that big, but it's quite intimate when it comes to python specifically14:25
smcginnismihalis68: Good points.14:25
mihalis68ok. I guess I should be a good chair and move on to next agenda item. This topic will be discussed in Sydney, however, as the upstream LTS releases talk was accepted onto the draft session list (see email from thing)14:26
mihalis68*thingee14:26
mihalis68#topic Sydney14:26
*** openstack changes topic to "Sydney (Meeting topic: Ops Meetup Team)"14:26
mihalis68did everyone see that list?14:27
mihalis68look for email entitled "[Openstack-operators] [forum] Draft Schedule - Deadline Oct 13 Friday 20:00 UTC"14:27
mihalis68from Mike Perez (thingee)14:27
shintaroI guess the Forum schedule is now open14:27
shintaroI mean on the official schedule already14:28
mrhillsmano/14:28
emaganamihalis68: I was expecting a lot more Forum sessions from the Ops prespective14:28
thingeehttp://lists.openstack.org/pipermail/openstack-dev/2017-October/123699.html14:28
thingeehey all sorry, I meant to send this to the ops list too. I'll do that right now.14:28
med_thanks mike14:28
* med_ has seen THAT one14:29
smcginnisHere's a nice session: What do operators want from the stable policy?14:29
mihalis68very apropos14:29
mihalis68hi mrhillsman, thingee14:29
emccormickemagana Operators really slacked proposing things, but lots of the project teams have crossover things in there.14:30
emccormickIt worked kinda that way in Boston too14:30
emaganaemccormick: fair enough14:31
mihalis68is there anything else we need to try to get organized for Sydney? I forget where the idea of an evening event got to14:31
mihalis68any more on Sydney? I imagine that schedule of talks will take a while to digest14:32
mihalis68ok14:33
mihalis68#topic Tokyo mid-cycle meetup14:33
*** openstack changes topic to "Tokyo mid-cycle meetup (Meeting topic: Ops Meetup Team)"14:33
mihalis68shintaro had two questions on the agenda14:33
mihalis68is $20 admission fee acceptable to all?14:33
shintaroyes. need that for Eventbite14:33
mihalis68and is 150 person capacity enough?14:33
mihalis68in my view yes and yes14:33
mihalis68thoughts?14:33
med_+1 +114:33
mrhillsman++14:34
mihalis68any objections to either?14:34
shintaroseems not.14:34
mihalis68I find it very unlikely14:34
shintarook I will move on with those numbers.14:34
mihalis68#agreed $20 admission fee and 150-person capacity are both suitable for this event14:34
*** chlong has quit IRC14:34
mihalis68great14:34
mihalis68we can get the eventbrite issued, then start promotion14:35
emccormickgood on both fronts14:35
mihalis68#action mihalis68 to submit blog about tokyo meetup14:35
shintaroone bad news is that the beer place emccormick suggested may not be available for reservation on week days. but still confirming14:35
mihalis68shintaro do you want to update the event landing page on the openstack.org wiki with the eventbrite when it's created?14:35
emccormickTell them lots of Americans with big livers will be coming. They'll make lots of money.14:36
mihalis68we run openstack, so we can certainly organize a beer outing on tokyo14:36
mihalis68*in tokyo14:36
shintaroI will. and we will get graphics from the Foundation after Sydney.14:36
smcginnisThe beer place is pretty big from what I remember. May be able to still just drop in there.14:36
mihalis68#action shintaro to update Tokyo event landing page14:36
emaganacan somebody remind me the dates?14:36
med_pro-tip: If you have limited time in Tokyo, skip the Robot Restaurant.14:36
smcginnis:)14:36
smcginnisMarch 8-9, right?14:37
mihalis68I'm going to book tokyo once the evenbrite comes up14:37
shintaroMarch 7-814:37
mihalis68I keep forgetting that I'm going!14:37
smcginnisAh, I was close. :)14:37
shintaroWed and Thursday14:37
shintarono more update on Tokyo for now14:38
mihalis68Hmmm, I wonder if I can work from Tokyo on friday and then take Saturday for tourism. We have an office there14:38
med_+114:38
mihalis68ok thanks shintaro. I am excited about this one14:38
mihalis68#topic future events14:38
emaganaThanks!14:38
*** openstack changes topic to "future events (Meeting topic: Ops Meetup Team)"14:38
med_I can recommend the tokyo tower14:38
emccormickSkytree? +114:39
shintaroI would recommend new Sky-Tree tower :)14:39
mihalis68Vancouver is set to be next Summit, but too early to plan for. After that we thought the next mid-cycle would be Europe?14:39
med_yep that one14:39
med_sorry, had the wrong name14:39
mihalis68there was agreement to try and agree the geo-region for that meet up this week, IIRC14:39
emccormickI thought our next would be NAM east14:39
emccormickfollowing pattern anyway14:40
smcginnisI like the idea of having the ops midcycle colocated with the next PTG. Though my schedule conflicts there are already bad enough, could help getting some other ops-dev interaction.14:40
mihalis68where will the PTG be then?14:40
mihalis68geographically, not precisely14:40
shintaroLauren said the location is not fixed yet14:41
smcginnisDublin is the one right before the Tokyo ops midcycle. Next after that should be somewhere North America.14:41
mihalis68well, NAM would be convenient but mexico just happened, so if we do tokyo and then NAM again that seems off to me14:42
emaganasmcginnis: PTG in Dublin, Ireland?  When?14:42
* med_ just asked Fdn for dates. nothing on website I can see14:43
smcginnisFebruary I believe emagana14:43
emccormickNA East and NA West are considered separate regions14:43
aprice___it is going to be announced soon14:43
aprice___re: Dublin.14:43
smcginnisProbably a week or two before Tokyo.14:43
aprice___still finalizing contracts14:43
emaganasmcginnis: cheers!14:43
smcginnisemagana: ;)14:43
smcginnisaprice___: Thanks!14:43
emccormickso NA West, Asia, NA East, EU, rinse and repeat14:43
med_ah, it leaked out in some Queens PTG wrapup emails14:43
mihalis68emc this is more precise a definition than I am aware of. I thought the idea was to rotate NAM, EUR and APAC14:43
*** simon-AS5592 has quit IRC14:43
emccormicksummit flip flops the NA regions14:44
emccormickThat's what Summits do14:44
smcginnisYeah, I think Thierry officially stated it, just not a firm "when".14:44
mihalis68and which bit is mexico city in?14:44
emccormickPortland, Hong Kong, Atlanta, Paris14:44
mihalis68has it been stated that ops mid cycles follow that policy? I hadn't seen that14:44
emccormickVancouver, Tokyo, Austin, Barcelona14:44
emccormicksee?14:44
mihalis68yes I see that's the one for summits14:45
med_emccormick, but I think this group wanted the 3 region rotation. This group/team/etc sets their own policy14:45
mihalis68but also I see that openstack is weak in the NE USA now14:45
mihalis68sorry, but I think it is14:45
emccormickif only by accident we have14:45
mihalis68openstack days east was cancelled due to lack of interest14:45
med_lack of vendor support I think14:45
mihalis68thanks med_ I am not against EMC's suggestion, it's just not how I remember it!14:46
med_also why I didn't try for a Rocky Mountain OpenStack Days.14:46
mihalis68obviously for me NE USA is GREAT!14:46
emccormickit shouldn't be14:46
mihalis68oh I see openstack days needs vendors? It's one of *those things* :|14:46
emccormickWe've got a huge Redhat presence here and in Raleigh14:46
* med_ would have to look through meeting logs to see if we every #actioned or #decisioned 3 way rotation14:46
emccormickComcast and Walmart are here and in Philly14:46
med_mihalis68, it's kind of expensive.14:47
mihalis68even if it was hash agreed, it could be changed14:47
med_truly14:47
mihalis68I think Comcast openstack is near death14:47
* med_ is fully ambivalent but unlikely to travel beyond USA/Canada for Ops Midcycle14:47
mihalis68proposal : email the list and ask for interest level in a mid-cycle in europe in that slot?14:48
*** chlong has joined #openstack-operators14:48
mihalis68or is it likely that these events will merge with PTG and just go where they go?14:48
shintaroI think giving a shot for europe is a good idea and if we can't find the host, then we can go for co-location with PTG or something14:49
mihalis68maybe a better idea is to get the community to express a view on joining PTG cycle/location?14:49
* med_ knows some people relatively recently joined Comcast OpenStack and don't think it's going away14:49
emccormickmihalis68 They are still hiring Openstack people here and in Philly both. Doesn't seem too dead yet ;)14:49
mihalis68maybe I am guilty of repeating the biased view from the Walmart folks (formerly at ComCast)14:50
emccormickRE: joining PTG, this still makes me kinda squirmy on the Devs behalf.14:50
mihalis68I am glad to hear it's not pining for the fjords14:50
emccormickI would basically want an invite from them as a group14:50
mihalis68I'm ambivalent, to reuse med_s great description. I like the independent spirit of separate mid-cycles14:51
mihalis68but then I think of how difficult it was to get the mexico event off the ground14:51
*** catintheroof has joined #openstack-operators14:51
emccormickIt's not pining, it's passed on!14:51
emagana+214:51
mihalis68ok, as chair I think I can safely say no consensus, debate continues14:51
emccormickwhoops, wrong python14:52
emccormickSo we have 2 open questions I guess.14:52
*** Weiguo has joined #openstack-operators14:52
emccormick1) Do we or do we not colocate with the PTG beyond Tokyo14:52
emccormick2) If not, do we have a 3 region or 4 region rotation?14:53
VWI'm still leaning towards no14:53
mihalis68I believe it's 314:53
VWbut I can be convinced.14:53
mihalis68it's weird to colocate but not on same days14:53
mihalis68(I think that's the idea, or am I wrong?)14:53
* med_ is more and more confused but is patient and waits for a summary14:54
emccormickPTG runs a whole week. How would we avoid overlap?14:54
smcginnisThe risk with 1 is they wanted the PTG to get away from the issues of the summit of "oh, I need to leave this important design discussion to give a presentation". Some risk of reintroducing that with colocation.14:54
mihalis68It would be interesting to find out if the foundation expects to do every other summit in NA, viewing it as two regions going forward14:54
med_agreed, you have to overlap with either the first two days or the last three days (or right in the middle and overlap both)14:54
emaganaIt will be easy to justify a trip to week and days for two events, than two trips to different locations.14:54
smcginnismihalis68: Maybe aprice___ can answer that?14:54
med_thingee, aprice___ pretty sure NA is every other for both Summits and PTGs14:55
emaganaDoes the PTG need the whole week?14:55
med_is that about right?14:55
mihalis68I think perhaps I have not read a good enough definition of what is actually being proposed re: PTG14:55
emaganaI would think that 3 days for PTG and 2 days for Ops14:55
med_emagana, they use the whole week as there are so much going on14:55
smcginnisemagana: Yeah, we filled the week and really could have used more.14:55
mihalis68so after Berlin, Summit is due in NE NAM?14:55
smcginnis2 days of cross-project stuff, 3 days of project specific.14:55
emaganasmcginnis: understand it.. I used to be a developer!  :'(14:56
emccormickmihalis68 yes14:56
mihalis68let me just squeeze in my last agenda item14:56
aprice___I don't think that anything is finalized re: Summits post Berlin, but to date, we have alternated NA every other Summit, yes14:56
med_I'm not sure "NE NAM" just NAmerica14:56
mihalis68can everyone who appears on #link https://wiki.openstack.org/wiki/Ops_Meetups_Team please affirm they still want to be on the team or not?14:56
shintaroo/14:57
VWyes - the PTG is where the devs shuould really be diving in to blueprints and the HOW of new features/fixes that were discussed at the forum (the what).  The Ops mid-cycle is much more about getting Operators engaged in the larger community14:57
emccormick<aprice___> is the east / west alternating just an accident?14:57
mihalis68med_ it is EMC's contention that  NAM is two zones for planning purposes14:57
VWI worry about trying to put them together and risk losing their purpose14:57
VWI'm still in mihalis6814:57
mihalis68thanks guys14:57
mihalis68I will email matt jarvis and tom and ask this question14:57
VWbut I have to run to my next meeting here14:57
VWsee you all next week14:57
mihalis68it might seem harsh, but I want to see the real team size14:57
aprice___emccormick: I wouldn14:57
mihalis68thanks VW14:57
med_mihalis68, team or team organizers?14:57
emaganaThanks for leading the conversations mihalis6814:58
mihalis68my pleasure14:58
aprice___I wouldn't say accident as we try to change the location in NA to accommodate different areas and communities14:58
*** VW_ has joined #openstack-operators14:58
mihalis68team organizers14:58
* med_ is not much of an organizer, obviously14:58
mihalis68like I think Matt is out, right?14:58
mihalis68best clean that page up14:58
mihalis68I'm going to do it based on responses here and email14:59
emccormickSo it would be unlikely to do the next NAM in, say, Seattle.14:59
mihalis68last call for input14:59
mihalis68I think the rotation discussion has to carry on14:59
*** sdague has quit IRC14:59
med_thanks mihalis68 all.14:59
mihalis68thanks everyone14:59
* med_ goes to next meeting14:59
mihalis68#endmeeting14:59
*** 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/"14:59
shintarothanks14:59
openstackMeeting ended Tue Oct 17 14:59:49 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-17-14.02.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-17-14.02.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetup_team/2017/ops_meetup_team.2017-10-17-14.02.log.html14:59
*** shintaro has quit IRC15:00
emccormickThanks guys. Have a great week15:00
smcginnisThanks!15:00
mihalis68shintaro reminder I emailed you about my article15:00
*** smcginnis has left #openstack-operators15:00
*** VW_ has quit IRC15:01
*** VW_ has joined #openstack-operators15:01
*** VW has quit IRC15:02
*** catintheroof has quit IRC15:03
mihalis68emccormick your idea of the rotation matches this https://wiki.openstack.org/wiki/Operations/Meetups15:12
mihalis68but I think the discussions on this topic were somewhat different.15:13
mihalis68@emccormick15:13
*** penick has joined #openstack-operators15:13
*** bollig has quit IRC15:17
*** markvoelker has quit IRC15:17
*** bollig has joined #openstack-operators15:17
*** markvoelker has joined #openstack-operators15:18
*** Oku_OS is now known as Oku_OS-away15:18
*** markvoelker has quit IRC15:22
*** chyka has joined #openstack-operators15:23
*** AlexeyAbashkin has quit IRC15:30
*** AlexeyAbashkin has joined #openstack-operators15:30
*** Caterpillar2 has joined #openstack-operators15:40
*** AlexeyAbashkin has quit IRC15:41
*** simon-AS559 has joined #openstack-operators15:42
*** simon-AS559 has quit IRC15:43
*** Caterpillar has quit IRC15:44
*** chyka_ has joined #openstack-operators15:45
*** chyka has quit IRC15:47
*** aojea has joined #openstack-operators15:50
*** aojea has quit IRC15:54
*** Caterpillar2 is now known as Caterpillar15:56
*** slaweq has joined #openstack-operators15:59
*** bjolo_ has quit IRC16:00
*** pcaruana has quit IRC16:01
*** VW has joined #openstack-operators16:04
*** VW_ has quit IRC16:08
*** Apoorva has joined #openstack-operators16:11
*** yprokule has quit IRC16:16
*** simon-AS559 has joined #openstack-operators16:28
*** VW has quit IRC16:29
*** simon-AS5591 has joined #openstack-operators16:30
*** simon-AS559 has quit IRC16:33
*** penick_ has joined #openstack-operators16:38
*** penick has quit IRC16:40
*** VW has joined #openstack-operators16:44
*** VW_ has joined #openstack-operators16:45
*** VW has quit IRC16:48
*** arnewiebalck_ has joined #openstack-operators16:49
*** aojea has joined #openstack-operators16:50
*** aojea has quit IRC16:55
*** tesseract has quit IRC17:02
*** slaweq has quit IRC17:04
*** emagana has quit IRC17:05
*** penick_ has quit IRC17:05
*** emagana has joined #openstack-operators17:05
*** emagana has quit IRC17:07
*** penick has joined #openstack-operators17:07
*** derekh has quit IRC17:09
*** simon-AS5591 has quit IRC17:10
*** emagana has joined #openstack-operators17:13
*** AlexeyAbashkin has joined #openstack-operators17:22
*** AlexeyAbashkin has quit IRC17:24
*** fandrieu has quit IRC17:27
*** penick_ has joined #openstack-operators17:27
*** penick has quit IRC17:30
*** penick_ has quit IRC17:36
*** dfflanders has quit IRC17:50
*** aojea has joined #openstack-operators17:51
*** fragatina has quit IRC17:53
*** aojea has quit IRC17:56
*** slaweq has joined #openstack-operators17:57
*** penick has joined #openstack-operators18:00
*** dminer has quit IRC18:01
*** slaweq has quit IRC18:02
*** Apoorva_ has joined #openstack-operators18:02
*** Apoorva has quit IRC18:05
*** MVenesio has joined #openstack-operators18:11
emccormickmihalis68 Yeah. Apparently the East / West thing is mainly just a side effect of trying to make sure they are spread out in NAM. There's no policy that says it has to be a certain distance apart18:21
gregworkis there a way to pass custom qemu options via nova when an instance is spawned ?18:25
*** penick has quit IRC18:30
*** bjolo_ has joined #openstack-operators18:31
*** aojea has joined #openstack-operators18:38
*** electrofelix has quit IRC18:39
VW_cool - thanks for sharing emccormick18:41
*** Apoorva_ has quit IRC18:43
*** VW_ is now known as VW18:43
*** Apoorva has joined #openstack-operators18:43
*** aojea has quit IRC18:47
*** emagana has quit IRC18:51
*** VW has quit IRC18:55
*** VW has joined #openstack-operators18:55
*** slaweq has joined #openstack-operators19:02
*** ChiTo has joined #openstack-operators19:06
*** simon-AS559 has joined #openstack-operators19:15
*** simon-AS5591 has joined #openstack-operators19:17
*** simon-AS559 has quit IRC19:18
*** simon-AS559 has joined #openstack-operators19:21
*** simon-AS5591 has quit IRC19:23
*** fandrieu has joined #openstack-operators19:24
*** slaweq has quit IRC19:24
*** mihalis68 has quit IRC19:25
*** markvoelker has joined #openstack-operators19:26
*** slaweq has joined #openstack-operators19:38
*** AlexeyAbashkin has joined #openstack-operators19:40
*** slaweq has quit IRC19:40
*** slaweq has joined #openstack-operators19:41
*** aojea has joined #openstack-operators19:43
*** AlexeyAbashkin has quit IRC19:44
*** penick has joined #openstack-operators19:45
*** aojea has quit IRC19:48
*** catintheroof has joined #openstack-operators19:49
*** arnewiebalck_ has quit IRC19:50
*** gregwork has quit IRC19:54
*** gregwork has joined #openstack-operators19:54
*** fragatina has joined #openstack-operators19:55
*** emccormickva has joined #openstack-operators20:04
*** slaweq has quit IRC20:04
*** ChiTo has quit IRC20:07
*** emccormick has quit IRC20:08
*** fragatina has quit IRC20:08
*** dmibrid_ has joined #openstack-operators20:14
*** markvoelker_ has joined #openstack-operators20:15
*** chlong has quit IRC20:16
*** markvoelker has quit IRC20:18
*** AlexeyAbashkin has joined #openstack-operators20:22
*** AlexeyAbashkin has quit IRC20:27
*** catintheroof has quit IRC20:35
*** catintheroof has joined #openstack-operators20:36
*** catintheroof has quit IRC20:36
*** ansmith has quit IRC20:43
*** aojea has joined #openstack-operators20:44
*** umbSublime has quit IRC20:44
*** christx2 has joined #openstack-operators20:47
*** aojea has quit IRC20:49
*** umbSublime has joined #openstack-operators20:49
*** umbSublime has quit IRC20:49
*** umbSublime has joined #openstack-operators20:49
*** dminer has joined #openstack-operators20:53
*** emagana has joined #openstack-operators20:54
*** MVenesio has quit IRC20:57
*** simon-AS559 has quit IRC21:04
*** VW has quit IRC21:12
*** chlong has joined #openstack-operators21:17
*** fragatina has joined #openstack-operators21:30
*** ansmith has joined #openstack-operators21:35
*** aojea has joined #openstack-operators21:45
*** fragatina has quit IRC21:48
*** aojea has quit IRC21:49
*** Apoorva_ has joined #openstack-operators21:59
*** Apoorva has quit IRC22:03
*** dminer has quit IRC22:05
*** Weiguo has quit IRC22:06
*** VW has joined #openstack-operators22:07
*** fandrieu has quit IRC22:07
*** VW_ has joined #openstack-operators22:13
*** VW has quit IRC22:17
*** VW_ has quit IRC22:18
*** penick has quit IRC22:22
*** Adri2000 has quit IRC22:25
*** christx2 has quit IRC22:27
*** bjolo_ has quit IRC22:39
*** catintheroof has joined #openstack-operators22:43
*** chyka_ has quit IRC23:11
*** Apoorva_ has quit IRC23:11
*** Apoorva has joined #openstack-operators23:11
*** catintheroof has quit IRC23:17
*** fandrieu has joined #openstack-operators23:23
*** emagana has quit IRC23:26
*** emagana has joined #openstack-operators23:27
*** emagana has quit IRC23:31

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