Tuesday, 2016-05-31

*** reed has quit IRC00:09
*** reed has joined #openstack-operators00:09
*** ducttape_ has joined #openstack-operators00:32
*** lhcheng has joined #openstack-operators00:53
*** lhcheng has quit IRC00:57
*** britthouser has joined #openstack-operators01:26
*** britthouser has quit IRC01:31
*** julim has quit IRC01:44
*** kazuIchikawa has joined #openstack-operators01:48
*** markvoelker has joined #openstack-operators01:51
*** tojuvone has quit IRC01:53
*** markvoelker has quit IRC01:55
*** julim has joined #openstack-operators02:00
*** zul has joined #openstack-operators02:01
*** zhangjn has quit IRC02:01
*** saneax is now known as saneax_AFK02:02
*** julim has quit IRC02:04
*** zhangjn has joined #openstack-operators02:06
*** hieulq has quit IRC02:38
*** fragatin_ has joined #openstack-operators02:41
*** fragatin_ has quit IRC02:44
*** fragatin_ has joined #openstack-operators02:45
*** hieulq has joined #openstack-operators02:45
*** fragatina has quit IRC02:45
*** fragatin_ has quit IRC02:49
*** fragatina has joined #openstack-operators02:57
*** fragatina has quit IRC03:02
*** fragatina has joined #openstack-operators03:48
*** rcernin has joined #openstack-operators03:49
*** markvoelker has joined #openstack-operators03:52
*** markvoelker has quit IRC03:56
*** maishsk has quit IRC04:20
*** rcernin has quit IRC04:52
*** chlong has quit IRC04:54
*** chlong has joined #openstack-operators05:12
*** markvoelker has joined #openstack-operators05:52
*** markvoelker has quit IRC05:57
*** bryan_att has quit IRC06:03
*** fragatina has quit IRC06:08
*** liverpooler has joined #openstack-operators06:16
*** liverpooler has quit IRC06:21
*** liverpooler has joined #openstack-operators06:21
*** simon-AS559 has joined #openstack-operators06:31
*** simon-AS5591 has joined #openstack-operators06:34
*** fwdit has joined #openstack-operators06:35
*** simon-AS559 has quit IRC06:36
*** paramite has joined #openstack-operators06:41
*** belmoreira has joined #openstack-operators06:46
*** saneax_AFK is now known as saneax06:57
*** tesseract has joined #openstack-operators06:57
*** rcernin has joined #openstack-operators07:02
*** markvoelker has joined #openstack-operators07:53
*** pilgrimstack has joined #openstack-operators07:54
*** markvoelker has quit IRC07:58
*** zeih has joined #openstack-operators08:01
*** saneax is now known as saneax_AFK08:04
*** zeih has quit IRC08:08
*** christx2 has joined #openstack-operators08:11
*** fragatina has joined #openstack-operators08:12
*** zeih has joined #openstack-operators08:15
*** Dyon has joined #openstack-operators08:16
*** christx2 has quit IRC08:19
*** Dyon has quit IRC08:22
*** Dyon has joined #openstack-operators08:23
*** dmk0202 has joined #openstack-operators08:26
*** simon-AS5591 has quit IRC08:28
*** pilgrimstack has quit IRC08:32
*** paramite is now known as paramite|afk08:40
*** zeih has quit IRC08:43
*** zeih has joined #openstack-operators08:46
*** simon-AS559 has joined #openstack-operators08:53
*** simon-AS5591 has joined #openstack-operators08:54
*** admin0 has joined #openstack-operators08:55
*** simon-AS559 has quit IRC08:57
*** electrofelix has joined #openstack-operators09:01
*** paramite|afk is now known as paramite09:01
*** paramite is now known as paramite|afk09:03
*** derekh has joined #openstack-operators09:03
*** permalac has quit IRC09:16
*** matrohon has joined #openstack-operators09:20
*** zeih has quit IRC09:23
*** zeih has joined #openstack-operators09:26
*** chlong has quit IRC09:29
*** selfsimilar has joined #openstack-operators09:41
*** selfsimilar has left #openstack-operators09:41
*** saneax_AFK is now known as saneax09:43
*** admin0 has quit IRC09:46
*** chlong has joined #openstack-operators09:46
*** markvoelker has joined #openstack-operators09:54
*** admin0 has joined #openstack-operators09:56
*** ducttape_ has quit IRC09:57
*** markvoelker has quit IRC09:58
*** paramite|afk is now known as paramite10:03
*** pcaruana has joined #openstack-operators10:11
*** simon-AS559 has joined #openstack-operators10:14
*** selfsimilar has joined #openstack-operators10:14
*** chlong has quit IRC10:15
*** simon-AS5591 has quit IRC10:17
*** simon-AS5591 has joined #openstack-operators10:21
*** simon-AS559 has quit IRC10:24
*** chlong has joined #openstack-operators10:27
*** selfsimilar has quit IRC10:30
*** kazuIchikawa has quit IRC10:30
*** selfsimilar has joined #openstack-operators10:45
*** simon-AS5591 has quit IRC10:45
*** permalac has joined #openstack-operators10:48
*** liverpooler has quit IRC10:48
*** admin0 has quit IRC10:51
*** admin0 has joined #openstack-operators10:52
*** ducttape_ has joined #openstack-operators10:57
*** selfsimilar has quit IRC11:00
*** liverpooler has joined #openstack-operators11:01
*** ducttape_ has quit IRC11:02
*** dmk0202 has quit IRC11:07
*** selfsimilar has joined #openstack-operators11:16
*** selfsimilar has quit IRC11:29
*** ducttape_ has joined #openstack-operators11:33
*** zhangjn has quit IRC11:36
*** zhangjn has joined #openstack-operators11:38
*** dmk0202 has joined #openstack-operators11:42
*** selfsimilar has joined #openstack-operators11:44
*** admin0 has quit IRC11:44
*** simon-AS559 has joined #openstack-operators11:47
*** simon-AS5591 has joined #openstack-operators11:49
*** simon-AS559 has quit IRC11:52
*** markvoelker has joined #openstack-operators11:55
*** markvoelker has quit IRC11:57
*** markvoelker has joined #openstack-operators11:57
*** ducttape_ has quit IRC11:58
*** selfsimilar has quit IRC11:59
*** admin0 has joined #openstack-operators12:05
*** vinsh has joined #openstack-operators12:08
*** selfsimilar has joined #openstack-operators12:13
*** flaviodsr has joined #openstack-operators12:20
*** paramite has quit IRC12:23
*** ducttape_ has joined #openstack-operators12:24
*** ducttape_ has quit IRC12:29
*** ducttape_ has joined #openstack-operators12:29
*** selfsimilar has quit IRC12:30
*** ducttape_ has quit IRC12:34
*** frickler has joined #openstack-operators12:40
*** selfsimilar has joined #openstack-operators12:46
*** ducttape_ has joined #openstack-operators12:47
*** julim has joined #openstack-operators12:53
*** fwdit_ has joined #openstack-operators12:57
*** fwdit has quit IRC12:58
*** selfsimilar has quit IRC13:00
*** fragatina has quit IRC13:09
*** fragatina has joined #openstack-operators13:10
*** fragatina has quit IRC13:11
*** fragatina has joined #openstack-operators13:15
*** selfsimilar has joined #openstack-operators13:16
*** simon-AS559 has joined #openstack-operators13:26
*** simon-AS5591 has quit IRC13:26
*** simon-AS5591 has joined #openstack-operators13:28
*** simon-AS559 has quit IRC13:31
*** selfsimilar has quit IRC13:31
*** admin0 has quit IRC13:34
*** dminer has joined #openstack-operators13:37
*** electrofelix has quit IRC13:39
*** selfsimilar has joined #openstack-operators13:46
*** admin0 has joined #openstack-operators13:49
*** fifieldt has joined #openstack-operators13:50
* fifieldt wanders in13:51
*** electrofelix has joined #openstack-operators13:51
gfa_fifieldt: r u the chair?13:56
fifieldtapparently :)13:56
*** shintaro has joined #openstack-operators13:59
fifieldtok14:00
*** selfsimilar has quit IRC14:00
shintarohi14:00
fifieldtanyone here for the ops meetups team meeting?14:00
ckonstanskisure14:01
s3an2o/14:01
claytonyeap14:01
shintaroo/14:01
serverascodeo/14:01
fifieldtimpressive, ok, let's try it14:01
bloatyfloato/14:01
fifieldt#startmeeting Ops Meetups Team14:01
openstackMeeting started Tue May 31 14:01:28 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 thank you for coming to the meeting. It's our second ever, and based on the amount of stuff we raised in the last one, there are likely many more to come.14:01
*** admin0 has quit IRC14:01
fifieldtDue to the timing, being the "first thing back" after a US holiday, I'm not sure how many people we'll get today. We may need to postpone :)14:01
fifieldtOur agenda can be found at:14:01
fifieldt#link https://etherpad.openstack.org/p/ops-meetups-team14:01
fifieldtPlease add your name there in the list of attendees so we know who's here :)14:01
fifieldt#topic Review of actions from previous meeting14:01
fifieldtFirst up, a quick administrative topic. We had 4 action items from last meeting.14:02
fifieldt1.    dc_mattj keep the cloud running14:02
fifieldt==> umm.14:02
fifieldt2.   fifieldt to email the mailing list to propose 1400 UTC Tuesdays, every two weeks, with note about changing frequency14:02
fifieldt==> was put on the ML at http://lists.openstack.org/pipermail/openstack-operators/2016-May/010481.html - no objections noted14:02
fifieldt3.    mihalis68 to write up "users" vs "vendors" hosting philosophy14:02
fifieldt==> Was put on the ML at http://lists.openstack.org/pipermail/openstack-operators/2016-May/010461.html14:02
fifieldt4.    fifieldt to arrange next meeting in two weeks14:02
fifieldt==> Well, we're here :)14:02
fifieldtany comments on the work from the past meeting?14:02
fifieldt... I guess not :)14:04
fifieldtwell, since they're basically on the ML, feel free to continue there14:04
fifieldt#topic Upcoming Meetup14:04
fifieldtNow, I'm not sure if we have folks here from Bloomberg or Bestbuy, our two prospective hosts...14:04
*** zeih has quit IRC14:05
s3an2don't see any on the etherpad14:05
fifieldtWe didn't make any progress toward an open call for proposals in the past week (for some reason it wasn't an action item), and it's getting late in the process. Since we have two excellent proposals, I'd suggest that we move forward to choose between these two for August without calling for additional proposals. That way we'll be able to properly spec out for next time.14:05
shintaroI couldn't make Tokyo this time, I'll try one after Barcelona.14:05
fifieldtno problem, Mizuno san14:06
* fifieldt looks forward to the chance14:06
*** Zucan has joined #openstack-operators14:06
fifieldtwhat do you all think about that idea? and if so, how should that be shaped?14:06
shintaroI guess the Region will be NA, then14:07
fifieldtbased on the summit in Barcelona and the previous ops meetup in EU, it seems like it is NA's turn14:07
fifieldtbut, what do you think?14:07
s3an2I think NA is a good idea - east coast works better for EU folks.14:08
gfa_sounds good? the good thing about both Bloomberg and Bestbuy is they won't try to sell you anything14:08
shintaroare the proposals on the etherpad?14:08
fifieldtBestbuy proposal was written to the ML recently14:09
fifieldtlemme see if I can find the link14:09
fifieldt#link http://lists.openstack.org/pipermail/openstack-operators/2016-May/010459.html14:10
fifieldtBloomberg was a NYC venue ("city hall") and was discused briefly in the previous meeting14:10
fifieldtbut, it seems noone's here to provide further details for eithe14:11
fifieldtso we might need to postpone this topic14:11
fifieldtor are there further comments about the next meetup?14:11
serverascodeit might be good to determine if east/west coast is important14:11
*** VW has joined #openstack-operators14:12
fifieldtthat might be the crux of the decision, in the end14:12
fifieldtlast East Coast was philly14:12
fifieldtlast West Coast was Palo Alto14:12
fifieldtso if we're doing east/west coast swapping each time, we'd be back to East14:12
fifieldtbut, what do you think serves best?14:12
bloatyfloatPerhaps figuring out the distribution of operators to try and balance it?14:13
shintaronot much difference from Asia in terms of travel, I guess ;)14:13
serverascodeit did seem like european operators preferred east coast in the last meeting, but I don't have a preference14:13
fifieldtI'm with shintaro, it's always a long way from Asia :D14:13
fifieldtok, well we should probably check the feasibility of the venues14:14
fifieldtwhich means getting further details about them14:14
serverascodeok14:14
bloatyfloatindeed, there's no need to commit to anything without enough info on both14:14
fifieldtwould anyone like to join me in the detail seeking emails?14:14
*** paramite has joined #openstack-operators14:14
*** admin0 has joined #openstack-operators14:14
fifieldtkeen to share 'how' this is done14:14
fifieldtrather than expecting effortz :)14:14
*** selfsimilar has joined #openstack-operators14:15
gfa_fifieldt: i would join you14:15
*** d0ugal has quit IRC14:15
gfa_if you "guide" a bit14:15
fifieldtok, gfa_, I'll set up an etherpad or something and we can work on the emails?14:15
gfa_ok14:15
fifieldt#action gfa_ and fifieldt to email Bloomberg and BestBuy to determine venue feasibility for the August ops meetup14:16
fifieldtok, so gfa_ and I will come back to either this meeting or the ML once we have further details14:16
fifieldtis that the only thing we need to do in relation to the next meetup?14:16
*** d0ugal has joined #openstack-operators14:16
fifieldt(at this time, that is)14:17
bloatyfloatWill you be sending this in CC to the operators list, or just to those involved?14:17
fifieldtprobably off-list, to avoid embarassment in case there are mismatches between the proposal and the aims of the event14:17
bloatyfloatThats perfectly understandable :)14:18
*** ducttape_ has quit IRC14:18
fifieldtalso, some of the comms will go to events people who aren't in the community14:18
fifieldtso might not be "allowed"14:18
fifieldtif that's OK14:18
*** dc_mattj has joined #openstack-operators14:18
fifieldtbut all comms will be summarised :)14:18
fifieldtif a few more people would like to be on CC, that'd be cool too14:19
dc_mattjafternoon14:19
fifieldthola14:19
fifieldtdc_mattj, VW, just to bring you up to speed14:19
fifieldtwe looked at the previous action items, all were OK14:19
fifieldtthen started talking about the next meetup14:19
fifieldtbut noone from the proposers are here right now14:19
fifieldtso gfa_ and I took an action item to followup to determine feasibility14:20
dc_mattjk14:20
fifieldtwill also take others who want to tag onto those emails asking them for details14:20
fifieldtbut I think that's about it for the discussion of the next meetup in August14:20
fifieldtunless someone wants to jump in?14:20
fifieldtok, I guess not, so let's move on the fun stuff!14:21
shintarolet me in the CC list14:21
fifieldtok shintaro :)14:21
fifieldtanyone else?14:21
fifieldt#topic Higher-level discussion14:22
fifieldtOK, so14:22
fifieldtnot sure if anyone saw any of the new stuff I wrote up on our wiki page14:22
fifieldtparticularly,14:22
fifieldt#link https://wiki.openstack.org/wiki/Ops_Meetups_Team#Approach14:22
*** piet has joined #openstack-operators14:22
fifieldtjust tried to summarise all of the topics we ran into last meeting14:22
fifieldtMy proposal is that we try and pick one(?) per meeting and dive deep and 'solve' it14:23
fifieldtbut open to any and all ideas14:23
fifieldtas long as we make concrete progress in planning the "future" for these events14:23
dc_mattjsounds good14:23
fifieldtso, where would you like to start?14:24
shintarofifield: can you discribe "e planning for individual instances of the event:"?14:24
fifieldtsure thing14:24
fifieldtso in that "approach" section, I divided into two sections14:24
fifieldtbasically I guess ythis group does two things14:25
fifieldt1) "organise" the actual meetups - just like we were in the previous discussion topic14:25
fifieldt2) work out "the future" for this event14:25
fifieldt planning for individual instances of the event == #114:25
*** ducttape_ has joined #openstack-operators14:26
fifieldtso just like we had discussions last meeting about the best month to hold it14:26
shintarofifield: got it!14:26
fifieldtand the discussion just then about NA, with the followup with the NA venyues, etc14:26
fifieldtcool14:26
dc_mattja lot of this is pretty interconnected - room sizes, venue requirements, number of participants for example14:26
fifieldtthis is true14:26
*** ckonstanski has quit IRC14:26
fifieldtso, how about perhaps, what's most important?14:27
dc_mattjnumber of participants drives a bunch of other stuff14:27
VWit does14:27
fifieldtok, let's start there!14:27
fifieldtsomeone want to start with their thinking?14:27
dc_mattj15014:28
dc_mattjto 20014:28
shintaroyes14:28
serverascodeyup14:28
gfa_+114:28
gfa_we could grow if many ppl remains outside, or shrink14:29
s3an2seem to match the Seattle BestBuy location14:29
fifieldtfor the record, someone want to write out the "why"?14:29
dc_mattjon it14:30
*** selfsimilar has quit IRC14:30
dc_mattjor trying to at least ;)14:30
* fifieldt waits for the brilliance14:31
dc_mattjnope, can't log in14:31
VWok - thanks dc_mattj.  I'm still trying to reconcile the idea that we cap it if we found a venue that held say 400 or 50014:31
gfa_we could require venues for at least 150 - 200,if we got a bigger one raise the cap14:32
fifieldtso what does n event with 400 or 500 look like compared to a 150-200 event?14:32
gfa_then raise the cap14:32
mrhillsmani thought we decided on a cap last meeting?14:32
serverascodeall I can add is that it felt like palo alto had too many people14:33
fifieldtwhat are the differences between a capped 150 event and a 'large' 500 evnet?14:33
fifieldtpersonally, I agree with serverascode14:34
dc_mattjmore impersonal14:34
VWfair enough14:34
dc_mattjless opportunity to get to know people14:34
* VW backs off14:34
dc_mattjbigger org team needed to manage the event etc14:34
dc_mattj;)14:34
fifieldtI think one of the practical things is the number of people who can realistically join a discussion in a single room14:34
dc_mattjis it just me or is there something wrong with openID login to the wiki14:34
*** simon-AS5591 has quit IRC14:34
serverascodealso if 500 was possible then it could be split into separate geographic events14:35
dc_mattjfifieldt, +114:35
fifieldtso, is it important to have a "common14:35
fifieldt"14:35
fifieldtdiscussion14:35
fifieldtas we've had to date?14:35
shintarovenue selection would be hard for 500 with say 10 parallel session?14:35
fifieldta fair point14:35
dc_mattjas opposed to more one to many talks ?14:35
fifieldtyeah, I think a key part of this event is active participation14:36
fifieldtdo you agree?14:36
VWyes14:36
dc_mattjyes14:36
shintaroo/14:36
mrhillsmanyes14:36
s3an2yes14:36
VWbut I don't want to focus on the general sessions at the expense of times for teams/working groups14:36
fifieldtright, the different session types is a good point14:37
VWI think we frame a lot of our decsions on the flow of the general sessions - or at least we have in the 1.5 meetings so far :)14:37
fifieldtvery good point14:37
fifieldtso, what then about sizes for the teams/working groups?14:37
fifieldtLDT is hitting 60 at the meetups and 100 at the summit14:37
fifieldtScientificWG was about 40 at manchester14:38
fifieldtmaybe 60 in Austin14:38
fifieldtput those side by side and you hit your cap?14:38
fifieldtdc_mattj: maybe you can write your 'why' on the etherpad?14:39
serverascodethe ldt I went to in tokyo was more like 1514:39
*** ducttape_ has quit IRC14:40
fifieldttokyo and vancouver were both in general smaller, yes14:40
fifieldtanother interesting point14:40
fifieldttaking the 500 example14:40
fifieldtis what would happen during the working group/team time14:40
fifieldtwe don't have that many working groups14:41
fifieldtat least not enough to split to have a nice "50 in each" room or so14:41
*** dtrainor has joined #openstack-operators14:41
VWThat's fair14:41
fifieldtwhich means we end up with large numbers of people who may not necessarily be actively participating in the WGs14:41
VW50 is getting to the size that it's hard to do work in the session14:41
VWand we did for sure in Palo Alto14:42
fifieldtone of the arguments for the larger size event is that it's better because we can get more feedback from a wider gorup of people14:42
fifieldtconsidering one of our aims is feedback that's useful for development14:42
fifieldthowever that's countered by the people-in-one-room discussion problem14:42
fifieldtanother counter argument is more widely disributed meetups more often gets the same14:43
fifieldtso, it seems we're leaning toward a 150-200pax event14:43
fifieldtdc_mattj: cam i acton u to write the why?14:43
*** fwdit_ has quit IRC14:43
dc_mattjyup, putting it on the ether pad right now14:44
claytonpalo alto also had no fee required.  part of the problem in the fishbowl sessions was actually that people were too spread out in a room that was bigger than needed.  at least on the second day14:44
fifieldt#action dc_mattj to write the justificaiton for smaller meetups and communication on the M14:44
VWdc_mattj: ping me when done (even if dm after meeting), happy to provide extra eyes/tweaks14:44
fifieldt#action VW to help dc_mattj14:45
fifieldtcool14:45
*** selfsimilar has joined #openstack-operators14:45
fifieldtso, with that approximate number written up and justified14:45
dc_mattjdoes that mean communication on the ML ?14:45
fifieldtI think we'll be in a good position to move forward with that as a basis14:45
fifieldtdc_mattj: when you're happy with it14:45
dc_mattjcool14:45
fifieldtwe need wide consensus on this :)14:45
fifieldtsince it's pretty critical14:45
fifieldtbut, with that in mind, we can start looking at things like14:46
fifieldtif we have a number cap in mind, how do we execute it14:46
fifieldt?14:46
dc_mattjin Manchester, if we had more tickets they would have ended up with vendors mainly14:46
fifieldtbe good to do some aalysis there maybe14:47
fifieldti remember some irate people14:47
dc_mattjme too ;)14:47
fifieldtdo you still hve the list?14:47
fifieldtwaitlist14:47
dc_mattjyes, although in the end the waitlist didn't get massive as everyone knew we had a hard cap14:48
dc_mattjthink I've still got it all somewhere14:48
fifieldtin general, would you do it the same way again?14:48
dc_mattjwould add larger break out rooms14:49
fifieldtand the waitlist/rego mgmt?14:49
dc_mattjeventbrite works well14:49
fifieldtmaybe add something extra for the r the waitlist?14:50
fifieldtto avoid mass of emails?14:50
dc_mattjtricky bit is people trying to short circuit the process by going up the ladder14:50
dc_mattjmaybe14:50
fifieldtright14:50
fifieldtadd in some process there14:50
fifieldtanyway, we have just 10 minutes left in this meeting14:50
fifieldtgot a solid action item so far14:50
fifieldtjust want to ensure there wasn't someone who had a burning issue they wanted to raise14:51
fifieldtdoes anyone have concerns, or amazing ideas?14:51
serverascodeby the waitlist did you mean that the ppl who didn't get to attend the last meeting might have first dibs on the next?14:52
fifieldtwhat do people think about that?14:52
*** wasmum has quit IRC14:52
fifieldtworth a shot?14:52
serverascodeI think it would help if people were upset that they couldn't attend due to the cap14:53
VWI think I'm ok with it - provided we limit the time they have first shot14:53
s3an2VW, I agree14:53
fifieldtwhat's a reasonable time limit?14:53
fifieldt1 day after reg opens?14:53
fifieldt3 days?14:54
shintaro24hrs was an advantage for sponsorship in the summit.14:54
shintaroso maybe 1day14:54
s3an2I think 1 day is fair14:55
VWcan we create a certain number of tickets that require a code, send a code to those folks and have it expire like a week later?14:55
VWor one day14:55
fifieldteventbrite has that feature, I believe14:55
fifieldtWould someone like to write up a process for managing the waitlist?14:55
fifieldtdoesn't have to be anything fancy :)14:56
*** cdelatte has joined #openstack-operators14:56
*** klindgren has joined #openstack-operators14:56
mrhillsmani can14:56
fifieldtcheers mrhillsman !14:56
fifieldt#action mrhillsman to write up a proces for managing the waitlist and send to ML for discussion14:57
fifieldtfirst pass is all that's needed :)14:57
fifieldtwe can refine on ML14:57
mrhillsmansure thing14:57
fifieldtok, with 3 minutes left in our meeting, how are we feeling?14:57
fifieldtI'm sorry we didn't make a lot of progess on August today14:57
dc_mattjone other small point which came up in the context of the User Committee Charter14:58
dc_mattjwas naming14:58
fifieldtright14:58
dc_mattjmeetups vs mid cycles14:58
fifieldtthoughts?14:58
fifieldt(2 minute warning)14:58
dc_mattjI think I'm on the side of midcycle14:58
VWOps mid-cycles14:58
dc_mattjas it separates this from user group meetups14:59
s3an2dc_mattj, +114:59
VWand at the summits Ops sessions14:59
VWor something to mirror the design session naming14:59
shintaro+1 for midcycle14:59
dc_mattjVW, +114:59
fifieldtlol, someone want to setyup a surveymonkey?14:59
mrhillsmanmidcycle14:59
VWfor the whole ml, fifieldt?14:59
fifieldtI guess so, it's a bit of fun :)15:00
fifieldtanyway, we're at time15:00
fifieldtso I won't force that as an action item :)15:00
*** selfsimilar has quit IRC15:00
fifieldtbut if you do want to jump on the ML with that iidea, feel welcome!15:00
fifieldtOK, our hour went fast15:00
fifieldtlet's do this again in 2 weeks15:00
fifieldtand pay attention to the ML in the interim15:00
fifieldtfeel free to wrangle the next meeting agenda for your interes t:)15:01
shintarofifield: thank you15:01
fifieldtand thank you so much for coming!!15:01
fifieldt#endmeeting15:01
openstackMeeting ended Tue May 31 15:01:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.log.html15:01
dc_mattjbye all15:01
gfa_fifieldt: tnx15:01
*** shintaro has quit IRC15:01
mrhillsmanl8rs15:01
VWthanks, all!15:01
*** regXboi has joined #openstack-operators15:04
*** bryan_att has joined #openstack-operators15:05
*** armax has joined #openstack-operators15:05
*** rcernin has quit IRC15:07
*** ducttape_ has joined #openstack-operators15:09
dmsimardHas anyone noticed performance issues specific to nova API commands in Mitaka ? I filed this: https://bugs.launchpad.net/nova/+bug/158240915:16
openstackLaunchpad bug 1582409 in OpenStack Compute (nova) "nova-api performance issues on "openstack server list"" [Undecided,Invalid]15:16
dmsimardI'd like to hunt the problem down further but curious if anyone else has noticed anything.15:16
*** selfsimilar has joined #openstack-operators15:16
*** simon-AS559 has joined #openstack-operators15:20
*** ckonstanski has joined #openstack-operators15:21
*** selfsimilar has left #openstack-operators15:22
*** belmoreira has quit IRC15:22
*** simon-AS5591 has joined #openstack-operators15:23
*** simon-AS559 has quit IRC15:24
*** saneax is now known as saneax_AFK15:28
*** openstackgerrit has quit IRC15:33
*** dc_mattj has quit IRC15:33
*** openstackgerrit has joined #openstack-operators15:33
*** saneax_AFK is now known as saneax15:36
*** wasmum has joined #openstack-operators15:37
*** matrohon_ has joined #openstack-operators15:38
*** Apoorva has joined #openstack-operators15:39
*** dmk0202 has quit IRC15:42
*** tesseract has quit IRC15:54
*** kstev has joined #openstack-operators15:58
*** pcaruana has quit IRC15:59
*** gyee has joined #openstack-operators16:00
*** simon-AS5591 has quit IRC16:01
*** lhcheng has joined #openstack-operators16:07
*** Dyon has quit IRC16:08
*** fragatina has quit IRC16:10
*** admin0 has quit IRC16:12
*** gfa_ is now known as gfa_away16:14
*** dalees has quit IRC16:15
*** matrohon has quit IRC16:17
*** armax_ has joined #openstack-operators16:27
*** armax has quit IRC16:27
*** armax_ is now known as armax16:27
*** derekh has quit IRC16:34
*** vinsh has quit IRC16:38
*** vinsh has joined #openstack-operators16:39
med_dmsimard, has your deployment scaled at the same time as your move to Mitaka? That's an issue we noticed that kind of made us think it was a Liberty problem when it was really just our cloud growing.16:40
*** ckonstanski has quit IRC16:41
*** ckonstanski has joined #openstack-operators16:42
*** permalac has quit IRC16:42
*** vinsh_ has joined #openstack-operators16:43
dmsimardmed_: This is reproducible on an empty (brand new) very simple deployment driven with openstack puppet modules.16:43
med_kk16:43
dmsimardI haven't tried reproducing the issue on liberty, though16:44
*** vinsh has quit IRC16:44
*** rcernin has joined #openstack-operators17:01
*** mdorman has joined #openstack-operators17:06
*** armax has quit IRC17:11
*** armax has joined #openstack-operators17:12
*** dalees has joined #openstack-operators17:27
*** bryan_att has quit IRC17:33
*** wasmum has quit IRC17:41
*** fragatina has joined #openstack-operators18:03
*** electrofelix has quit IRC18:12
*** wasmum has joined #openstack-operators18:17
*** admin0 has joined #openstack-operators18:35
*** wasmum has quit IRC18:36
*** simon-AS559 has joined #openstack-operators18:38
*** saneax is now known as saneax_AFK18:43
*** simon-AS559 has quit IRC18:48
*** fragatina has quit IRC18:51
*** fragatina has joined #openstack-operators18:52
*** simon-AS559 has joined #openstack-operators18:52
*** simon-AS559 has quit IRC18:57
*** jrniemijr has joined #openstack-operators18:58
*** simon-AS559 has joined #openstack-operators19:06
*** simon-AS5591 has joined #openstack-operators19:33
*** simon-AS559 has quit IRC19:33
*** gyee has quit IRC19:35
*** wasmum has joined #openstack-operators19:40
*** simon-AS559 has joined #openstack-operators19:47
*** piet has quit IRC19:47
*** piet has joined #openstack-operators19:48
*** simon-AS5591 has quit IRC19:49
*** rockyg has joined #openstack-operators19:49
*** simon-AS559 has quit IRC19:52
*** Apoorva has quit IRC19:59
*** simon-AS559 has joined #openstack-operators20:00
*** simon-AS559 has quit IRC20:04
*** simon-AS559 has joined #openstack-operators20:05
*** dmk0202 has joined #openstack-operators20:05
*** Apoorva has joined #openstack-operators20:06
*** simon-AS559 has quit IRC20:09
*** admin0 has quit IRC20:11
*** simon-AS559 has joined #openstack-operators20:11
*** jrniemijr has quit IRC20:16
*** admin0 has joined #openstack-operators20:22
*** dminer has quit IRC20:26
*** dmk0202 has quit IRC20:28
*** VW_ has joined #openstack-operators20:29
*** VW has quit IRC20:33
*** fragatina has quit IRC20:34
*** VW_ has quit IRC20:34
*** Zucan has quit IRC20:37
*** VW has joined #openstack-operators20:37
*** VW has quit IRC20:37
*** VW has joined #openstack-operators20:37
*** julim has quit IRC20:38
*** dmk0202 has joined #openstack-operators20:44
*** Zucan has joined #openstack-operators20:50
*** Apoorva has quit IRC20:51
*** Apoorva has joined #openstack-operators20:51
*** bryan_att has joined #openstack-operators20:54
*** paramite has quit IRC21:02
*** simon-AS559 has quit IRC21:05
*** ducttape_ has quit IRC21:25
*** simon-AS559 has joined #openstack-operators21:26
*** simon-AS5591 has joined #openstack-operators21:28
*** simon-AS559 has quit IRC21:31
*** ducttape_ has joined #openstack-operators21:31
*** piet has quit IRC21:33
*** piet has joined #openstack-operators21:34
*** dmk0202 has quit IRC21:38
*** kstev has quit IRC21:43
*** kstev has joined #openstack-operators21:46
*** piet has quit IRC21:47
*** kstev has quit IRC21:47
*** admin0 has quit IRC21:48
*** fragatina has joined #openstack-operators21:52
*** rockyg has quit IRC22:02
*** turvey has quit IRC22:14
*** turvey has joined #openstack-operators22:15
*** VW_ has joined #openstack-operators22:15
*** VW__ has joined #openstack-operators22:18
*** VW has quit IRC22:19
*** VW_ has quit IRC22:20
*** VW__ has quit IRC22:22
*** regXboi has quit IRC22:29
*** simon-AS5591 has quit IRC22:34
*** ducttape_ has quit IRC22:36
*** ducttape_ has joined #openstack-operators22:36
*** turvey has quit IRC22:39
*** ducttape_ has quit IRC22:41
*** turvey has joined #openstack-operators22:43
*** mdorman has quit IRC22:44
*** turvey is now known as mwturvey22:44
*** ckonstanski has quit IRC22:45
*** mwturvey is now known as turvey22:45
*** turvey is now known as mwturvey22:45
*** mwturvey is now known as fragglerock2122:45
*** wasmum has quit IRC22:46
*** fragglerock21 has quit IRC22:47
*** mwturvey__ has joined #openstack-operators22:48
*** mwturvey__ has quit IRC22:48
*** julim has joined #openstack-operators22:56
*** julim has quit IRC22:59
*** darrenc is now known as darrenc_afk23:03
*** piet has joined #openstack-operators23:11
*** armax has quit IRC23:13
*** ckonstanski has joined #openstack-operators23:13
*** armax has joined #openstack-operators23:14
*** flaviodsr has quit IRC23:21
*** darrenc_afk is now known as darrenc23:23
*** mwturvey__ has joined #openstack-operators23:24
*** piet has quit IRC23:27
*** ducttape_ has joined #openstack-operators23:41
*** ggillies_ has quit IRC23:42
*** bryan_att has quit IRC23:43
*** gfa_away is now known as gfa_23:48
*** chlong has quit IRC23:53

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