Tuesday, 2016-05-17

*** lhcheng_ has joined #openstack-operators00:17
*** lhcheng has quit IRC00:17
*** rbridgeman has quit IRC00:27
*** georgem1 has joined #openstack-operators00:31
*** saneax is now known as saneax_AFK00:32
*** lhcheng_ has quit IRC00:41
*** ducttape_ has joined #openstack-operators00:43
*** mriedem has joined #openstack-operators00:47
*** gfa is now known as gfa_00:48
*** gyee has quit IRC00:52
*** gfa_ is now known as gfa00:58
*** kstev1 has quit IRC01:02
*** lhcheng has joined #openstack-operators01:05
*** lhcheng_ has joined #openstack-operators01:08
*** lhcheng has quit IRC01:11
*** Apoorva_ has joined #openstack-operators01:27
*** Apoorva has quit IRC01:31
*** Apoorva_ has quit IRC01:32
jlkmrhillsman: thanks. Looks like it's internal to libvirt. We ran into the bug where some have hte same UUID, and live migration stopped working, and I'm assessing the damage of replacing all the UUIDs in production with new ones.01:47
*** rbridgeman has joined #openstack-operators01:50
*** kazuIchikawa has joined #openstack-operators02:03
*** kazuIchikawa has quit IRC02:08
*** ducttape_ has quit IRC02:08
*** kazuIchikawa has joined #openstack-operators02:13
*** mriedem has quit IRC02:28
mrhillsmanjlk you're welcome02:37
*** fawadkhaliq has joined #openstack-operators02:46
*** VW has joined #openstack-operators02:59
*** georgem1 has quit IRC02:59
*** fawadkhaliq has quit IRC03:09
*** armax has quit IRC03:20
*** ducttape_ has joined #openstack-operators03:24
sorrisonanyone here know about nova policy.json. There seem to be duplicates in the default policy.json03:41
sorrisoneg. os_compute_api:servers:update or compute:update which one do you use?03:42
logan-i was working on some custom policies wondering exactly the same thing yesterday sorrison. haven't had time to research it yet. if you find the answer id be interested to hear it03:49
sorrisonlooking in the code I see authorize(context, action='update') which doesn't give much away03:51
sorrisonlooking in master its still the same so looks like they haven't addressed it03:53
sorrisonwill go ask in the nova channel03:53
*** fawadkhaliq has joined #openstack-operators03:56
*** ducttape_ has quit IRC04:00
logan-https://review.openstack.org/#/c/150267/ "This patch rename the v2.1 api policy with 'os_compute_api' prefix,04:01
logan-that used to distinguish with v2 and ec2 API."04:01
logan-so same functions, different endpoints it sounds like04:02
logan-then all of the os_compute_api stuff was rolled back into the normal policy.json in https://review.openstack.org/#/c/169464/04:11
*** rstarmer has joined #openstack-operators04:13
*** VW has quit IRC04:23
*** delatte has quit IRC04:27
*** dabukalam has joined #openstack-operators04:40
*** tojuvone has quit IRC04:40
*** rstarmer has quit IRC04:47
*** rstarmer has joined #openstack-operators04:51
*** tojuvone has joined #openstack-operators04:52
*** fragatina has quit IRC04:56
*** rbridgeman_ has joined #openstack-operators05:02
*** rbridgeman has quit IRC05:06
*** maishsk_ has quit IRC05:07
*** rbridgeman_ has quit IRC05:35
*** simon-AS559 has joined #openstack-operators05:45
*** fragatina has joined #openstack-operators05:53
*** fragatina has quit IRC05:53
*** fragatina has joined #openstack-operators05:54
*** rcernin has joined #openstack-operators06:03
*** liverpooler has quit IRC06:04
*** liverpooler has joined #openstack-operators06:04
*** simon-AS559 has quit IRC06:06
*** rcernin has quit IRC06:18
*** rcernin has joined #openstack-operators06:21
*** simon-AS559 has joined #openstack-operators06:26
*** simon-AS5591 has joined #openstack-operators06:28
*** cdelatte has joined #openstack-operators06:30
*** simon-AS559 has quit IRC06:31
*** haukebruno has joined #openstack-operators06:32
*** eddima has joined #openstack-operators06:38
*** belmoreira has joined #openstack-operators06:53
*** mcunietti has joined #openstack-operators06:58
*** bvandenh has joined #openstack-operators07:00
*** zeih has joined #openstack-operators07:12
*** zeih has quit IRC07:17
*** fawadkhaliq has quit IRC07:22
*** fawadkhaliq has joined #openstack-operators07:23
*** fwdit has joined #openstack-operators07:23
*** saneax_AFK is now known as saneax07:24
*** mcunietti has quit IRC07:32
*** matrohon has joined #openstack-operators07:33
*** lhcheng_ has quit IRC07:33
*** zeih has joined #openstack-operators07:39
*** zeih has quit IRC07:44
*** liverpooler has quit IRC08:01
*** liverpooler has joined #openstack-operators08:01
*** pilgrimstack has joined #openstack-operators08:04
*** jeh has quit IRC08:07
*** jeh has joined #openstack-operators08:08
*** jeh has quit IRC08:08
*** jeh has joined #openstack-operators08:08
*** krobzaur has quit IRC08:08
*** dmk0202 has joined #openstack-operators08:12
*** bvandenh has quit IRC08:17
*** bvandenh has joined #openstack-operators08:18
*** derekh has joined #openstack-operators08:39
*** fawadkhaliq has quit IRC08:41
*** fawadkhaliq has joined #openstack-operators08:42
*** maishsk has joined #openstack-operators09:01
*** maishsk_ has joined #openstack-operators09:05
*** maishsk has quit IRC09:05
*** maishsk_ is now known as maishsk09:05
*** B_Smith has quit IRC09:08
*** electrofelix has joined #openstack-operators09:17
*** maishsk has quit IRC09:21
*** eddima has quit IRC09:25
*** eddima has joined #openstack-operators09:29
*** dmk0202 has quit IRC09:31
*** maishsk has joined #openstack-operators09:41
*** matrohon has quit IRC09:43
*** fragatina has quit IRC10:11
*** fragatina has joined #openstack-operators10:11
*** fragatina has quit IRC10:16
*** saneax is now known as saneax_AFK10:20
*** krobzaur has joined #openstack-operators10:20
*** zeih has joined #openstack-operators10:23
*** zeih has quit IRC10:27
*** arcimboldo has joined #openstack-operators10:31
*** maishsk has quit IRC10:38
*** dbecker has quit IRC10:42
*** eddima has quit IRC10:45
*** rstarmer has quit IRC10:47
*** zeih has joined #openstack-operators10:50
*** zeih has quit IRC10:54
*** zeih has joined #openstack-operators10:57
*** fawadkhaliq has quit IRC10:59
*** zeih has quit IRC11:02
*** eddima has joined #openstack-operators11:05
*** maishsk has joined #openstack-operators11:09
*** dbecker has joined #openstack-operators11:10
*** maishsk has quit IRC11:14
*** maishsk has joined #openstack-operators11:15
*** fawadkhaliq has joined #openstack-operators11:30
*** fawadkhaliq has quit IRC11:30
*** georgem1 has joined #openstack-operators11:38
*** georgem1 has quit IRC11:41
*** georgem1 has joined #openstack-operators11:42
*** vnogin has quit IRC11:47
*** maishsk has quit IRC11:49
*** maishsk has joined #openstack-operators11:51
*** dmk0202 has joined #openstack-operators11:52
*** simon-AS559 has joined #openstack-operators12:01
*** simon-AS5591 has quit IRC12:04
*** julim has joined #openstack-operators12:05
*** ducttape_ has joined #openstack-operators12:09
*** georgem1 has quit IRC12:19
*** ducttape_ has quit IRC12:25
*** mcunietti has joined #openstack-operators12:28
*** fwdit has quit IRC12:32
mrhillsman /window right12:35
*** fwdit has joined #openstack-operators12:37
*** simon-AS5591 has joined #openstack-operators12:41
*** simon-AS559 has quit IRC12:45
*** kstev has joined #openstack-operators12:49
*** georgem1 has joined #openstack-operators12:50
*** matrohon has joined #openstack-operators12:55
*** maishsk has quit IRC12:59
cloudnullO/13:02
cloudnullis the meeting in this room  ?13:03
cloudnullI'm not seeing a meeting entry here: http://eavesdrop.openstack.org/13:06
mrhillsmanmorning13:06
mrhillsmani think the meeting room changed...13:07
mcuniettiwhere is it now?13:07
mrhillsmani thought it was openstack-meeting-3 but could be wrong13:08
cloudnullIts also not listed on the meeting page, or I'm searching wrong.13:09
mrhillsmanhrm, yeah, it is gone :(13:11
mrhillsmanmy calendar says tomorrow 1-2pm CDT13:12
mrhillsmanopenstack-meeting-413:12
*** anteaya has joined #openstack-operators13:12
mrhillsmanall the operator meetings i have are on wednesdays13:13
mrhillsmanmonitoring/ops, operators13:13
mrhillsmanoh, and operators tag group, that is thurs13:13
serverascodemorning13:13
*** mriedem has joined #openstack-operators13:14
*** ducttape_ has joined #openstack-operators13:15
cloudnullI had thought I saw an ml post staying it was Tuesday starting may 1713:16
* cloudnull could be wrong it's early yet. 13:16
mcuniettiI got an email yesterday from Matt Jarvis and Tom Fifield talking about today at 14.00 UTC13:17
mcunietti"IRC freenode, in the #openstack-operators channel."13:17
cloudnullTuesday, 17 of May at 1400 UTC [1]13:18
cloudnullhttps://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information13:18
cloudnullThat's the one. Seems I'm early13:18
mrhillsmanah ok13:21
mrhillsmani need to change my calendar for sure then13:22
*** MarkBaker has joined #openstack-operators13:23
*** ducttape_ has quit IRC13:23
*** anteaya has quit IRC13:27
*** openstackgerrit has quit IRC13:32
*** openstackgerrit has joined #openstack-operators13:33
*** jproulx1 has joined #openstack-operators13:34
*** kstev has quit IRC13:35
*** fifieldt has joined #openstack-operators13:35
*** mcunietti has quit IRC13:40
*** Zucan has joined #openstack-operators13:43
*** emccormick has joined #openstack-operators13:47
*** hieulq_ has joined #openstack-operators13:47
*** kazuIchikawa has quit IRC13:48
*** ukinau has quit IRC13:49
* fifieldt looks up13:50
mrhillsmanhey there fifieldt13:51
*** MarkBaker has quit IRC13:51
fifieldtohai mrhillsman13:51
fifieldthow are you?13:51
mrhillsmangood sir and u?13:51
* jproulx1 lurks distractedly13:52
fifieldtAll is well here13:52
fifieldthat tip to the venerable jproulx113:52
* mrhillsman sees jproulx1 lurking and smiles...you sneaky devil you13:52
*** jproulx1 has quit IRC13:52
*** jproulx has joined #openstack-operators13:53
*** ukinau has joined #openstack-operators13:54
fifieldtook, we're about 5 minutes out or so from the first Ops Meetups Team meeting :)13:55
*** shintaro has joined #openstack-operators13:55
*** hvprash_ has joined #openstack-operators13:55
fifieldtwe have mrhillsman, jproulx, shintaro ... anyone else?13:55
mihalis68hello13:56
*** MeganR has joined #openstack-operators13:56
fifieldthi mihalis68 !13:56
shintarohi13:56
mihalis68good morning from NYC13:56
hieulq_hi13:56
mrhillsmancloudnull you still around13:56
*** dminer has joined #openstack-operators13:56
fifieldtwas also expecting a vw13:56
fifieldtmaybe even a jarvis13:56
fifieldtbut, they still have 4 minutes :)13:56
fifieldtif you need something to do for a few minutes, it might be worth listing yourself at https://etherpad.openstack.org/p/ops-meetups-team so people can put a name to the IRC handle :)13:57
fifieldtthis is a new group, after all13:57
*** MarkBaker has joined #openstack-operators13:57
*** lsell has joined #openstack-operators13:58
fifieldtyay lsell :D13:59
fifieldthieulq_: I think you were also planning to attend?13:59
lsellhello there13:59
emccormickgood morning everyone :)13:59
fifieldthi!13:59
hieulq_fifieldt, yo o/13:59
* dabukalam is here14:00
dabukalamo/14:00
fifieldtexcellent14:00
fifieldtwell, the time is upon us14:00
fifieldtit seems we have enough to kick it off14:00
fifieldtso here goes14:00
fifieldt#startmeeting Ops Meetups Team14:00
openstackMeeting started Tue May 17 14:00:59 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 first ever meeting of the generically-named "Ops Meetups Team".14:01
fifieldtNB: If you're new, or just idling in the channel, be sure to have read:14:01
fifieldt#link https://wiki.openstack.org/wiki/Ops_Meetups_Team14:01
fifieldtfor background.14:01
fifieldtThank you very much for coming - I'm excited about what we're going to achieve together!14:01
fifieldtToday's agenda starts with some fairly boring administrative stuff, and finishes with the excitement of working out how we're going to pull off the next meetup in short order.14:01
fifieldt# link https://etherpad.openstack.org/p/ops-meetups-team14:01
fifieldt#link https://etherpad.openstack.org/p/ops-meetups-team14:01
fifieldtI suspect that we'll probably get through the entire hour today, but the faster we get through agenda items 1 & 2, the more likely the following meetings will be shorter, so here goes.14:01
fifieldtFirstly: 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:01
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
*** ducttape_ has joined #openstack-operators14:02
fifieldtraise of hands for attendance?14:02
dabukalamo/14:02
hieulq_o/14:02
serverascodeo/14:02
shintaroo/14:02
Zucano/14:02
MeganRo/14:02
mihalis68o/14:02
emccormicko/14:02
jproulxo/14:02
lsello/14:02
keekzo/14:02
s3an20/14:03
fifieldtThat looks so cool :)14:03
fifieldtAnyway, it's 10PM here in Taiwan, I've got my fluffy slippers on, and that's working for me ... but does it work for you ...14:03
fifieldt#topic Meeting Time14:03
mihalis68WFM14:03
fifieldt==> Is this time OK for the ongoing meeting time?14:03
claytono/14:03
mrhillsmano/14:03
mrhillsmansorry14:03
mihalis68o/14:03
MeganRo/14:03
dabukalamfifieldt: seems reasonable, considering the timezone distribution14:03
emccormicko/14:03
jproulxo/14:03
keekzo/14:03
mihalis68we are just on coffee two in NYC14:04
shintaro1hr earlier would be better for me but works14:04
*** med_ has joined #openstack-operators14:04
*** med_ has quit IRC14:04
*** med_ has joined #openstack-operators14:04
serverascodetime works for me14:04
fifieldtindeed, it is 11pm in Japan, so quite late14:04
fifieldtdo we have folks from US west coast, though"?14:04
dabukalamand 7am on the west coast :)14:04
hieulq_fifieldt, it's 9PM in Vietnam, so it work for me14:04
fifieldtanyone from EU?14:05
dabukalamI'm in Austin temporarily for OSCON, so 9am here, but have been on the west coast recently14:05
* med_ is late14:05
med_I'm here now though14:05
* med_ had to restart his IRC proxy 14:05
fifieldtwelcome med_14:05
med_\014:05
med_\o14:05
fifieldtso, related question14:05
*** krobzaur has quit IRC14:05
fifieldtFrequency14:05
fifieldt==> is a frequency of every two weeks OK?14:05
*** cloudbert has joined #openstack-operators14:05
mihalis68o/14:06
emccormicko/14:06
Zucano/14:06
shintaroo/14:06
keekzo/14:06
med_wfm14:06
med_o/14:06
hieulq_o/14:06
claytono/14:06
fifieldtOK, so what I'm hearing is that we should meet at 1400 UTC, on Tuesdays, every two weeks. Roughly?14:06
emccormickperhaps an extra meeting or two as we approach mid-cycle / summits, but generally good14:06
fifieldtright, that is a good point14:06
*** VW has joined #openstack-operators14:07
fifieldtthere is a natural tendancy to need more closer to the events14:07
fifieldttendency*14:07
dabukalam+114:07
fifieldtso maybe we kick it off at every two weeks, because we have a lot to do to get this started14:07
jproulxemccormick +114:07
fifieldtthen expect a bit more closer to the ops meetups14:07
keekz+114:07
fifieldtand maybe after this first one we take it back a bit14:07
VWsounda resaonable14:08
fifieldtwould anyone like to comment further?14:08
*** shamail has joined #openstack-operators14:08
dabukalamwe can always review afterwards and decide to meet more often if we find that there's far more work to do and no time14:08
fifieldtIn the interests of time, and for those who couldn't make it tonight, why don't I email it as a proposal for the mailing list14:08
fifieldt?14:08
*** dc_mattj has joined #openstack-operators14:08
shamailo/14:08
dabukalamaha, a wild dc_mattj appears14:08
mihalis68o/14:08
dabukalamfifieldt: that works14:08
fifieldtok,14:08
dc_mattjhello, sorry got caught up in some actual cloud operation14:08
dabukalamdc_mattj: those damn clouds14:09
fifieldtnice one :)14:09
dc_mattjhave I missed much ?14:09
MarkBakero/14:09
fifieldt#action dc_mattj keep the cloud running14:09
fifieldtjust meeting time and frequency discussions14:09
shamailI'm just listening in since I have to drop in 20 min :(14:09
fifieldt#action fifieldt to email the mailing list to propose 1400 UTC Tuesdays, every two weeks, with note about changing frequency14:09
mihalis68rough consensus for every two weeks at this time for now, to be reviewed14:09
dc_mattj+114:09
shamail+114:09
emccormick+114:10
fifieldtok, so, moving on14:10
shintaro+114:10
fifieldt#topic Team aims, objectives and scope14:10
keekz+114:10
fifieldt==> Do you agree with what is on the wiki page as the scope for this team? https://wiki.openstack.org/wiki/Ops_Meetups_Team14:10
fifieldtdiscussion! go!14:10
med_... reading14:10
VW+114:10
med_+114:10
dc_mattj+114:10
mihalis68I agree with it14:10
shamailLooks good to me fifieldt14:10
cloudbert+114:11
keekz+1 lgtm14:11
dabukalamyup, +114:11
emccormick+114:11
MeganR+114:11
fifieldtdc_mattj: I added in a sentence based on the discussion we had in Austin to emphasize that the Foundation is here to help with logistics14:11
shintaro+114:11
Zucan+114:11
hieulq_+114:11
dc_mattjwe should probably add a bit about actually running the events though14:11
fifieldtthis is true14:11
dc_mattjthere will definitely be some input from folks on this team to that14:11
fifieldtthere's a whole blank section on "Approach" on that wiki page14:12
dc_mattjespecially for midcycles14:12
fifieldtat the moment there's some inherit knowledge that those who've been involved in ops meetup organisation before like dc_mattj , vw and myself have that probably needs to be written down14:12
mrhillsman+1 for scope14:12
VWagree fifieldt14:12
mrhillsmanand for your last comment14:12
VWis the thought that this group would do most of the MC'ing, etc during the event?14:13
fifieldtwhat would you think is best?14:13
dc_mattjI would have thought so, depending on who's comfortable doing that kind of stuff14:13
shamailThere is also the whole scheduling piece14:13
med_is VW van winkle?14:13
fifieldtyessir14:13
*** maishsk has joined #openstack-operators14:13
med_yep, I figured we were MC-ing14:13
*** mdorman has joined #openstack-operators14:14
med_ie, foundation for logistical support14:14
mihalis68IRC handles can be posted to the ether pad to help everyone know who everyone else is14:14
fifieldt#link https://etherpad.openstack.org/p/ops-meetups-team14:14
med_do we have a new ehterpad?14:14
VWyes, med_14:14
fifieldt^^ as per mihalis6814:14
med_kk14:14
fifieldtso the practicalities, to list them very roughly off the top of my head14:14
fifieldt1) schedule planning process14:14
fifieldt2) finding moderators for the slots14:15
fifieldt3) venue selection14:15
shamailWe should add a section for those willing to help at meetups but not be a part of the bi-weekly meeting14:15
med_4) venue date14:15
jproulxshamail +114:15
dc_mattjfood14:15
med_hotel/discount group rate/etc14:15
dc_mattjhotel discounts14:15
fifieldt4) MCing / intro sessions14:16
MarkBakeroptimum # of participants14:16
dc_mattjevening event possibly14:16
dc_mattj+1 MarkBaker14:16
mihalis68I went to the Philly one and that one was the one that overflowed the hosts facilities. Andrew Mitry said he could help based on that experience14:16
mihalis68was at comcast now at walmer14:16
mrhillsman+1 MarkBaker should probably be a minimum number?14:16
shintaro# of rooms in the venue14:16
mihalis68walmart14:16
fifieldtah, good point MarkBaker - there's also scope in this group for talking about stuff bigger than individual events14:16
dc_mattjit's not entirely down to just having a big venue either14:16
fifieldtsuch as, how to scale the events14:17
dc_mattjthere's an optimum number of people per session for effective communication14:17
med_yep, probably cap... I think we want to leverage everything we've already learned14:17
VWyeah, a good idea at the number of rooms we might want help14:17
med_a) charge a token fee14:17
med_b) have a token fee waiver as needed14:17
VWI know it's a big concern I have with trying to host one here again14:17
med_c) etc14:17
fifieldtso sorting out what that number is, making it into the schedule grid etc is within scope of this group14:17
VWwe have two big spaces, but not a lot of break out spots14:17
dabukalamfifieldt: and also, whether a few cycles down the line whether multiple distributed meetups makes sense rather than just the one14:17
dabukalamand how to manage multiple, and make sure nothing is missed14:17
fifieldtyup14:17
med_we held breakouts in kumbaya circles in the cafe a couple years ago at Rax.14:18
fifieldtdeciding that is in scope of this group, IMO14:18
VWI would agree14:18
MarkBakermrhillsman, min is probably 20 - 30, max 150 - 20014:18
dc_mattjdabukalam: we already went round that on the list a while back14:18
mihalis68I recall some support for a max of 150 at the austin talk three weeks ago14:18
med_so the Manchester (or wherever that UK place was) had 100-150 aiui and it was a "good" meeting as well14:18
dc_mattjI would say 150 is a good number14:18
dc_mattjkeeps the costs manageable14:18
shamaildc_mattj: +114:19
dc_mattjpeople can get to know each other, and the sessions are a good size for communication14:19
fifieldtworking out the split between the venue, foundation crew, and this group with regards to logistics - such as making the wifi work - will be something we need to look at14:19
med_I'm not sure the costs scale with the number (I guess it depends on what kind of participant sponsorship there is--free rooms vs conf hotel rooms)14:19
med_+1 dc_mattj14:19
fifieldt(FYI, there is some beginnings of content on venue selection at https://wiki.openstack.org/wiki/Operations/Meetups#Venue_Selection )14:19
dc_mattjmed_ in my experience bigger conference venues end up being £40+ per head per day for catering14:20
med_nod14:20
med_ah, food. Good point.14:20
*** matrohon has quit IRC14:20
dabukalamI suspect keeping it at 150 is going to be hard without creating serious barriers. The success of previous meetups and word of mouth will only mean more people will attend in future14:20
dc_mattjManchester came out at around half that14:20
dc_mattjdabukalam: it's also about keeping it focused properly14:20
med_so do we think we want ONE mid-cycle or regional ones?14:21
dc_mattjthere were a lot of people wanting to come to Manchester who weren't operators or dev14:21
lsellI was going to say 150 seems like an effective number, but I agree the community is growing and we had a lot of angry folks who couldn't attend last time14:21
mihalis68again at the austin talk I leaned about a silicon valley one that got too many people on the list14:21
MarkBakerit is easy to keep at 150 if you are as ruthless as dc_mattj14:21
emccormickPhilly was around 200 wasn't it? We're probably going to get larger turnouts in NE and northern CA14:21
dabukalamdc_mattj: right, so you end up with the same problem that the summits have begun to experience14:21
dabukalam(at a much larger scale)14:21
dc_mattjthis is an operators meeting14:21
dc_mattjincluding folks from dev14:22
VWas long as we are talking overall criteria for "where" - were do we stand on alternating geographies from the Summit14:22
dc_mattjVW I like that idea14:22
mrhillsmanwell we should definitely decide on a cap for the sake of baselining across the board14:22
VWe.g. - Europe/Asia before a North American summit and vice versa?14:22
keekzVW +1, i think it would help get more people involved that may not be able to make it to summit14:22
MarkBakeras a community we need to learn how to deal with popularity. It means considering multiple regional meets or accepting we will have big ons14:22
MarkBakerones14:22
VWof course, that is always governed somewhat by who's willing to host :)14:23
keekzMarkBaker: or perhaps a multiple smaller ones?14:23
dc_mattjpersonally my view is to try and keep it as one thing for as long as possible14:23
dc_mattjthere's a huge benefit from a wide constituency14:23
mihalis68philly appeared to be on the edge for what works in a single room14:23
shamail+114:23
mihalis68where it's full participation, not a "show" like the keynotes at the main summit14:24
fifieldtwe do do multiple rooms in the summit ...14:24
clayton+114:24
dc_mattjI think we potentially have a couple of offers on the table for venues right now14:24
VWyeah - it's tough - could argue either way, but IDEALLY, you have working groups, carrying items from summit to IRC meetings to midcycle -etc14:24
med_so pre Barcelona would be N.A.?14:24
VWso I see the risk in spreading it around to too many events14:24
med_I vote for Vancouver. :^)14:24
mihalis68yes civic hall nyc is 180 people main room and some breakout rooms14:24
fifieldtwe do indeed have some offers14:24
fifieldtbtw this discussion is looking excellent - I think in the past 12 minutes we've listed our year's worth of topics to attack and and solve :)14:24
dc_mattjMilan and NY were the two I know of14:24
fifieldtas we're still in the Team aims/objectives/scope agenda item14:25
fifieldtany objections to moving to the next one14:25
fifieldtwhich is indeed about the next upcoming meetup14:25
VWMilan as in Italy?14:25
fifieldt?14:25
shamailfifieldt: +114:25
mrhillsman^14:25
med_+114:25
dabukalamfifieldt: nope, go ahead14:25
dc_mattjVW: yes14:25
*** krobzaur has joined #openstack-operators14:25
fifieldt#topic Upcoming mid-cycle Ops meetup14:25
VWif so, I'd say we get a head start on the fall then ;)14:25
jproulxGeographically I like keeping it 'opposite' the summits for soem value of oppose14:25
fifieldtsorry for the procedural interruption, do go ahead :)14:25
dc_mattj+114:25
VWor winter actually14:25
mrhillsman+1 jproulx14:25
*** zeih has joined #openstack-operators14:26
fifieldtSo, I think we need something in ~August14:26
* med_ wonders who has a site in Milan.... may need to update my resume'14:26
fifieldtdoes that sound right to folks?14:26
dc_mattj+114:26
VWyes fifieldt14:26
med_+114:26
claytonyeap14:26
jproulx+114:26
Zucan+1 August14:26
VWat this point, it will be a mad dash to plan and we shouldn't go much later than that14:26
emccormickeThere's the Openstack East event in NYC in August14:26
VWor we are right up on summit14:26
shamail+1 to Aug14:26
emccormickneed to be aware of conflicts or consider colocating14:26
keekz+114:26
mrhillsmanOpenStack Days Texas Aug 25th14:26
fifieldtyup - vw is right on the sandwich factor14:26
fifieldtwe do need to be aware of those events too14:27
shamailCould we possibly target the same week as OpenStackDay East?  This would allow people to do two events if they are traveling14:27
fifieldtwhen is East, emccormick ?14:27
dc_mattjshamail: +114:27
med_I'd definitely want to NOT consider too strongly regional event conflicts. I'm fine with considering mid-cycle project events as potential conflicts.14:27
med_ie, nova mid-cyc, etc.14:27
fifieldt(NB: part of the date selection depends on venue availability)14:27
mrhillsmanmed_ +114:27
jproulxsince we were just in NA and headed to Europe I think ASia would be next, but having no offers and short time may be impractical this go round14:27
med_NECTAR?14:28
emccormickI brought up the NYC thing as a possible colocation thing more than an avoidance thing14:28
fifieldthaha, ask sorrison14:28
VWNorth America, med_14:28
med_emccormick, understood.14:28
mrhillsmani know we say opposite summit, but would it make more sense to line up with summit?14:28
emccormickit would be nice to hit both events at once14:28
dc_mattjjproulx: there were some potential issues raised in Austin about Asia with regards to language barriers14:28
VWno mrhillsman14:28
mrhillsmanconsidering $$14:28
shamailemccormick: +114:28
VWbecause there are those that can't travel some ways14:28
fifieldtso mihalis68 has some ideas that could be interesting14:28
claytonemccormick: +1 I like the idea of adjoining another event14:29
VWso it's a double whammy if both are regionally the same in a 6 month period14:29
mihalis68well we can get civic hall early in august for two consecutive days. 180 people main hall14:29
fifieldtshintaro may have some ideas on asia, too14:29
med_agreed, we had no representation in the Man meetup due to travel concerns. Asia would likely be the same. Not sure how we can better support the APAC folks but...14:29
mrhillsmani was thinking more like some days before summit14:29
mrhillsmanbut i gotcha14:29
*** shamail has quit IRC14:29
shintaroI need to find the venue in Tokyo14:30
med_mrhillsman, the summit itself is already an ops meetup14:30
jproulxmrhillsman we're alread at the summit though yes?14:30
med_and more so in the future.14:30
fifieldt(For those new, OpenStack summits happen every 6 months in a rotation that's approx US-EU-US-Asia)14:30
*** zeih has quit IRC14:30
claytonfifieldt: I think you suggested it at the summit, but I think it makes sense to follow something similar, with an offset14:30
fifieldtshintaro, I vaguely remember that tokyo day co-location was being looked into, but I understand that venue space in Tokyo is very difficult :)14:30
med_$$$$¥¥¥¥¥¥14:31
fifieldtwe've also had the folks from best buy get in touch14:31
jproulxAPAC definitely has challenges, I'm not opposed to NYC this time and catching up with the hoped for rotation later14:31
shintarofifieldt: yes Tokyo Days is in June and we do not have enough room for this event14:31
shintaroJuly14:31
fifieldtso, one of the key questions i have is14:31
fifieldtif we have multiple venue options14:31
fifieldthow do we choose?14:31
dc_mattjNY would work well for EU folks14:31
med_NYC or just NY State?14:32
emccormickOpenstack East is 8/23 - 8/24 (Tue., wed.). Could do Thu, Fri or have 1 day overlap with Mon., Tue.14:32
claytonfifieldt: you mean cheap and regional vs central and expensive?14:32
fifieldtnaw14:32
*** Zucan has quit IRC14:32
serverascode(side note: tokyo was less expensive for me than palo alto)14:32
claytonI didn't attend MAN because it was 2 days of travel time for a 2 day event, and that's coming from the US east coast14:32
fifieldtas in two or more awesome users, in the right geography we're looking at, come forward and offer to host14:32
dc_mattjfifieldt: has that happened so far ?14:32
fifieldthow do we choose one over the other in a fair, transparent way that doesn't frustrate people14:32
med_what about us so-so users?  :^)14:33
fifieldtdc_mattj: it's been one of the crappiest things I've had to do14:33
fifieldtwas deal with having to say no to people, based on behind-the-scenes dealings :)14:33
dc_mattjpromise them for the next cycle around ?14:33
med_fifieldt, Condorcet?14:33
claytonfifieldt: vote?14:33
dabukalamfifieldt: I think we need to get a better idea of where people are to enable us to make this devision fairly14:33
*** Zucan has joined #openstack-operators14:33
mihalis68+114:33
fifieldtI think I'14:33
fifieldtve14:33
med_decision or division?14:33
mrhillsmandecision :D14:33
dabukalam*decision14:33
fifieldtprobably promised "next time" to about 3-4 folks, and probably just forgot to reply to others14:33
dc_mattjlol14:34
VWhmm - that is tough14:34
fifieldtso I'm hoping this group can come up with a proposal :)14:34
claytonI think it might makes sense to come up with some sort of scoring  for each option as a filter pre-voting or to inform voting14:34
dc_mattjone other thing to consider in this context is vendor neutrality14:34
cloudbert+114:34
dabukalam+114:34
jproulxclayton +14:34
MarkBakerSo I would say that hosting venues hosted by users take preference over vendor venues14:34
claytonit's hard to vote in an informed way without information like "this venue is really small, but with a host that will cover all costs"14:35
med_vs. operator neutrality14:35
dc_mattjwe love sponsors, but don't want the event to be overshadowed by one or other vendor14:35
jproulxI liek the idea of having criteria we can score14:35
VWin theory - if we can get a couple of mid-cicyles ahead in planing, we might even be able to solicit member imput14:35
VWto the choices14:35
mihalis68Some clear desires have been expressed that I think have strong backing - rotating geography in opposition to main summit in terms of region14:35
dabukalamMarkBaker: dc_mattj: +114:35
*** markvoelker has joined #openstack-operators14:35
mihalis68is that fully agreed?14:35
*** markvoelker has quit IRC14:35
dc_mattj+1 if possible14:35
VW+114:35
keekzmihalis68: +114:35
*** dank_ has joined #openstack-operators14:35
dc_mattjI think we've also got to be pragmatic about what offers are on the table14:35
dc_mattjre hosting14:35
mihalis68I think this group could lock in a region and a time range and then ask for proposals14:35
*** kencjohnston has joined #openstack-operators14:36
med_seems like there are two topics/proposals on the table at once so I can't +1 until I know what we are voting on14:36
jproulxI'd say geo preference is 'Strongly desirable'14:36
fifieldt+1 mihalis6814:36
med_I anti-geo preference?14:36
med_+1 on that14:36
emccormick+1 for rotating geography14:36
fifieldtwhat do other folks think about an open call for proposals within a region>?14:36
emccormickopposite summits14:36
mihalis68@fifieldt you can restate proposals and have a vote14:36
*** markvoelker has joined #openstack-operators14:36
emccormick+1 for proposals in a region14:37
mihalis68(I am still learning IRC!)14:37
fifieldtmihalis68: I think the meetbot has vote functionality somewhere14:37
VWyes, fifieldt - I'm good with acall for proposals14:37
mrhillsman+1 for proposals in a region14:37
dabukalamfifieldt: while I think this should remain as open a process as possible, considering our worries about sizing and non-operators/devs attending and using up important space, shouldn't we avoid promoting this widely?14:37
fifieldtso, an addendum then14:38
cloudbertAgree with making regional decisions and then considering proposals14:38
med_eventbrite allows limited tickets.14:38
mihalis68ooh nice14:38
dabukalammed_: right, which doesn't help if we get 150 salespeople14:38
dabukalamand no operators can attend14:38
mrhillsmanis there a method/way to determine ops vs dev/non-ops?14:38
med_not afaik14:38
dabukalammrhillsman: I don't think discrimination is a good idea either14:38
mrhillsmanlol14:38
dabukalam:D14:38
ZucanAs much as that sounds interesting... I don't think we should go down the "determine worthiness" rabbit hole.14:38
dc_mattjnope14:38
dabukalamZucan: +114:38
dc_mattjworry about things when they happen14:38
mrhillsmanit's not discrimination or worthiness14:38
fifieldtok, just to close off the venue selection topic quickly14:39
mrhillsmanit's simply a what you do14:39
*** markvoelker has quit IRC14:39
mrhillsmanbut i digress14:39
fifieldt1. This group, as an organ of community feedback, determines approximate dates for the ops midcycles14:39
emccormickLast time you had a big thing at the top of the email saying basically "IF YOU'RE NOT AN OPERATOR, STAY HOME. THIS IS NOT FOR YOU". Did you end up with a bunch of sales people and noobs in Manchester?14:39
fifieldt2. This group, as an organ of community feedback, determines regions for the ops midcycles14:39
*** markvoelker has joined #openstack-operators14:39
ZucanMaybe that was why Manchester was half its normal size for a meetup? :)14:39
*** zioproto has joined #openstack-operators14:40
* med_ feels like an organ at times.... generally appendix.14:40
fifieldt3. Once 2 &3 are decided, an open call for proposals will be sent out for hosts matching the criteria14:40
med_2 & 3?14:40
med_1 & 2?14:40
mrhillsman^14:40
fifieldt1 &2 , sorry14:40
dc_mattjemccormick: no, we had none of either I don't think14:40
fifieldtDo you agree with the above 3 statements?14:40
mihalis68both 1&1 are o/ for me14:40
mihalis681&214:40
mihalis68darnit14:41
mrhillsmanfifieldt: +114:41
med_1,2,3 +114:41
dc_mattjnow I'm confused ;)14:41
mrhillsmanagreed14:41
mihalis68o/14:41
hieulq_+114:41
dc_mattj+1 on whatever numbers they were14:41
shintaro+114:41
cloudbertYes 1,2, 3 fifieldt and agree with VW that if we plan ahead makes the whole thing easier.14:41
emccormick+1 on the process14:41
MeganR+114:41
VWprocess looks good to me14:41
fifieldtare there any comments on that? perhaps an open call is a bad idea?14:41
keekz+114:41
dabukalam+114:41
med_fifieldt, there are now (apparently) and have certainly been offers pre-planning in the past14:42
emccormickand let's not make ourselves neurotic on the attendees. Just leave Tom's discouraging disclaimer on all announcements :)14:42
mrhillsmani don't think open call is a bad idea14:42
dabukalamfifieldt: maybe not a bad idea, but done carefully14:42
med_or rather, seemed to be pre-planning....14:42
dc_mattjif we've got offers, I don't think we need an open call14:42
med_so we just add those early offers into the mix?14:42
jproulxgot distracted, I think an open call is good so long as we have clear selection criteria with it so we get good submissions14:42
fifieldtwe could do either14:42
mrhillsmanjproulx: +114:42
med_jproulx, +114:42
fifieldtIMO we don't want to make the process to onerous14:42
fifieldtsince it's a huge effort to offer to host one of these things14:42
fifieldtand people have been very generous in the past14:42
med_so selection criteria/toolset/etc needs to be prioritized before open call is ever done.14:42
fifieldtdon't want to come across as arrogant/ungratful14:42
*** anteaya has joined #openstack-operators14:43
mrhillsmani think stuff as simple as like at least 150 seats, etc etc14:43
jproulxfor this round given existing offers and short time go with what we've got though14:43
VWvery true fifieldt14:43
dabukalamfifieldt: are our existing offers more users or vendors?14:43
mihalis68open call fine by me14:43
s3an2med_, +114:43
mihalis68and we put in an offer14:43
med_and that open call needs to be pretty SPECIFIC: Need venue that can handle N rooms, and M*N people14:43
dc_mattjdabukalam: users14:43
fifieldtthis time users dabukalam14:43
mrhillsmannothing anal but some basic minimums14:43
fifieldtprevious times have been vendors14:43
fifieldtso, I was going to propose:14:43
dank_We can supply you with space in 2 locations, theatres in each location and multiple breakout areas, plus we aren’t a vendor or noobs ;)14:44
med_when you say vendor, what do you mean? I thought of comcast as a user.14:44
jproulxfifieldt don't want to add hurdles just express needs.14:44
fifieldt4. Based on what comes back from the call, This Group decides what to do using $PROCESS_TO_BE_DETERMINED14:44
lselland datacentred14:44
fifieldtit could be that a vote etc is not needed sometimes14:44
med_#4 "the call" the call for hosting volunteers?14:44
fifieldtopen call for hosts, yes14:44
mihalis68user means an org whose primary interest IN OPENSTACK is using it14:44
med_okey-doke.14:44
*** xelwarto has joined #openstack-operators14:44
med_+1, #414:44
mihalis68not selling to people who use it14:44
mihalis68obviously we sell something14:45
fifieldtok, I need someone to take an action item to write up this philosophy about "users" being preferred as hosts over "vendors"14:45
fifieldtit's clear that there's consensus here, someone just needs to write it down well :)14:45
mihalis68I could try, but noob alert14:45
*** xelwarto has left #openstack-operators14:45
mihalis68happy to in fact14:45
fifieldtI like it :D14:45
*** zeih has joined #openstack-operators14:45
med_go for it into the etherpad please14:45
emccormickI'm still kinda lost on the vendor v. user distinction14:46
mrhillsmanin the fear of sounding dumb, why do we need to prefer one host over another?14:46
emccormickin my mind Comcast = user14:46
fifieldt#action mihalis68 to write up "users" vs "vendors" hosting philosophy14:46
mihalis68accepted14:46
med_mrhillsman, I don't think we want to be a captured audience for marketing14:46
emccormickRedhat / Suse / Mirantis = vendor14:46
emccormickyes?14:46
fifieldtI suspect this will be easiuer to get after we see it written down, mrhillsman14:46
shintarovendors sometimes have internal ops for their private clouds14:46
mrhillsmanagreed, but that can be clearly stated14:46
med_and Cisco, Juniper, Cumulus....14:46
emccormickie. If you'd have a booth in the marketplace, you're a vendor14:46
fifieldtalso true shintaro14:46
mrhillsmanok fifieldt14:46
emccormickif you're up for a superuser award, you're a user14:47
med_+1 emccormick14:47
fifieldtso, it was the HP public cloud team who kicked off the palo alto event14:47
*** steviee has joined #openstack-operators14:47
fifieldtok, we have 13 minuntes left14:47
keekzemccormick: i've seen some cases where both apply, though14:47
emccormickuser14:47
fifieldtit seems like those points were agreed, so I'm going to enter them into the minutes14:47
med_and I think they were very very non-vendor-y at that event14:47
fifieldtunless there are any objections?14:47
emccormickbecause HP public cloud was a public cloud not HP enterprise services14:47
med_s/they/HP14:47
emccormickthey are technically both so they are confusing :)14:47
fifieldt#agreed 1. This group, as an organ of community feedback, determines approximate dates for the ops midcycles14:48
mihalis68I ended up with an eye-watering black on purple color scheme on etherpad14:48
jlkoh, right, meeting.14:48
fifieldt#agreed 2. This group, as an organ of community feedback, determines regions for the ops midcycles14:48
mihalis68I might have to write this definition elsewhere and paste it14:48
fifieldt#agreed 3. Once 1 &2 are decided, an open call for proposals will be sent out for hosts matching the criteria14:48
fifieldtall good mihalis6814:48
fifieldt#agreed 4. Based on what comes back from the call, This Group decides what to do using $PROCESS_TO_BE_DETERMINED14:48
fifieldtOK, so thanks for standing by there14:48
* med_ confirms, embraces, and approves of this fifieldt message.14:49
fifieldtnow, if we're going to have one of these in August, we need to move fast14:49
* VW does as well14:49
dc_mattj+114:49
dc_mattjif we have a proposed venue we need to lock it down ASAP14:49
fifieldtany volunteers to write up a draft email about the upcoming meetup to go to the ops list14:49
*** MarkBaker has quit IRC14:49
fifieldtincluding the date: august14:49
fifieldtapproximate location: US?14:49
med_that's a good point, being RESPONSIVE to offers is important or offer--ees may hae to retract.14:49
med_or not be able to meet their offer if accepted too late.14:49
dc_mattjfifieldt: to solicit feedback on dates ?14:50
med_North America, I'd say either coast since we were just Mid-America14:50
*** zeih has quit IRC14:50
med_either coast suits one or another region14:50
emccormickN.A. and August14:50
fifieldtdc_mattj: I think we're more of less agreed on August, based on discussion before14:50
fifieldtafter august too close to the summit14:50
*** kstev has joined #openstack-operators14:50
emccormickCanada is OK too14:50
fifieldtpre august, too crazy to organise14:50
emccormickN.A. in general14:50
dc_mattjdo we want to lock in the venue first ?14:50
*** markvoelker has quit IRC14:51
med_NA, either coast. I'd recommend coastal for travel reasons (due to Austin being mid-america)14:51
fifieldtI think date is a prerequisite of locking in the venue, no, dc_mattj ?14:51
fifieldtapproximate date, anyway?14:51
dc_mattjor are we proposing to ask for venue proposals for this one ?14:51
VWagust in NA is good with me14:51
med_I think they are symbiotic: date and venue14:51
dc_mattjchicken and egg problem14:51
med_one can dictate the other (and either can be the one)14:51
fifieldtdc_mattj: I have two offers (that I remember) in my inbox at the moment14:51
emccormickChicago is pretty easy international also. Direct flights to all over. No need to limit to the coasts I don't think14:52
fifieldtso there needs to be some way of dealing with that14:52
dc_mattjdo you want to share who those offers are from for this group ?14:52
med_emccormick, hmmm. Tokyo/Beijing to Chicago. Okay. For that matter so is Denver... but not say, St Louis14:52
fifieldtBloomberg and BestBuy14:52
dc_mattjwhereabouts are BestBuy ?14:52
fifieldtI know shintaro is also very interested in getting something running in Asia, too14:52
med_+1 on the offers14:52
dank_@fifieldt BBY is flexible on location and dates14:52
fifieldtjust not sure about the timing14:52
dank_we have offices in Minnesota and Seattle14:52
med_dank_, cool.14:53
fifieldtthank you very much dank_ :)14:53
jlkSeattle would be lovely :D14:53
stevieeI'm with BBY; we have two locations Seattle (S. Lake Union) or Minneapolis14:53
emccormick+1 for Seattle :D14:53
cloudbert+1 Seatt;e14:53
* med_ has to drop but will review minutes.14:53
dabukalam-1 for seattle14:53
dank_Our seattle location is lovely, we have a 200 person theatre and multiple breakout rooms you can use.14:53
emccormickok we're done then. Meeting adjourned ;)14:53
*** markvoelker has joined #openstack-operators14:53
mrhillsmanlol14:53
dc_mattjlong way for us :(14:53
dabukalam(even though I'm currently on the west coast, I just think that will be unfair to EU operators)14:54
emccormicktrue. Tough or EU14:54
zioprotodc_mattj: I agree, NYC would be easier, less jet lag for the short meetup14:54
fifieldtanyway, so they're both amazing offers from really cool people14:54
VWagreed14:54
fifieldtwe have but 6 minutes left14:54
dc_mattjagreed14:54
mihalis68threw som words on ether pad about definition of user, but not happy with it, more later14:54
dabukalamfifieldt: yup, both Minneapolis and NY could work14:54
fifieldtand I think talking about those deserves more time than we have left14:54
fifieldtsince, it is a really big deal to step up and offer to host one of these things14:54
fifieldtso I want to give the most respect we possibly can :)14:55
mihalis68I guess I take an action to write one offer up, since people seem to like the idea of lock in region and time range and then look at offers14:55
zioprotoflying from EU for the meeting is okay, but try to keep it within 6 hours of Jet Lag from London please :)14:55
VWnext meeting then fifieldt?14:55
dc_mattjpostpone that decision to the next meeting ?14:55
emccormickDo you have specifics on the offers?14:55
mrhillsmanmonday-tuesday aligning with days east? or earlier in Aug?14:55
fifieldtsince this is all very new and exciting14:55
mrhillsmansounds like we have a venue already?14:55
emccormickwe could review and maybe come up with selection criteria so we can move quickly on it before next meeting or by next meeting14:55
fifieldtI think it might be nice to get those folks who have venues some time to process all of this14:55
fifieldtrather than demanding immediate details :)14:56
fifieldtunless I'm speaking out of turn ...14:56
VWno, sounds completely reasonable14:56
*** admin0 has joined #openstack-operators14:56
dank_+114:56
mrhillsmannext meeting enough time?14:56
dabukalamVW: +114:56
emccormickoh sorry, thought you had details already. Certainly give them time :)14:56
dc_mattjsome of this does come down to logistics though - if we cap at 200, with 2 tracks and breakouts, then it does define the number and size of rooms required14:56
fifieldtok, so what I'd like to see is some traffic on the mailing list14:57
mihalis68I believe our offer only has limited time slots available already, since August is "near" for venue booking in NYC14:57
fifieldtdoes anyone want to email out the summary, or shall I do that?14:57
mihalis68I will write something and fwd to Tom (since I'm new to all this). If all ok will fwd to mailing list14:57
fifieldtI'm happy to vett anything14:57
mihalis68I can have a go at that tom14:57
*** markvoelker has quit IRC14:57
fifieldtif you're sure mihalis68 ?14:58
*** markvoelker has joined #openstack-operators14:58
mihalis68not 100% but I think it's clear you want to devolve this14:58
mihalis68so yes I will14:58
fifieldtmuch appreciated14:58
fifieldtwith two minutes left, any other action items we didn't enter into the minutes?14:58
fifieldt#action fifieldt to arrange next meeting in two weeks14:58
fifieldtone minute ...14:59
mihalis68think that was a lot already!14:59
fifieldthuge amounts14:59
mrhillsmanbig ups to you fifieldt for getting this together14:59
dabukalamfifieldt: thanks for leading and driving this fifieldt14:59
mrhillsmanand whoever may have helped ;)14:59
mihalis68+114:59
emccormick+114:59
dabukalammrhillsman: +114:59
keekz+114:59
MeganR+114:59
fifieldtThank _you_ all14:59
steviee+114:59
fifieldtthis has been an amazing experience14:59
fifieldtI'm so happy we did this14:59
shintaro+114:59
dc_mattjdo we think this meeting might be better in one of the openstack-meeting channels in the future ?15:00
hieulq_+115:00
fifieldtI'll take that to the ML dc_mattj15:00
dc_mattjcool15:00
fifieldtfor now, it's time to say goodbye :)15:00
dabukalamcya15:00
fifieldt#endmeeting15:00
mihalis68TTFN15:00
openstackMeeting ended Tue May 17 15:00:28 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
dc_mattjlaters15:00
*** fwdit has quit IRC15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-17-14.00.html15:00
emccormickso long15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-17-14.00.txt15:00
*** dc_mattj has quit IRC15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-17-14.00.log.html15:00
*** shintaro has quit IRC15:00
*** cloudbert has left #openstack-operators15:01
fifieldtSee you 'around :)15:01
VWthanks for pulling us togehter fifieldt15:01
*** matrohon has joined #openstack-operators15:02
fifieldtso much passion about these events, I mean why wouldn't we give the people more control :)15:02
fifieldtno brainer15:02
VWha15:03
*** markvoelker has quit IRC15:04
jlkso much backlog15:05
*** zioproto has quit IRC15:05
*** arcimboldo has quit IRC15:06
VWour gift to you, jlk ;)15:06
*** steviee has quit IRC15:10
*** fragatina has joined #openstack-operators15:12
*** dtrainor has joined #openstack-operators15:14
*** fragatina has quit IRC15:16
*** hieulq_ has quit IRC15:20
*** belmoreira has quit IRC15:28
*** sticker has quit IRC15:32
*** dmk0202 has quit IRC15:33
*** gyee has joined #openstack-operators15:36
*** maishsk has quit IRC15:39
*** lhcheng has joined #openstack-operators15:50
*** admin0 has quit IRC15:51
*** rbridgeman has joined #openstack-operators15:56
*** fragatina has joined #openstack-operators15:57
*** armax has joined #openstack-operators15:57
*** haukebruno has quit IRC15:59
*** mdorman has quit IRC16:05
*** eddima has quit IRC16:05
*** hvprash_ has quit IRC16:06
*** fragatina has quit IRC16:07
*** mdorman has joined #openstack-operators16:07
*** fragatina has joined #openstack-operators16:07
*** maishsk has joined #openstack-operators16:17
*** matrohon has quit IRC16:18
*** saneax_AFK is now known as saneax16:23
*** Apoorva has joined #openstack-operators16:27
*** racedo has quit IRC16:29
mihalis68Sorry for spamming the mailing list. I am getting a bounce message every time from openstack-private16:30
mihalis68but I see it has gone through16:30
serverascodedo we put in a bug somewhere for that?16:37
serverascodethe openstack-private bounc16:37
*** derekh has quit IRC16:46
*** armax_ has joined #openstack-operators16:52
*** armax has quit IRC16:54
*** armax_ is now known as armax16:54
*** priteau has joined #openstack-operators16:58
*** piet has joined #openstack-operators17:00
*** gyee has quit IRC17:00
*** saneax is now known as saneax_AFK17:01
*** christx2 has joined #openstack-operators17:02
christx2hello17:02
christx2and afternoon from London17:02
*** anteaya has quit IRC17:04
*** gyee has joined #openstack-operators17:08
*** vinsh has quit IRC17:11
*** vinsh has joined #openstack-operators17:11
*** admin0 has joined #openstack-operators17:11
*** dmsimard has quit IRC17:13
*** lhcheng_ has joined #openstack-operators17:15
*** lhcheng_ has quit IRC17:15
*** lhcheng_ has joined #openstack-operators17:16
*** dmsimard has joined #openstack-operators17:16
*** lhcheng_ has quit IRC17:16
*** lhcheng_ has joined #openstack-operators17:17
*** lhcheng has quit IRC17:18
*** kelv has joined #openstack-operators17:21
*** maishsk has quit IRC17:22
*** electrofelix has quit IRC17:27
*** christx2 has quit IRC17:27
*** priteau has quit IRC17:27
*** simon-AS559 has joined #openstack-operators17:33
*** simon-AS5591 has quit IRC17:37
*** pilgrimstack has quit IRC17:37
*** simon-AS559 has quit IRC17:38
*** ducttape_ has quit IRC17:48
*** racedo has joined #openstack-operators17:52
*** piet has quit IRC17:52
*** ducttape_ has joined #openstack-operators17:55
*** piet has joined #openstack-operators17:55
*** christx2 has joined #openstack-operators17:59
*** mdorman has quit IRC18:01
*** pilgrimstack has joined #openstack-operators18:05
*** VW has quit IRC18:05
*** VW has joined #openstack-operators18:11
*** christx2 has quit IRC18:19
*** christx2 has joined #openstack-operators18:20
*** priteau has joined #openstack-operators18:22
*** rcernin has quit IRC18:31
*** saneax_AFK is now known as saneax18:38
*** rockyg has joined #openstack-operators18:38
*** saneax is now known as saneax_AFK18:41
*** MeganR has quit IRC18:44
*** racedo_ has joined #openstack-operators18:50
*** racedo has quit IRC18:52
*** racedo__ has joined #openstack-operators18:53
*** racedo_ has quit IRC18:54
*** mdorman has joined #openstack-operators19:12
*** fragatin_ has joined #openstack-operators19:13
*** fragatina has quit IRC19:15
*** fragatin_ has quit IRC19:18
*** piet has quit IRC19:22
*** jeh has quit IRC19:24
*** fragatina has joined #openstack-operators19:25
*** racedo__ has quit IRC19:33
*** gyee has quit IRC19:33
*** mriedem has quit IRC19:35
*** mriedem has joined #openstack-operators19:41
*** pilgrimstack has quit IRC19:42
*** racedo has joined #openstack-operators19:45
*** matrohon has joined #openstack-operators19:48
*** christx2 has quit IRC19:50
*** simon-AS559 has joined #openstack-operators19:50
*** rcernin has joined #openstack-operators19:58
*** piet has joined #openstack-operators20:00
*** matrohon has quit IRC20:02
*** fragatin_ has joined #openstack-operators20:04
*** fragatina has quit IRC20:08
*** mdorman has quit IRC20:14
*** racedo has quit IRC20:15
*** mdorman has joined #openstack-operators20:18
*** kstev has quit IRC20:19
*** georgem1 has quit IRC20:20
*** fragatin_ has quit IRC20:26
*** simon-AS559 has quit IRC20:26
*** fragatina has joined #openstack-operators20:27
*** fragatina has quit IRC20:28
*** fragatina has joined #openstack-operators20:29
*** dmk0202 has joined #openstack-operators20:29
*** rcernin has quit IRC20:41
*** flaviodsr has quit IRC20:52
*** christx2 has joined #openstack-operators20:57
*** julim has quit IRC21:01
*** kstev has joined #openstack-operators21:06
*** georgem1 has joined #openstack-operators21:06
*** georgem1 has quit IRC21:08
*** georgem11 has joined #openstack-operators21:08
*** dmk0202 has quit IRC21:10
*** mdorman has quit IRC21:13
*** mdorman has joined #openstack-operators21:18
*** fragatina has quit IRC21:24
*** fragatina has joined #openstack-operators21:24
*** fragatina has quit IRC21:29
*** georgem11 has quit IRC21:35
*** B_Smith has joined #openstack-operators21:49
mrhillsmanquite interesting link someone shared with me - https://software.intel.com/en-us/blogs/2016/05/06/doubling-the-performance-of-openstack-swift-with-no-code-changes21:49
*** maishsk has joined #openstack-operators21:54
*** mriedem has quit IRC21:55
*** fragatina has joined #openstack-operators21:56
*** fragatin_ has joined #openstack-operators21:59
*** fragatina has quit IRC22:01
*** fragatin_ has quit IRC22:01
*** fragatina has joined #openstack-operators22:02
*** dbecker has quit IRC22:04
*** mdorman has quit IRC22:04
*** markvoelker has joined #openstack-operators22:14
*** maishsk_ has joined #openstack-operators22:15
*** maishsk has quit IRC22:16
*** maishsk_ is now known as maishsk22:16
*** ducttape_ has quit IRC22:17
*** rockyg has quit IRC22:19
*** markvoelker has quit IRC22:21
*** markvoelker has joined #openstack-operators22:22
*** dansmith has quit IRC22:23
*** dansmith has joined #openstack-operators22:23
*** fragatin_ has joined #openstack-operators22:29
*** kstev has quit IRC22:32
*** fragatina has quit IRC22:32
*** kstev has joined #openstack-operators22:33
*** VW_ has joined #openstack-operators22:40
*** VW has quit IRC22:44
*** VW_ has quit IRC22:44
*** priteau has quit IRC22:44
*** fragatin_ has quit IRC22:47
*** fragatina has joined #openstack-operators22:48
*** kstev has quit IRC22:49
*** sticker has joined #openstack-operators22:49
*** kstev has joined #openstack-operators22:50
*** kstev has quit IRC22:50
*** kstev has joined #openstack-operators22:53
*** lhcheng has joined #openstack-operators23:00
*** lhcheng_ has quit IRC23:03
*** dminer has quit IRC23:03
*** markvoelker has quit IRC23:12
*** admin0 has quit IRC23:15
*** Zucan has quit IRC23:21
*** fragatina has quit IRC23:30
*** fragatina has joined #openstack-operators23:31
*** dansmith has quit IRC23:31
*** dansmith has joined #openstack-operators23:32
*** Zucan has joined #openstack-operators23:34
*** armax_ has joined #openstack-operators23:37
*** armax has quit IRC23:39
*** armax_ is now known as armax23:39

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