16:01:45 #startmeeting Large Deployments Team April 2016 Meeting 16:01:46 Meeting started Thu Apr 21 16:01:45 2016 UTC and is due to finish in 60 minutes. The chair is VW. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:49 The meeting name has been set to 'large_deployments_team_april_2016_meeting' 16:01:49 :) 16:02:11 oh good - dronshaw and cloudhollyb_, you both made it! 16:02:11 o/ 16:02:23 yep! glad to be here 16:02:33 ditto 16:03:00 belmoreira, hi! glad you could make it too 16:03:03 hey guys 16:03:21 hello everyone 16:03:42 Central Texas should be nice and soggy by the time you all start showing up the next few days 16:03:43 :D 16:04:01 10” in one day, craziness. 16:04:10 we are still working on melting snow here 16:04:41 so, I really only had one topic for today 16:04:42 looks like summer in Geneva :) 16:04:52 ha - indeed, belmoreira 16:05:08 #topic Summit Session Planning 16:05:49 in case anyone needs it, here is our etherpad - https://etherpad.openstack.org/p/AUS-ops-Large-Deployments-Team 16:05:57 if you didn't know, we have 3 sessions next week 16:06:23 Monday at 11:15 and 12:05 and Wed at 1:50 16:08:18 So, a few notes are already in there - mostly around catching up on old work the team has been doing 16:08:35 yeah i dropped in the follow up stuff i could remember from Tokyo and other meetings 16:08:57 I'm assuming we have some new burning issues we'd like to float up as new things to chase 16:09:00 klindgren and i asked carlbaldwin to come to our Monday session 16:09:08 oh - cool 16:09:09 which one 16:09:24 I mean, I know it will be one long one 16:09:42 but didn't know if one of the two "official" time slots suited them better 16:09:52 not sure, we need to follow up with him and see what works for his schedule i guess. i can ping him today and see what works bets 16:09:54 *bet 16:09:58 *best. geeze. 16:10:26 cool 16:11:21 Since I know we have some new folks, I'd like to know how we can take some of this time to help you all understand the team and share some of your problems 16:12:13 my gut mdorman is we'd want them to come closer to the start of the second session so we have time to do a bit of what I just said 16:12:23 then catch up with Neutron 16:12:31 then dive into some new stuff 16:12:39 that's just a rough idea though 16:12:49 btw there will be Performance WG results/plan session on the summit as well - https://www.openstack.org/summit/austin-2016/summit-schedule/events/7399 - we did not collect much feedback yet from the LDT, although I believe it'll be interesting. This cycle we were mostly focused on the cloud underlying technologies like MQ/DB/provisioning/etc. 16:12:51 belmoreira: is already lighting things up around cells :D 16:13:48 that sounds good to me. i've been working with some of my colleagues to polish our pain points and see what you guys think. so second session would be best for that? 16:13:54 VW: yeah makes sense, i’ll thrown that out as a possibility. 16:14:14 good stuff, DinaBelova - added a note in our etherpad for extra visibility to that session 16:14:23 VW - ack, thanks 16:14:44 we are pretty flexible dronshaw 16:14:57 usually, we have a good agenda and then manage to derail it 16:15:17 hahah 16:15:26 in a good way, of course 16:15:29 no that there’s anything wrong with that 16:15:31 as go all great meetings :) 16:16:08 would it be best for me to add that content to the etherpad you linked above, or just come prepared to the sessions? 16:16:15 now that we have some new players, though, I think some time spent going back through large issues they bring to the table and either sharing tips and/or finding common pain relative to those is great 16:16:30 we can start a section in the pad, dronshaw 16:17:00 agreed, some review of the history would be useful. 16:17:01 Back in Vancouver, we organized around some common needs with networking and engaged with the Neutron team 16:17:06 sounds great, appreciate the help everyone 16:17:26 our next candiate was common cells V1 patches, but I'm afraid that ship has sailed :\ 16:17:49 yeah don’t think there’s much sense in pushing on that any more. 16:17:57 probably better to focus efforts on migration path to v2 16:18:44 * VW was hoping that would just involve "magic" 16:19:28 oh i’m sure it will involve lots of magic! hah 16:22:59 so, I think the first 40ish minutes can be intro and a little usecase/pain sharing? 16:23:11 unless anyone objects 16:23:35 that sounds good to me 16:23:49 +1 16:24:00 also, selfishly, I'd love to use the break between Monday and Wed, to identify things we need to engage with other teams/devs on, go engage and then recap on wed 16:24:25 but that's assuming we get A LOT done in 2 40 minute sessions :P 16:24:28 see if we can re-find something that we are all fixing in our own openstack installs. To refocus on. Since that worked pretty well with neutron. 16:24:34 sounds great 16:25:28 +1 16:25:31 ok - we'll make that the general goal then and work the Neutron folks in when they can be there. If we haven't settled on something by the end of Monday , we can pick back up on Wed, but hopefully we can do some work in between 16:25:34 i think we can kinda state a goal at the beginning of the monday sessions to come out with a couple solid action things to get with other teams about. 16:25:50 +1 16:29:57 (i have to go run our standup right now, so might be slow to respond here) 16:30:42 no problem 16:30:57 I think we've knocked out the main bits for summit planning 16:31:06 unless anyone has anything specific they want to bring up 16:31:14 Wed session conflicts with design sessions so I think we should try to do most of the work Mon and leave Wed only for open discussion. 16:31:15 please keep making all those notes in the ether pad 16:31:41 good call out belmoreira 16:31:44 Are there any cross project/op feedback session that people are planning on goingto 16:31:54 let me make a note 16:33:55 probably klindgren 16:34:05 made a section so we can start identifying those for all 16:34:26 kk 16:38:45 cool - any other summit related stuff? 16:39:27 if not would love to give dronshaw and cloudhollyb_ time to ask the group questions 16:39:50 +1 on that 16:40:04 #action VW clean up summit etherpad based on today's discussion 16:40:24 nothing else for me 16:40:30 #topic General Discussion 16:41:01 thanks everyone. I'm new to WG's, so wanted to take the opportunity to sit in and get a feel for the plans next week. hoping to come with our other engineers and share some of our pain points during our large deployments 16:42:07 super excited to have some new perspectives (not that I don't love working with usual band of misfists ;) ) 16:42:21 +1 16:42:38 in general, though I'd say that LDT has done a good job of showing that a working group can actually get work done 16:43:11 largely due to the efforts of mdorman, klindgren and belmoreira and their bridging for our pain points to dev teams 16:43:28 yeah it’s been a long process, but neat to see that work 16:44:02 we've also done some pretty cool combined talks with members of LDT from different orgs discussion how they use certain features or have common approaches 16:44:18 it be nice if we can identify some more of those for Barcelona and beyond 16:45:16 +1 16:45:19 agreed. would love to see us be more effective in knowledge sharing and working upstream. hoping Austin is a great start :) 16:45:37 and by us I mean att, haha 16:46:31 I think it will be 16:47:07 you are joining up with an impressive group of Stackers. I'm impressed every time I get to hang out with them all 16:47:08 I'm going to have to drop off early. was great meeting everyone 16:47:19 great having you dronshaw 16:47:26 see you in Austin 16:47:51 actually, if nobody has anything else, I'm happy to give you all 13 minutes back 16:48:18 sounds good. thanks for driving VW 16:48:40 my pleasure. really glad we have a loose plan for Austing. I'll organize the etherpad 16:48:48 and update the wiki with today's meeting notes 16:49:01 everybody travel safe and all that 16:50:02 #endmeeting