21:00:37 <mestery> #startmeeting networking 21:00:38 <openstack> Meeting started Mon Apr 13 21:00:37 2015 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:41 <openstack> The meeting name has been set to 'networking' 21:00:46 <mestery> #link https://wiki.openstack.org/wiki/Network/Meetings Agenda 21:00:50 <mestery> We have a very small agenda 21:00:57 <mestery> I've likely just jinxed us 21:01:01 <mestery> Lets get right to it! 21:01:09 <mestery> #topic Announcements 21:01:11 <dougwig> throw a name change into the topic list 21:01:19 <emagana> hi there! 21:01:24 <mestery> lol 21:01:24 <mestery> We cut the RC! 21:01:26 <mestery> #link https://launchpad.net/neutron/+milestone/kilo-rc1 21:01:37 <xgerman> Hooray! 21:01:40 <mestery> Please file any bugs you think are RC candidates as "kilo-rc-potential" 21:01:47 <vishwanathj> congratulations to one and all 21:01:54 <mestery> Unless we find release critical issues, this will be our Kilo release 21:02:13 <kevinbenton> so if something is back-portable but not critical, hold off? 21:02:21 <salv-orl_> aloha 21:02:24 <mestery> In honor of a successful RC, I broke the world release python-neutronclient 2.4.0 ... but only for a few hours. 21:02:24 <mestery> #link https://launchpad.net/python-neutronclient/2.4/2.4.0 21:02:31 <mestery> I continually learn things about releasing client libraries with reach release 21:02:40 <mestery> The branch plan for the client library is as follows: 21:02:56 <mestery> #info client library branch plan: 2.3.x: Juno, 2.4.x: Kilo, 2.5.x: Liberty 21:02:57 <salv-orl_> mestery: yeah about that I learnt only thing - I should never attempt to do anything like that 21:03:10 * mestery nominates salv-orl_ to release the next client library. 21:03:24 <mestery> One more announcement 21:03:24 <mestery> wait for it 21:03:26 <mestery> #link http://lists.openstack.org/pipermail/openstack-dev/2015-April/060713.html 21:03:33 <mestery> The mid-cycle coding sprint is in Fort Collins, CO 21:03:46 <mestery> Also, we'll have a second coding sprint in Tel Aviv, Israel focused on QoS 21:03:49 <mestery> Stay tuned for details on that one. 21:03:57 * mestery catches his breath 21:04:15 <mestery> Any questions? 21:04:31 <angela-s2> kevinbenton had one 21:04:43 <mestery> kevinbenton: Yes 21:05:06 <kevinbenton> ok, so when is kilo "open for backports" ? 21:05:16 <kevinbenton> after the official release? 21:05:24 <mestery> kevinbenton: Yes 21:05:33 <haleyb> has the paint dried yet? :) 21:05:42 <mestery> haleyb: lol 21:05:56 <kevinbenton> sounds good 21:06:24 <armax> haleyb: it depends if we’re trying to paint the sistine chapel 21:06:40 <dougwig> haleyb: on openstack? does that answer have to be constrained to kilo? 21:07:07 <mestery> OK, in the interest of keeping this short, lets move on. 21:07:12 <mestery> #topic Bugs 21:07:24 <mestery> enikanorov enikanorov_: Hi! Are you around? 21:07:32 <mestery> And if not, does anyone else have any bugs they want the broader team to be aware of today? 21:07:46 * mestery is still dazed and confused from the RC a bit. 21:08:54 <mestery> OK, lets move right along then, again, in the interst of keeping this short. 21:09:01 <mestery> #topic Design Summit 21:09:13 <mestery> Now that we're (almost) out of the Kilo business, it's time to think about Liberty 21:09:24 <mestery> #link https://etherpad.openstack.org/p/liberty-neutron-summit-topics 21:09:27 <mestery> Some great ideas on there 21:09:46 <mestery> Over the next few weeks, we'll be finalizing the agenda for Vancouver. 21:10:08 <mlavalle> mestery: is there a deadline to submit ideas to the etherpad 21:10:12 <mlavalle> ? 21:10:29 <mestery> mlavalle: Not a firm deadline, I'd say by next week we should have the ideas on there. 21:10:37 <mestery> mlavalle: We already have a lot of fun things on there :) 21:10:42 <blogan> mestery: *aas topics should go in here too? 21:10:46 <yamahata> how about LT? 21:10:47 <mestery> blogan: Yes sir! 21:10:58 <mestery> yamahata: LT? 21:11:08 <yamahata> Lightening talk 21:11:15 <kevinbenton> yamahata: at the bottom 21:11:25 <mestery> thanks kevinbenton 21:11:29 <yamahata> I mean dead line for applying lighting talk. 21:11:31 <mestery> Yes, Lightning Talks are at the bottom 21:11:54 <mestery> yamahata: Lets go with the same. If we have more lightning talks than slots we'll vote again like we did for Paris 21:12:18 <yamahata> mestery: I see. thanks 21:12:28 <mestery> Do people have any other questions on the Design Summit at this point? 21:12:48 <kevinbenton> mestery: how much happens concurrently? 21:12:57 <mestery> kevinbenton: A lot ;) 21:13:05 <mestery> kevinbenton: Tuesday is cross project and ops sessions 21:13:10 <mestery> Wed/Thur are sessions for everyting else 21:13:24 <mestery> For those remaining Friday, there will be space for collaboration 21:13:31 <mestery> e.g. coding sprints 21:13:45 <mestery> Also, the conference runs concurrently and goes Mon-Thur 21:13:46 <kevinbenton> mestery: what i meant is, out of the allocated slots for neutron, do any happen simultaneously? 21:13:49 <salv-orl_> I think however we should probably do *only* ligthning talks, so everybody will have a chance to share their ideas and proposals 21:13:57 <mestery> kevinbenton: No, neutron sessions are all serial 21:14:19 <kevinbenton> cool 21:14:19 <dougwig> as long as kevinbenton does his code review talk, all will be right in the world. 21:14:24 <mestery> salv-orl_: That's an interesting idea. 16*5 = 90 lighning talks! 21:14:25 <mestery> With no breaks in between! 21:14:28 <salv-orl_> because that's what the design summit is about, isn'it? "Design" is not really a thing we really want to do 21:15:00 <kevinbenton> salv-orl_: i thought we saved design desicions until a week before the release? 21:15:12 <mestery> kevinbenton salv-orl_: That's what the RC is for. 21:15:42 <dougwig> no, no, design decisions stay in the private "cores only" IRC channel. 21:15:50 <dougwig> and hey lurkers, THAT WAS A F**KING JOKE. 21:16:05 <mestery> lol 21:16:09 <mlavalle> Lol 21:16:17 <salv-orl_> also somebody stole wihite on red background from the etherpad. Thas was MY color 21:16:24 <mestery> So, just to remind folks: 21:16:31 <emagana> Action Item - Hack the :core only" IRC 21:16:35 <mestery> We have 7 "fishbowl sessions", and 9 "working group sessions" 21:16:54 <mestery> 200 people in fishbowl, 20-40 in working groups 21:17:17 <salv-orl_> dougwig: core only? There are a lot of circles within circles ;) 21:17:23 <kevinbenton> salv-orl_: i didn't steal it, i used a slightly different shade of red :) 21:17:27 <rkukura> mestery: If we don’t have concurrent working group sessions, where will everyone go during these? 21:17:37 <xgerman> sight seeing? 21:17:47 <dougwig> i wonder how long until the TC sends a subpeona to my house now. 21:17:52 <neiljerram> So do working group sessions require invitation or sign up (to manage the numbers)? 21:18:00 <kevinbenton> salv-orl_: there, you can have your color :) 21:18:04 <mestery> rkukura: We have 2 slots with no overlap, ideally people will go to the QA and nova overlap sessions I'm planning 21:18:16 <salv-orl_> mestery: I am serious this time. Pick release priorities before the summit, and assign a working group session to each of them 21:18:22 <markmcclain> dougwig: I'm filling out the paperwork now 21:18:24 <mestery> neiljerram: Working group sessions will ahve boring names to discourage casual entrants 21:18:40 <neiljerram> Boring and cryptic? 21:18:42 <salv-orl_> so we can establish "workling group" of people that will take care of that work item throughou the release cycle 21:18:42 <kevinbenton> is there a session on nova/neutron communication? 21:18:44 <mestery> salv-orl_: I am too! We need to do that, we tried in Paris, lets do it again this time. 21:18:49 <mestery> salv-orl_: Makes sense. 21:18:57 <salv-orl_> mestery: for the 7 fishbowl sessions... I believe that's showtime 21:19:24 <mestery> salv-orl_: Awesome 21:20:09 <neiljerram> As a newbie, it's going to be fun to try to navigate all this... 21:20:24 <mestery> neiljerram: Lots of folks willing to help you out I bet :) 21:20:46 <blogan> takes a lot of focus 21:20:59 <blogan> and caffeine 21:21:01 <mestery> OK, lets move on, we're almost done I suspect 21:21:02 <salv-orl_> mestery: the trick is to have a room where the session name is also a buzzowrd like "NFV-aas WAN EDGE" 21:21:04 <watanabe_isao> mestery, may I ask a question about etherpad? 21:21:12 <neiljerram> Thanks :) 21:21:19 <watanabe_isao> I am not able to be in Vancouver. But I have put an idea there. Should I delete it? 21:21:24 <mestery> salv-orl_: We discussed the "NFV Docker" honeypot room 21:21:24 <mestery> It's a valid concept 21:21:35 <mestery> watanabe_isao: No, it's fine to leave it there for now, but it's up to you. 21:21:38 <salv-orl_> and then have just a projector showing "battleship potemkin" over and over 21:21:38 <xgerman> lol 21:21:42 <salv-orl_> and no coffee in the room 21:21:46 <watanabe_isao> mestery, thanks. 21:21:50 <neiljerram> That so works. 21:21:53 <mestery> #topic Open Discussion 21:22:02 <kevinbenton> what is battleship potemkin? 21:22:06 <mestery> We may finish this is record time! 21:22:10 <emagana> mestery: I want to share something about Docs! 21:22:13 <mestery> A smooth RC is to blame really :) 21:22:17 <mestery> emagana: Please do! 21:22:38 <neiljerram> kevinbenton: A film by Sergei Eisenstein? 21:22:46 <banix> kevinbenton: it has to do with pumkin 21:22:51 <emagana> So, we are organizing the Networking Guide Doc Day! 21:23:02 <mestery> emagana: Cool! 21:23:14 <salv-orl_> kevinbenton: Considering your employer, I think you might be fired for not knowing that movie 21:23:16 <emagana> It will be next week on April 23rd 2015 21:23:54 <mestery> #info Networking Guide Day April 23, 2015 21:23:58 <emagana> Etherpad will be use to coordinate who will be doing what. 21:24:22 <emagana> #link https://etherpad.openstack.org/p/networking-guide 21:24:41 <markmcclain> #info markmcclain will off the grid Apr 17-28th 21:24:57 <emagana> The Networking Guide ToC Wiki explains the process to do patches: https://wiki.openstack.org/wiki/NetworkingGuide/TOC 21:25:31 <emagana> Our wiki has been update with all the details. All docs are now in .RST which makes easier to contribute.. please plan to attend it. 21:26:10 <emagana> I will coordinate to have an IRC channel for the work.. but probably will make sense to use the current #openstack-doc one 21:26:35 <mestery> #info markmcclain's wedding is April 18. 21:26:40 <mestery> Early congrats markmcclain :) 21:26:45 <markmcclain> mestery: thanks! 21:26:46 <emagana> A lot of the work has been already completed but we need people to review it and provide feedback and open bugs if needed 21:26:46 <blogan> congrats markmcclain! 21:26:48 <xgerman> congrats! 21:26:50 <dougwig> markmcclain: congrats. 21:27:09 * mestery thinks we should save markmcclain some DB related bugs for post-honeymoon 21:27:24 <blogan> or crash his honeymoon with a coding sprint 21:27:25 <markmcclain> blogan, xgerman, dougwig: thanks 21:27:34 <emagana> blogan: +1 21:27:35 <mestery> lol 21:27:36 <dougwig> lbaasv2 during his honeymoon. 21:27:38 <dougwig> v3 21:27:41 <mestery> v4! 21:27:42 <xgerman> +1 21:27:42 <emagana> markmcclain: My best wishes! 21:27:45 <mestery> dougwig: See what I did there? 21:27:52 <blogan> bourbon + beach! 21:28:04 <markmcclain> blogan: haha… the place does have free drinks 21:28:05 <vishwanathj> mestery, is there a link that lists all kilo-rc-potential bugs/patchsets, Thanks 21:28:12 <marun> congrats! 21:28:32 <mlavalle> markmcclain: best wishes! 21:28:54 <mestery> vishwanathj: Yes, there should be, looking 21:28:54 <carl_baldwin> +1 Congratulations 21:29:28 <mestery> #link https://bugs.launchpad.net/neutron/+bugs?field.tag=kilo-rc-potential 21:29:31 <mestery> vishwanathj: ^^^ 21:29:37 <mestery> OK, if there's nothing else, lets wrap this up. 21:29:40 <markmcclain> emagana, marun, mlavalle, carl_baldwin: thanks 21:29:43 <mestery> Thanks again to all for the awesome work in Kilo! 21:29:45 <vishwanathj> mestery, thanks 21:29:54 <vishwanathj> markmcclain, congratulations and all the best 21:29:55 <mestery> See you all in channel and on the ML! 21:30:01 <mestery> #endmeeting