Tuesday, 2016-06-14

*** jamesdenton has joined #openstack-operators00:18
*** gyee has quit IRC00:21
*** piet_ has joined #openstack-operators00:26
*** saneax is now known as saneax_AFK00:41
*** zul has joined #openstack-operators01:04
*** Apoorva_ has quit IRC01:04
*** fragatina has quit IRC01:23
*** piet_ has quit IRC01:39
*** zul has quit IRC01:41
*** zul has joined #openstack-operators01:54
*** piet_ has joined #openstack-operators02:07
*** mfisch has quit IRC02:10
*** VW has joined #openstack-operators02:14
*** VW has quit IRC02:19
*** julim has joined #openstack-operators02:29
*** VW has joined #openstack-operators02:36
*** jamesdenton has quit IRC02:48
*** openstackgerrit has quit IRC03:11
*** openstackgerrit has joined #openstack-operators03:11
*** piet_ has quit IRC03:16
*** ducttape_ has quit IRC03:50
*** saneax_AFK is now known as saneax04:16
*** markvoelker has quit IRC04:16
*** cartik has joined #openstack-operators04:27
*** dtrainor has quit IRC04:29
*** pcaruana has quit IRC04:39
*** VW has quit IRC04:41
*** fragatina has joined #openstack-operators04:45
*** fragatina has quit IRC04:50
*** markvoelker has joined #openstack-operators05:17
*** cartik has quit IRC05:19
*** markvoelker has quit IRC05:22
*** liverpooler has quit IRC06:00
*** liverpooler has joined #openstack-operators06:01
*** rcernin has joined #openstack-operators06:11
*** pcaruana has joined #openstack-operators06:16
*** openstackgerrit has quit IRC06:48
*** openstackgerrit has joined #openstack-operators06:48
*** ducttape_ has joined #openstack-operators06:51
*** klindgren has quit IRC06:54
*** simon-AS559 has joined #openstack-operators06:55
*** tesseract has joined #openstack-operators06:56
*** Hosam has joined #openstack-operators06:56
*** Hosam has quit IRC06:56
*** ducttape_ has quit IRC06:56
*** Hosam has joined #openstack-operators06:56
*** cllewellyn_ has joined #openstack-operators06:59
*** cllewellyn_ has quit IRC07:00
*** cllewellyn__ has joined #openstack-operators07:00
*** cllewellyn__ has quit IRC07:01
*** cllewellyn__ has joined #openstack-operators07:01
*** jeh has quit IRC07:09
*** zeih has joined #openstack-operators07:11
*** markvoelker has joined #openstack-operators07:18
*** simon-AS5591 has joined #openstack-operators07:18
*** simon-AS559 has quit IRC07:18
*** markvoelker has quit IRC07:22
*** bsv has joined #openstack-operators07:26
*** dmk0202 has joined #openstack-operators07:32
*** cllewellyn__ has quit IRC07:32
*** cllewellyn_ has joined #openstack-operators07:37
*** zeih has quit IRC07:47
*** jeh has joined #openstack-operators07:48
*** jeh has quit IRC07:48
*** jeh has joined #openstack-operators07:48
*** fragatina has joined #openstack-operators07:49
*** dbecker has joined #openstack-operators07:50
*** fragatina has quit IRC07:55
*** zeih has joined #openstack-operators08:05
*** zeih has quit IRC08:06
*** zeih has joined #openstack-operators08:09
*** cllewellyn_ has quit IRC08:25
*** admin0 has joined #openstack-operators08:30
*** cllewellyn_ has joined #openstack-operators08:30
*** cllewellyn_ has quit IRC08:31
*** cllewellyn_ has joined #openstack-operators08:31
*** klindgren has joined #openstack-operators08:38
*** snecklifter has joined #openstack-operators08:38
*** derekh has joined #openstack-operators08:40
*** matrohon has joined #openstack-operators08:50
*** ducttape_ has joined #openstack-operators08:52
*** ducttape_ has quit IRC08:58
*** snecklifter has left #openstack-operators09:04
*** sticker has joined #openstack-operators09:14
*** racedo has joined #openstack-operators09:15
*** zeih has quit IRC09:15
*** admin0 has quit IRC09:16
*** racedo has quit IRC09:18
*** admin0 has joined #openstack-operators09:18
*** electrofelix has joined #openstack-operators09:26
*** zeih has joined #openstack-operators09:27
*** admin0 has quit IRC09:35
*** admin0 has joined #openstack-operators09:36
*** admin0 has quit IRC09:37
*** gfa has quit IRC09:39
*** admin0 has joined #openstack-operators09:40
*** admin0 has quit IRC09:43
*** zeih has quit IRC09:48
*** admin0 has joined #openstack-operators09:57
*** gfa has joined #openstack-operators09:58
*** admin0 has quit IRC10:00
*** dmk0202 has quit IRC10:08
*** admin0 has joined #openstack-operators10:09
*** zeih has joined #openstack-operators10:23
*** zeih has quit IRC10:27
*** zeih has joined #openstack-operators10:28
*** admin0 has quit IRC10:35
*** admin0 has joined #openstack-operators10:36
*** admin0 has quit IRC10:50
*** admin0 has joined #openstack-operators10:50
*** ducttape_ has joined #openstack-operators10:54
*** admin0 has quit IRC10:55
*** ducttape_ has quit IRC10:59
*** zeih_ has joined #openstack-operators11:02
*** zeih has quit IRC11:02
*** permalac has quit IRC11:09
*** liverpooler has quit IRC11:17
*** liverpooler has joined #openstack-operators11:17
*** admin0 has joined #openstack-operators11:28
*** zeih_ has quit IRC11:32
*** cllewellyn_ has quit IRC11:41
*** piet has joined #openstack-operators11:44
*** admin0 has quit IRC11:50
*** ducttape_ has joined #openstack-operators11:54
*** piet has quit IRC11:58
*** ducttape_ has quit IRC12:03
*** zeih has joined #openstack-operators12:06
*** fragatina has joined #openstack-operators12:11
*** markvoelker has joined #openstack-operators12:13
*** matrohon has quit IRC12:15
*** fragatina has quit IRC12:16
*** paramite has joined #openstack-operators12:20
*** zeih has quit IRC12:21
*** matrohon has joined #openstack-operators12:25
*** cllewellyn_ has joined #openstack-operators12:27
*** cllewellyn_ has quit IRC12:28
*** cllewellyn__ has joined #openstack-operators12:28
*** Hosam has quit IRC12:29
*** fwdit has joined #openstack-operators12:30
*** Hosam has joined #openstack-operators12:30
*** Hosam has quit IRC12:34
*** zeih has joined #openstack-operators12:36
*** admin0 has joined #openstack-operators12:36
*** cllewellyn__ has quit IRC12:45
*** racedo has joined #openstack-operators12:46
*** piet has joined #openstack-operators12:49
*** jamesdenton has joined #openstack-operators12:50
*** piet has quit IRC12:51
*** piet has joined #openstack-operators12:53
*** zeih has quit IRC12:54
*** admin0 has quit IRC12:54
*** admin0 has joined #openstack-operators12:59
*** zeih has joined #openstack-operators12:59
*** zeih has quit IRC13:01
*** racedo has quit IRC13:19
*** pilgrimstack has joined #openstack-operators13:20
*** piet has quit IRC13:22
*** pilgrimstack has quit IRC13:24
*** fwdit has quit IRC13:24
*** shintaro has joined #openstack-operators13:30
*** admin0 has quit IRC13:31
*** admin0 has joined #openstack-operators13:32
*** bsv has quit IRC13:33
*** mriedem_away is now known as mriedem13:33
*** jsheeren has joined #openstack-operators13:38
*** piet has joined #openstack-operators13:39
*** dminer has joined #openstack-operators13:43
*** racedo has joined #openstack-operators13:46
*** fifieldt has joined #openstack-operators13:47
fifieldtbenefits of ipv6 #3127 - being able to get on freenode without complicated SASL setup13:51
*** ckonstanski has quit IRC13:51
*** cdelatte has joined #openstack-operators13:56
*** admin0 has quit IRC13:59
*** admin0 has joined #openstack-operators14:00
fifieldtanyone here for the ops meetups team meeting?14:01
mrhillsmano/14:01
*** mihalis68 has joined #openstack-operators14:01
fifieldtyay!14:01
serverascodeyup14:01
shintaroo/14:01
fifieldtfantastic14:01
*** vnogin has joined #openstack-operators14:01
fifieldtlet me hit the button14:01
fifieldt#startmeeting Ops Meetups Team14:01
openstackMeeting started Tue Jun 14 14:01:39 2016 UTC and is due to finish in 60 minutes.  The chair is fifieldt. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
openstackThe meeting name has been set to 'ops_meetups_team'14:01
fifieldtHello all, and welcome to the third meeting of the Ops Meetups Team :) It's great to have you here.14:01
mihalis68I only have unpaid irc cloud access so far from work, so anything before I joined I can't see14:01
fifieldtyou're just in time - nothign yet :)14:02
*** admin0 has quit IRC14:02
fifieldtNB: If you're new, or just idling in the channel, be sure to have read:14:02
fifieldt#link https://wiki.openstack.org/wiki/Ops_Meetups_Team14:02
fifieldtfor background.14:02
mihalis68glad to be here this time, sorry I missed the last one14:02
fifieldtToday's agenda is fairly exciting. We had a great discussion on the sizing of meetups on the ML, and our friends at BestBuy and Bloomberg have both come back with fantastic information about their venues.14:02
fifieldt# link https://etherpad.openstack.org/p/ops-meetups-team14:02
fifieldtWe need to come to a very rapid decision on the venue for the August meetup. This meeting will be critical for that.14:02
fifieldtThough, we also need to spend some time every meeting thinking about the "big picture" plan :)14:02
fifieldtAs always: please write your name down on the agenda etherpad as a way of introduction, since we're a new crew. Also, please help to collaboratively summarise the discussion.14:02
fifieldtSecondly, if there's something else burning to put on the agenda (very likely I've missed something obvious), please add it to that same etherpad.14:02
fifieldtNow, onto the first topic:14:02
fifieldt#topic Review of actions from previous meeting14:02
*** admin0 has joined #openstack-operators14:02
fifieldtWe had 3 main action items14:02
fifieldt1.     gfa_ and fifieldt to email Bloomberg and BestBuy to determine venue feasibility for the August ops meetup14:02
fifieldtThis one will be its own agenda item14:02
fifieldt2.     dc_mattj to write the justificaiton for smaller meetups and communication on the M14:03
fifieldtML*14:03
fifieldtThis was done14:03
fifieldtin general there was support for what was discussed in this meeting last time14:03
*** admin0 has quit IRC14:03
fifieldtI will followup with dc_mattj and vw since they don't appear to be here to get them to summarise the discussion14:03
*** admin0 has joined #openstack-operators14:04
fifieldt#action fifieldt to ask dc_mattj and vw to summarise smaller meetup discussion :)14:04
fifieldt3.    mrhillsman to write up a proces for managing the waitlist and send to ML for discussion14:04
fifieldtThis was a lower-priority action :)14:04
mrhillsmanboooo14:04
fifieldtso it's cool to have it take a bit longer14:04
fifieldtshall we keep it as an action, mrhillsman ? :)14:04
mrhillsmani sent email - basically using eventbrite14:04
fifieldtoh!14:04
fifieldtI missed it14:05
mrhillsmanno one objected from what i saw14:05
fifieldtcool14:05
fifieldtlooks like we've got a process then :)14:05
fifieldtmark it off :)14:05
fifieldtok, enough administrivia then14:05
fifieldtI'm sure everyone is really keen to talk about the first agenda item14:05
fifieldtunless there were issues with the other action items?14:05
fifieldtok14:06
fifieldt#topic Report from the August 2016 Midcycle Venue selection crew14:06
fifieldtgfa, shintaro14:06
fifieldtare you available to give a quick rundown?14:06
* fifieldt also keeps in mind that mihalis68 is here too14:06
fifieldtare we OK to link to that etherpad yet?14:07
* fifieldt hears silence14:08
mrhillsman:(14:08
fifieldtok14:08
fifieldtin the interests of driving this forward14:09
fifieldthere's the summary14:09
fifieldtwe emailed both of the crews at bloomberg and bestbuy, with a series of questions and dove deeper into the venues14:09
fifieldtyou can find the summary on14:09
fifieldt#link https://etherpad.openstack.org/p/ops-meetup-venue-discuss14:09
fifieldtplease take a look there and raise questions for the next little bit14:10
fifieldtwhile I keep rambling14:10
fifieldtThe good and bad news is that both venues seem very good :)14:10
*** shintaro has quit IRC14:10
fifieldtboth have large theatres of size 150-20014:10
fifieldtat least another breakout room that does 3014:11
fifieldtthey're not soulless "hotel"-like spaces either :)14:11
fifieldtso we have a really difficult decision ahead of us14:11
fifieldtI'm not sure if mihalis68 feels like spruiking? :)14:11
mihalis68I don't know, I've never spruiked!14:12
*** ducttape_ has joined #openstack-operators14:12
fifieldtwe're engineers, it's not in our ability :P14:12
fifieldtwell, the big question is:14:12
fifieldthow do we decide ?14:12
*** shintaro has joined #openstack-operators14:12
fifieldtwelcome back sir shintaro :)14:12
*** ducttape_ has quit IRC14:12
*** ducttape_ has joined #openstack-operators14:13
shintarodon't know why but I was off line14:13
fifieldtall good :)14:13
fifieldtI just sent a link to our venue specs etherpad14:13
fifieldtand posed the question14:13
fifieldt"How do we decide?"14:13
fifieldtWe need to decide how to decide today, in this meeting :)14:13
mrhillsmani like the idea of the nyc venue because it coincides with openstack days east14:13
*** admin0 has quit IRC14:13
shintaroyes, both looks good and not much difference14:14
serverascodeare the facilities essentially equivalent? seems like it14:14
mihalis68I am a bit hesitant to comment, being one of the "hosts"14:14
fifieldtI consider your opinion as valid as any mihalis68 :)14:14
*** admin0 has joined #openstack-operators14:14
mihalis68however an idea might be to ask for "likely attendance" for each venue from mailing list members14:14
mihalis68I mean, if seattle in August were to look like drawing a better crowd, I'd go to seattle happily14:15
serverascodeI think it becomes and east coast west coast question14:15
mihalis68where was the last NA one?14:15
mihalis68sorry, I should khow14:15
fifieldtwest coast14:15
fifieldtpalo alto14:15
mihalis68I went to Philly last year14:15
mihalis68or was that 2 years ago, OMG14:16
fifieldtMar 2015 :)14:16
mihalis68ok, so not entirely losing mind14:16
mihalis683 summits since then14:16
fifieldtwhat do others think about asking "likely attendance" for each venue from mailing list members14:17
mihalis68maybe I should make statements and see if there are comments14:17
mihalis68are both offers suitable to everyone according to the selection criteria?14:17
fifieldt#link https://wiki.openstack.org/wiki/Operations/Meetups#Venue_Selection14:17
mrhillsman+114:18
*** dc_mattj has joined #openstack-operators14:18
shintaroI guess both looks fine14:18
fifieldthi dc_mattj14:18
dc_mattjafternoon, sorry I'm late14:18
fifieldtquick summary for you dc_mattj: both bloomberg and bestbuy venues seem feasible14:18
fifieldtthere's an etherpad at https://etherpad.openstack.org/p/ops-meetup-venue-discuss14:18
*** VW has joined #openstack-operators14:19
fifieldthi VW14:19
VWhey folks, sorry I'm late14:19
fifieldtquick summary for you VW: both bloomberg and bestbuy venues seem feasible14:19
fifieldtthere's an etherpad at https://etherpad.openstack.org/p/ops-meetup-venue-discuss14:19
fifieldtthe question is: How do we decide?14:19
fifieldtone suggestion so far from mihalis68 was "an idea might be to ask for "likely attendance" for each venue from mailing list members"14:19
fifieldtothers commented on east vs west coast14:19
fifieldtwhat do you think?14:19
mihalis68trying to be neutral, the best buy venue appears to be a tad larger, the NYC venue appears to be on the coast slightly more "due"14:20
dc_mattjfor folks from Europe, NY is obviously better travel wise14:20
fifieldtI'd tend to agree with mihalis68's assessment14:21
mrhillsmani like the idea of asking the mailing list but we need to put a time on it14:21
VWwell, my first reaction - as someone who wants to maximize a limited budged for mid-cycles and Summits - I'd lean towards the option that is less expensive to get to to and to stay in14:21
dc_mattjVW, +114:21
VWbut dc_mattj makes a good point about it being easier to pull from Europe14:21
fifieldtmrhillsman, agreed - we basically need a decision within 7 days, I'd say, to give us the best chance14:22
mihalis68How about we see if we can get a voting with feet direction in a few days?14:22
dc_mattjtravel aside, the breakout rooms seem a bit small on the BestBuy venue /14:22
mrhillsmandoodle poll?14:22
mihalis68"hey everyone, there are these two venues <link>. They both seem ok, could you say which you'd likely attend if chosen?"14:23
*** kstev has joined #openstack-operators14:23
mrhillsman+114:23
fifieldtso, freeform?14:23
fifieldtno doodle poll ?14:23
fifieldtdo we lay more info in the ML post - eg talk about coasts being due, talk about travel, talk about sizing?14:24
fifieldtor keep it as mihalis68 has written?14:24
*** admin0 has quit IRC14:24
* fifieldt stops asking questions14:24
dc_mattjI'd keep it simple14:24
shintaro+1 for mihalis6814:24
dc_mattjdecision needs to be quick14:24
dc_mattjjust lay it out there and get some numbers14:24
*** admin0 has joined #openstack-operators14:24
mihalis68someone not a host nor Tom volunteer to write just the email asking for sentiment? :)14:25
mrhillsmani can if you all do not mind it happening some time from now14:25
mrhillsmani am about to travel so will be afk14:25
mihalis68I can do it today, but I should say that I have an interest in the result14:26
serverascodewhat happens if it seems like there are more ppl than either capacity14:26
mrhillsmanwaiting list14:26
serverascodeok14:26
*** kstev1 has joined #openstack-operators14:27
mihalis68I don't think we can get a bigger venue for august. These are the offers14:27
VWwhat are we pointing them to for details - this etherpad?14:27
mihalis68https://etherpad.openstack.org/p/ops-meetup-venue-discuss14:27
*** racedo has quit IRC14:27
serverascoderight, I suppose I'm saying I'm sure we'll have a good crowd either way14:27
mrhillsmanindeed14:27
VWdo we want to do that with info from those offering up the space?14:27
VWemails, internal processes, etc?14:27
mihalis68the most important thing IMO is choose which and allow it to be locked in an travel planning to start. I am aware that NYC in August is not easy, for example14:27
fifieldtnot sure what the question is VW14:28
fifieldt+1 mihalis6814:28
*** jproulx has joined #openstack-operators14:28
VWI just didn't know if all the info in that etherpad were details we wanted to share publicly, but I re-read it14:29
VWignore me14:29
mihalis68Ok, unless objections, I'll write an email outlining two venues and asking for a response indicating likely attendance ASAP. How should that response be recorded?14:29
VW:)14:29
mihalis68someone mentioned a polll14:29
mihalis68i haven't made a poll, but I like that14:29
mihalis68I do not want to be a mailing list scraper :)14:29
fifieldtyes, so there are two tasks here14:29
*** kstev has quit IRC14:30
fifieldt1. Sending the  "hey everyone, there are these two venues <link>. They both seem ok, could you say which you'd likely attend if chosen?"14:30
fifieldt2. Making a decision from the result14:30
dc_mattj+1 for a poll14:30
mihalis683 tasks14:30
mihalis680 make poll14:30
mihalis681 email14:30
mihalis682 tally14:30
fifieldtack14:30
VWdo we want to have a special, one-off, meeting next Tuesday to review the results?14:30
fifieldtworks for me14:31
mihalis68I can14:31
*** mriedem1 has joined #openstack-operators14:31
mihalis68is there precedent for a poll to select this before?14:31
mihalis68or a similarly quite important decision?14:31
fifieldtnope, this is first time14:31
fifieldtoh, polls get used for others t14:31
fifieldtother stuff14:31
mihalis68one question: will we be able to make real contact with a worthwhile body of operators?14:32
mihalis68I wonder. Could the foundation help just a tad here?14:32
fifieldtideas? :)14:32
mihalis68if we make a poll, getting the word out?14:33
VWif you can get it out today/tomorrow, I have an LDT meeting on Thursday14:33
mihalis68I guess just tweet it and ask foundation to retweet that?14:33
fifieldtconsider it done14:33
VWI'll make sure to point it out to those folks14:33
mihalis68ok who makes the poll?14:33
*** mriedem has quit IRC14:33
fifieldtsomeone should do it immediately14:33
mihalis68someone who knows how, is my suggestion. Not that I think it's hard in principle14:33
fifieldtthere's only two options :)14:33
dc_mattjI think I can make a doodle poll14:33
fifieldtquickly sir, you've got 3 minutes :)14:34
* jproulx lurks in late...14:34
mihalis68ha ha. Now we're cooking with gas14:34
mrhillsmandoodle poll is pretty straight forward14:34
fifieldthi jproulx - basic update: nyc and seattle both good go go for next midcycle.14:34
mihalis68ok dc_mattj makes poll then I email it to the mailing list and tweet it and a few other people tweet and then the foundation?14:35
fifieldttalking about hot to decide14:35
jproulxnice! I see the polling discussion14:35
fifieldtsounds good14:35
mihalis68my email will explain the situation. I can tweet a link to this email in the archives14:35
*** Hosam has joined #openstack-operators14:35
fifieldtthen we meet at this time next week for a quick decision meeting?14:35
mihalis68works for me14:35
fifieldt#action dc_mattj to make a doodle poll with the two midcycle options14:35
fifieldt#action mihalis68 to email out a 'simple' "hey everyone, there are these two venues <link>. They both seem ok, could you say which you'd likely attend if chosen?"14:36
VWNot to side track, but this leaves me with two follow ups.  1.  Do we set the one not chosen up for next summer and get ahead of the game.  2. Do we also try to follow with an East/West/Central type of cycle for North American mid-cycles14:36
fifieldt#action fifieldt to arrange a meeting next Tuesday14:36
fifieldtoh yes, this is a good point14:36
fifieldtwhen is Boston, again?14:36
fifieldtBoston summit14:36
VWApril14:36
VWwell, May14:36
mihalis68that's difficult because I think there was an agreement that next meet up should be opposite the next summit globally14:36
fifieldtah, indeed14:37
mrhillsman^14:37
VWthat's why I said a year from now14:37
mihalis68that's too hard for today. HEAD HURTS14:37
VW:)14:37
VWso +2 midcycles from this one14:37
jproulxSo second place would be after Sydney14:37
mihalis68I can say that if we (Bloomberg) don't have our offer accepted I would expect us to offer again14:37
mihalis68we are really only on the cusp of big openstack action here (such excite!)14:37
mrhillsman@VW 1. i think that would be good if venue agrees 2. also agree with that14:37
dc_mattjhttp://doodle.com/poll/e4heruzps4g94syf14:38
fifieldt#action give that man a beer14:38
jproulx+114:38
dc_mattjshout if it needs any more detail than that14:38
mihalis68very good!14:38
mihalis68simple, elegant14:38
jproulxI like it14:39
fifieldtwell, I think a good reply to mihalis68's post on the ML will be about the summit rotation14:39
fifieldtand talking about the offset there14:39
fifieldtI think we're also likely to get a few east coasters piping up :)14:39
fifieldtsince it's been a while14:39
fifieldtso maybe all will work out as per VW's plan14:39
fifieldt?14:39
mihalis68of course, just getting location "sentiment" maybe makes the strict location rotating slightly less critical14:39
mihalis68I mean if a venue is offered and a lot like it... that's kind of all we need?14:40
mihalis68or have we promised?14:40
mrhillsmanok good peoples, i have to get on the road, apologies for skipping out a bit early14:40
mrhillsmanttyl14:40
fifieldtthanks mrhillsman14:40
fifieldtVW, is the current plan of action here OK, or do you think we need to re-think it?14:40
VWno, looks good14:40
VWwas just thinking outloud14:40
fifieldtyour out loud thoughts are good ones :)14:41
fifieldtOK, so, has this topic made sufficient progress?14:41
VWI'd love to be in a spot where we know venues 6 to 12 months out14:41
fifieldtthat is very true, VW14:41
VWso, I figured we could take advantage of two offers  - either outcome14:41
mihalis68in future I can foresee a "call to host"14:41
jproulxmihalis68 I think we perfer and have made public statements about rotation, but obviously the community could change it's mind...14:41
VWbut hes, fifieldt - sufficient progress made14:41
fifieldtok, in the interests of keeping the meeting lean and clean14:42
fifieldtprovided there are not any remaining concerns people want to raise14:42
fifieldtwe should move on to the next topic?14:42
mihalis68+114:42
jproulx+114:42
shintaro+114:42
VW+114:43
fifieldtok14:43
fifieldtso, my thought was to call this one:14:43
fifieldt#topic     "Big picture" topic of the week14:43
fifieldtIt's easy to get caught up in organising the next one14:43
*** admin0 has quit IRC14:43
fifieldtbut I think VW hits on the right idea - we also need to be thinking about the future14:43
jproulxT14:43
fifieldtwe have so many questions about how these events are going to continue to run14:43
fifieldtmany of them came up in the first meeting14:44
fifieldtso I tried to make a list at14:44
fifieldt#link https://wiki.openstack.org/wiki/Ops_Meetups_Team#Approach14:44
fifieldtIn the last 15 minutes14:44
fifieldtmy hope was that we could choose one topic from there14:44
fifieldtand make some solid progress14:44
fifieldtthoughts?14:44
fifieldtfavo[u]rite topic?14:44
VWwell, we can probably knock a couple off quickly.  Any reason NOT to have two a year?14:45
VWand we are pretty set on about 200 max, right?14:45
fifieldtyes, so last week's topic was the sizing14:45
fifieldtbut, how many per year might seem simple at first14:45
fifieldtcould become more complicated14:46
fifieldtsay, for example, we're pretty happy that 150-200 is the number14:46
jproulxI like the list, seems like something good to review after each event (once we get initial answers down)14:46
fifieldtand we always end up with waiting lists of excellent people14:46
fifieldtwould there be scope for having more events?14:46
fifieldtsuch as a US and an Asia in a single cycle14:47
fifieldtor, a special event for large deployers14:47
fifieldtor telco14:47
*** bzurawski has joined #openstack-operators14:47
fifieldtany thoughts in that kind of direction?14:47
*** julim has quit IRC14:47
fifieldtbecause, I mean, I deally, wouldn't we have tens of thousands of openstack sysadms?14:47
jproulxThink that's a wait & see topic14:47
*** admin0 has joined #openstack-operators14:47
fifieldtquite possibly14:48
fifieldtbut, what happens if a particular geographical community just comes to us and says "hey, we want to organise one!"14:48
jproulxIf we're too big then perhaps specialization becomes the way to go (or perhaps larger events).  I think now we're ok around 200 (though it *may* prove to be a bit restrictive)14:48
fifieldtcall it "Eastern Europe Ops"14:48
VWI like the idea of working group/team related events14:49
VWbut need to think on that14:49
jproulxlike OpenStackDays<Foo> with an operations focus?  sure if there's local organizers who's to say no, the  mor ethe merrier14:49
VWmy gut is to let demand drive increasing the number14:49
dc_mattjVW, +114:49
VWif we get as many or more on the waiting list as we do attending, we know that it's time to increase14:49
mihalis68it does become something different somewhere north of recent sizes14:50
VWor realistically - 50%+ of the attendees on the wait least14:50
shintaroWe are planning to have Ops workshop in Days Tokyo to increase awareness to the OpsMeetups14:50
fifieldt:D14:50
mihalis68even in philly it was often two discussion in different parts of a large room14:50
*** racedo has joined #openstack-operators14:50
jproulxmihalis68 +1 that does become problematic14:50
shintaroI would be great if we have some way to feedback to the original OpSMeetup14:51
jproulxsome sort of integration engine perhaps...14:51
fifieldt*fishslap*14:52
fifieldtindeed shintaro14:52
fifieldtOn that note, and this goes toward mihalis68's recommendation that we communicate more broadly about the venue choice too14:52
fifieldtthere's an entry on the list for14:52
fifieldt* managing "echo chamber" effect, and "elitism"14:52
jproulx+114:53
fifieldtwe've got to make sure we take in every damn viewpoint we can14:53
fifieldtand so having a way to integrate these events like shintaro's ops workshop14:53
fifieldtinto the planning and the participation14:53
fifieldtsounds pretty key :)14:53
fifieldtjust not sure how!14:53
fifieldtthoughts?14:53
jproulxI think geographic rotation helps with this, but not enough.14:53
mihalis68we are meeting in only 7 days14:53
mihalis68maybe we all take an action to ponder the remaining items on the excellent list and have some thoughts we can share then?14:54
dc_mattj+114:54
fifieldtworks for me14:54
mihalis68only 6 minutes left in this meeting anyway14:54
fifieldtanyone down with finishing early?14:54
mihalis68+114:54
jproulxHaving events build on each other so they are an evolving conversation rather than isolated events is a worthy goal14:54
mihalis68agreed14:55
fifieldt+114:55
jproulxthat's my last word for the day :)14:55
fifieldtsomeone should write that down14:55
shintaro+114:55
mihalis68can spend the last 5 minutes googling fish slap for my edification14:55
fifieldt:D:D14:55
fifieldthighly recommended14:55
fifieldtok14:55
fifieldtwell, thank you very much for coming to this meeting14:55
fifieldtwe've made solid progress today thanks to your efforts14:56
dc_mattjtx all14:56
*** ckonstanski has joined #openstack-operators14:56
VWso, same bat time, same bat channel next week?14:56
mihalis68TTFN14:56
mihalis68yes14:56
fifieldtYessir VW14:56
jproulxthanks all!14:56
fifieldtuntil then puppet --noop apply site.pp14:56
fifieldtciao14:56
shintarothanks14:56
fifieldt#endmeeting14:56
openstackMeeting ended Tue Jun 14 14:56:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-06-14-14.01.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-06-14-14.01.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-06-14-14.01.log.html14:56
*** dc_mattj has quit IRC14:57
*** shintaro has quit IRC14:59
*** admin0 has quit IRC15:06
*** fifieldt has quit IRC15:08
*** admin0 has joined #openstack-operators15:09
*** racedo has quit IRC15:11
*** rcernin has quit IRC15:11
*** racedo has joined #openstack-operators15:11
*** saneax is now known as saneax_AFK15:13
mihalis68email done15:13
mihalis68anyone here see it?15:13
admin0email ?15:14
mihalis68http://lists.openstack.org/pipermail/openstack-operators/2016-June/010695.html15:14
*** julim has joined #openstack-operators15:14
mihalis68the email saying we want people to give feedback on venue choice via a poll15:14
jproulxmihalis68: now I've seen it :) looks good, thanks.15:15
mihalis68I'd like to know if that met people's expectations asap before I dive back into $DAYJOB15:15
mihalis68ah ok, Great, thanks @jproulx !15:15
*** pilgrimstack has joined #openstack-operators15:18
mihalis68I invite people to tweet about this poll15:18
mihalis68I just tweeted  a link to my email, but however people can get the word out is fine by me15:19
mihalis68and if someone from the foundation is on-line here if they can publicize it that would be good15:19
mihalis68I want the operators to hear about this!15:19
*** pilgrimstack has quit IRC15:24
jproulxmihalis68 stole lots of your text to post on LinkedIn  OpenStack group (as I recently discovered in some places people actually use that much to my surprise)15:30
mihalis68steal away!15:30
mihalis68and thanks!15:30
*** zeih has joined #openstack-operators15:32
*** zeih has quit IRC15:32
*** zeih has joined #openstack-operators15:32
*** liverpooler has quit IRC15:34
*** zeih has quit IRC15:38
*** permalac has joined #openstack-operators15:38
serverascodehow did ppl select both in the openstack ops venue poll? I can't seem to do that15:40
*** admin0 has quit IRC15:42
*** delattec has joined #openstack-operators15:44
*** zeih has joined #openstack-operators15:44
*** cdelatte has quit IRC15:47
mihalis68someone in touch with Matt Jarvis? I am hearing the poll forces either/or not both venues15:47
serverascodeyeah I was just trying to set both and can't seem to do it15:48
mihalis68I emailed matt.jarvis@datacentred.co.uk about this15:49
mihalis68email from the etherpad15:49
serverascodecool tahnks15:50
mihalis68I think he changed it to force either or after a couple of votes. I got an update about the poll because I registered with Doodle15:50
mihalis68I think voting for both is fine and should be allowed15:50
serverascodeI would think taht if you want to get numbers you have to allow both15:51
*** delattec has quit IRC15:51
*** dc_mattj has joined #openstack-operators15:51
mihalis68yes15:51
dc_mattjthe doodle poll for the ops mid cycle location should now allow multiple selection15:52
dc_mattjif anyone has been trying to select both15:52
*** delattec has joined #openstack-operators15:53
serverascodecool thanks dc_mattj :)15:53
mihalis68I voted for both. If it's not NYC I will see you in Seattle! :)15:56
*** matrohon has quit IRC16:04
*** dc_mattj has quit IRC16:07
*** zeih has quit IRC16:11
*** mriedem has joined #openstack-operators16:15
*** permalac has quit IRC16:16
*** Apoorva has joined #openstack-operators16:16
*** zeih has joined #openstack-operators16:17
*** Apoorva has quit IRC16:17
*** Apoorva has joined #openstack-operators16:18
*** mriedem1 has quit IRC16:18
*** dtrainor has joined #openstack-operators16:21
*** zeih has quit IRC16:22
*** gyee has joined #openstack-operators16:35
*** fragatina has joined #openstack-operators16:36
*** dminer has quit IRC16:36
*** fragatin_ has joined #openstack-operators16:36
*** fragatina has quit IRC16:40
*** tesseract has quit IRC16:43
jproulxHmmm I have a meeting in 15min where I'm supposed to talk to a user about 'allowed_address_pairs' in Neutron, but while I can still find docs about it in the API I can't find the command line I though existed ...  can anyone offer a pointer?16:49
*** simon-AS5591 has quit IRC17:07
*** ducttape_ has quit IRC17:17
mgagnejproulx: neutron port-update <port-uuid> --allowed-address-pairs type=dict list=true ip_address=10.13.0.0/2417:21
med_https://ask.openstack.org/en/question/84676/how-to-add-multiple-ip-inside-allowed-address-pairs/17:24
*** dminer has joined #openstack-operators17:24
*** ducttape_ has joined #openstack-operators17:28
*** simon-AS559 has joined #openstack-operators17:30
*** simon-AS5591 has joined #openstack-operators17:32
*** simon-AS559 has quit IRC17:34
*** VW has quit IRC17:35
*** mriedem1 has joined #openstack-operators17:38
*** mriedem has quit IRC17:40
*** electrofelix has quit IRC17:41
*** matt__ has joined #openstack-operators17:42
*** mriedem1 is now known as mriedem17:42
*** VW has joined #openstack-operators17:48
*** VW has quit IRC17:53
*** admin0 has joined #openstack-operators17:56
*** Rockyg has joined #openstack-operators17:58
*** VW has joined #openstack-operators18:02
*** matt__ has quit IRC18:05
*** dmk0202 has joined #openstack-operators18:09
*** admin0 has quit IRC18:10
*** admin0 has joined #openstack-operators18:10
*** uxdanielle has joined #openstack-operators18:13
*** priteau has joined #openstack-operators18:24
*** priteau has quit IRC18:25
*** priteau has joined #openstack-operators18:25
*** dmk0202 has quit IRC18:30
*** harlowja has quit IRC18:30
*** harlowja has joined #openstack-operators18:32
*** bzurawski has quit IRC18:41
*** VW_ has joined #openstack-operators18:51
*** VW has quit IRC18:54
*** VW_ has quit IRC18:56
*** dronshaw has joined #openstack-operators18:56
*** VW has joined #openstack-operators18:58
*** VW has quit IRC18:58
*** VW has joined #openstack-operators18:59
*** dmk0202 has joined #openstack-operators19:05
*** VW has quit IRC19:07
*** VW has joined #openstack-operators19:07
mrhillsmanhey peeps, should that doodle poll allow folks to select both venues?19:10
mrhillsmannvm, i see the previous discussion19:10
*** fragatin_ has quit IRC19:12
*** dc_mattj has joined #openstack-operators19:12
*** christx2 has joined #openstack-operators19:16
*** admin0 has quit IRC19:17
*** dc_mattj has quit IRC19:19
*** admin0 has joined #openstack-operators19:28
*** mriedem has quit IRC19:31
*** admin0 has quit IRC19:32
jproulxmed_ thanks for that pointer19:33
*** mriedem has joined #openstack-operators19:34
*** admin0 has joined #openstack-operators19:34
*** admin0 has quit IRC19:34
*** gyee has quit IRC19:36
*** mihalis68 has quit IRC19:41
*** delattec has quit IRC19:45
*** harlowja_ has joined #openstack-operators19:45
*** derekh has quit IRC19:46
*** harlowja has quit IRC19:49
*** cllewellyn_ has joined #openstack-operators19:53
*** pilgrimstack has joined #openstack-operators19:56
*** jsheeren has quit IRC19:57
*** dminer has quit IRC20:06
*** ducttape_ has quit IRC20:07
*** uxdanielle has quit IRC20:09
*** cdelatte has joined #openstack-operators20:12
*** pilgrimstack has quit IRC20:12
*** uxdanielle has joined #openstack-operators20:14
*** ducttape_ has joined #openstack-operators20:16
*** ducttape_ has quit IRC20:16
*** ducttape_ has joined #openstack-operators20:16
*** dmk0202 has quit IRC20:26
*** dmk0202 has joined #openstack-operators20:26
*** mriedem1 has joined #openstack-operators20:27
*** paramite has quit IRC20:28
*** cllewellyn_ has quit IRC20:29
*** mriedem has quit IRC20:30
*** mriedem1 is now known as mriedem20:32
*** dmk0202 has quit IRC20:33
*** VW has quit IRC20:41
klindgrenjproulx, we make heavy use of allowed-addresspairs20:42
klindgren(little late) but feel free to ask any questions20:42
klindgrenfrom a stupid simple standpoint all it does is add the requested ip's/mac's to the anti-spoofing rules that neutron creates on the port20:43
klindgrenso that traffic to/from those IP's can pass through the anti-spoofing rules for those specific ip's/mac addy's20:44
klindgrenassuming the use of SDN network with L3 gateways - it does nothing to impact/change that behavior20:44
klindgrenmost people use it to have an IP that they use pacemaker/keepalived/whatever to move between two vm's.20:45
*** saneax_AFK is now known as saneax20:46
jproulxklindgren yeah that's exactly the use case, I just needed to find the mechanics.20:48
jproulxneutron help port-update  makes no mention of the --allowed-address-pairs option so discovering the syntax was a small adventure20:50
klindgrenneutron port-update 90a65080-06d9-445a-bc15-3a1b2964835d --allowed-address-pairs type=dict list=true ip_address=10.224.78.2420:54
klindgrenits an extension that should be enabled by default - but you may have to specifically enable it20:54
klindgrento see if it worked do a port show and you should see the allowed_address_pair section contain something other than a {}20:56
*** VW has joined #openstack-operators20:57
*** darrenc is now known as darrenc_afk21:03
*** fragatina has joined #openstack-operators21:05
*** kstev1 has quit IRC21:10
*** julim has quit IRC21:12
*** piet has quit IRC21:14
*** uxdanielle has quit IRC21:36
*** kstev has joined #openstack-operators21:39
*** cdelatte has quit IRC21:39
*** VW has quit IRC21:46
*** darrenc_afk is now known as darrenc21:54
*** VW_ has joined #openstack-operators21:59
*** kstev has quit IRC22:08
*** ckonstanski has quit IRC22:09
*** dronshaw has quit IRC22:11
*** mriedem is now known as mriedem_away22:12
*** Rockyg has quit IRC22:12
*** jamesdenton has quit IRC22:12
*** christx2 has quit IRC22:15
*** simon-AS5591 has quit IRC22:16
*** priteau has quit IRC22:17
*** simon-AS559 has joined #openstack-operators22:22
*** openstack has joined #openstack-operators22:27
*** simon-AS559 has quit IRC22:27
*** rcernin has joined #openstack-operators22:28
*** catintheroof has quit IRC22:30
*** simon-AS559 has joined #openstack-operators22:32
jamespdjproulx: be aware of the fact that CIDRs from allowed_address_pairs can affect security group filtering in scary ways.22:34
jamespdi.e. If a port is in the default security group and has allowed address pair (SOME_MAC,10.0.0.0/8), then the security group rule "allow all traffic from default group" implies "allow all traffic from 10.0.0.0/8 too."22:36
*** simon-AS559 has quit IRC22:36
*** furlongm_ has joined #openstack-operators22:37
*** furlongm has quit IRC22:37
* jamespd tried to convince neutron devs that this behaviour dangerous and non-intuitive, but nobody seemed to care :/22:38
* jamespd weeps into his coffee.22:38
*** simon-AS559 has joined #openstack-operators22:42
*** ducttape_ has quit IRC22:43
*** simon-AS559 has quit IRC22:47
*** kstev has quit IRC22:56
*** simon-AS559 has joined #openstack-operators23:01
*** simon-AS559 has quit IRC23:06
*** jamesdenton has joined #openstack-operators23:12
*** jamesden_ has joined #openstack-operators23:14
*** asselin has joined #openstack-operators23:14
asselinhello, I'm looking for ansible work that finds unmounted attached cinder volumes, and formats/partitions/mounts them so they're ready to go. Any tips where to look?23:14
xavpaicethat sounds scary23:16
*** jamesdenton has quit IRC23:17
asselinxavpaice, why's that scary?23:17
xavpaicewhat if a volume isn't mounted but has a filesystem with data on it, or is a 'raw' device used for a database?23:18
xavpaicealso - we typically don't have access to our customer's VMs, and formatting volumes for them would introduce vast costs that would be difficult to recover23:19
asselinyeah, I'm taking this from a customer using a cloud point of view. They just use ansible to launch a vm, create a volume, attach it. Now they want to partiition/format/mount it (idempotently) so that they can install their services on it.23:22
xavpaicesounds like the sort of job for cloud-init23:27
serverascodeasselin: there is an os_volume module, but you would have to parse cinder output and then attach unattached voumes, then there is a filesystem moudle that will create an fs on that device23:28
jamespdasselin: depending on your hypervisor, you might get information from the metadata service about your block device mapping.23:28
serverascodebut I'm assuming you have a bunch of existing volumes not creating new ones on a new instance creation23:28
jamespdmost likely, it will be easier to just scan for /dev/vd? from inside the instance, or orchestrate from outside the instance using APIs as serverascode suggest.23:29
asselinin my case I'm creating new instances and volumes23:29
asselinI'm using ansible to orchestrate outside of VM.23:30
serverascodeyeah so you would create a new instance, create some kind of volume naming scheme, and if that volume doesn't exist create it and attach it and format it23:30
xavpaicethe tricky part is that when you attach it you need to know what the OS names it inside the guest, in order to format the right one23:31
xavpaiceif it's a new instance, cloudinit has tools for filesystem layout (but I can't explain it cos I don't know it well enough)23:32
jamespd^^ also, KVM does not guarantee predictable block device names23:33
serverascodeI haven't looked into if you can access by uuid or something for a while, but yeah if you have more than one volume that would be a problem23:34
xavpaiceI was just hunting for that, but haven't yet found a way in Trusty - and we don't know what the guest OS is in this case23:35
*** simon-AS559 has joined #openstack-operators23:35
*** simon-AS559 has quit IRC23:35
* xavpaice returns to breaking horizon in preprod :/23:35
*** piet_ has joined #openstack-operators23:39
*** rcernin has quit IRC23:40
*** simon-AS559 has joined #openstack-operators23:44
*** simon-AS559 has quit IRC23:48
*** VW_ has quit IRC23:49
*** PerfectChaos has joined #openstack-operators23:49

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