21:01:38 #startmeeting networking 21:01:39 Meeting started Mon Jun 16 21:01:38 2014 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:42 The meeting name has been set to 'networking' 21:01:54 #link https://wiki.openstack.org/wiki/Network/Meetings Agenda 21:02:16 Juno1 was released last week 21:02:22 #link https://launchpad.net/neutron/+milestone/juno-1 21:02:31 Great work by all involved! 21:03:09 I have started grooming the Juno-2 milestone as well now 21:03:33 I also wanted to mention the upcoming mid cycle sprint for nova-network parity 21:03:45 Any other announcements for the team? 21:04:18 #link markmcclain1 don't forget link to tarball: http://tarballs.openstack.org/neutron/neutron-2014.2.b1.tar.gz 21:04:32 Thanks for reminding me markmcclain1 :) 21:05:09 mestery: you're welcome 21:05:22 #topic Bugs 21:05:39 enikanorov has listed some bugs we should be aware of 21:05:50 I encourage people to view the agenda 21:06:16 It looks like arosen1 has also linked nova bugs we should be reviewing 21:07:22 speaking of locks, we in Red Hat also got another Lock wait timeout bug for floatingips a day ago, I was going to investigate it 21:07:47 looks like some general issue (I'll report my specific failure upstream tomorrow) 21:07:48 Thanks ihrachyshka 21:08:08 Any other bugs the team should be aware of this week? 21:08:34 I have a suspect we already have bugs for all three reported by enikanorov. I think there is also an oustanding patch for one of the three 21:09:01 beyond that - no other bug we should be aware of on my side. 21:09:12 Thanks salv-orlando 21:09:21 salv-orlando: hmm, i've looked through existing bugs, they were alittle bit different 21:09:33 (update operation vs create, or such differences) 21:09:49 but i may be wrong 21:09:53 I remember exactly those three instances 21:10:02 let’s take that offline 21:10:17 sure. also feel free to mark as duplicate 21:10:18 I think you want to sleep after the meeting as it’s 1AM foryou I guess 21:10:34 honestly i want to sleep right now :) 21:10:45 #topic Team Discussion Items 21:10:57 Is prad here? 21:11:34 prad wanted to discuss a patch focused an helping ceilometer 21:11:42 But if he's not here we will move on 21:12:46 #topic Nova Parity 21:12:51 hi 21:12:53 Hi 21:13:02 so obondarev has been busy 21:13:10 and posted a WIP for the nova extension 21:13:21 Nice! 21:13:26 #link https://review.openstack.org/#/c/100265 21:14:18 I encourage neutron devs to review that 21:14:37 the WIP is early, so he'll be adding more features to it 21:15:13 Any other updates here markmcclain1? 21:15:21 thats all for this week 21:15:28 Thanks! 21:15:41 #topic Docs 21:15:58 emagana: hi! 21:16:05 mestery: hi there! 21:16:20 no updates from the docs side 21:16:43 Good to hear things moving smoothly there emagana. :) 21:16:44 But... 21:16:59 the same recommendation that last week, we need to be sure that we have either bugs or bps filed against neutron 21:17:40 mestery: I would like to see all the new staff with "DocImpact" added on the commit message 21:17:41 Good reminder emagana. 21:17:59 besides that, all major bugs are assigned 21:18:07 Yes, people should be cognizant of that. 21:18:10 Thanks! 21:18:19 emagana: do what kind of changes need DocImpact flag? 21:18:51 amotoki_: anything that changes the way we use/deploy/configure neutron staff 21:19:03 amotoki_: and new features like DVR for instance 21:19:38 in my understanding the configuration guide is built automatically, so i don't think DocImpact is necessary for patches which only affects the configuration guide. 21:20:47 amotoki_: It would not affect the tag anyway, I would prefer to tag as invalid a bug that missing a change 21:21:23 emagana: sounds good. we need to take care of DocImpact flag more. 21:21:33 mestery: that's all 21:21:40 Thanks emagana 21:21:42 is this uptodate? https://wiki.openstack.org/wiki/Documentation/DocImpact 21:21:54 emagan: ^^^ 21:22:05 emagana: ^^^ 21:22:21 yamamoto: not 100% sure 21:22:35 yamahata: last edit was the 11th, so I'm guessing yes 21:22:37 let me bring that with the docs team 21:22:43 yamamoto: ^^^ 21:23:07 #topic Tempest 21:23:17 mlavalle: hi! 21:23:23 hi! 21:23:56 we added the 27th api test to the tempest repo this week, out of the 28 that we targeted in January 21:24:09 Nice! 21:24:41 the one remaining to merge is actually mine….. I am having somo tough times with Jenkins, but we will get there 21:25:23 I've been wrting a rst file that will be added to the tempest repo, with the tutorial to develop scenario tests for Neutron 21:25:40 Awesome 21:25:42 that will be very helpful mlavalle! 21:25:55 it will become part of the tempest docs 21:26:28 it's taking a little longer than expected because I am targeting new developers, so I walk them through the classes and all the details 21:27:14 I have been talking to the LBaaS guys at Rackspace to make sure we have a new api document to start implementing tests 21:27:53 and finally I had a nice conversation with sc68cal a while ago. he is developing some tests for ipv4 and ipv6 on proviuder networks 21:27:54 Awesome! I expect we can talk more on that in person this week too. 21:28:10 that's all I have 21:28:25 Thanks! 21:28:53 mestery: I'll see you tomorrow here 21:29:04 #topic Advanced Services 21:29:16 SumitNaiksatam: hi! 21:29:21 mestery: hi 21:29:32 we are still waiting of approval of blueprint specs 21:29:47 the most notable among them is enikanorov’s flavors bp 21:29:49 Yes. 21:30:04 #link: https://review.openstack.org/#/c/90070 21:30:05 I was looking at that one earlier today 21:30:13 mestery: great, thanks 21:30:32 our hope is that we have can move forward on this by the end of this week 21:30:39 I encourage people to review the flavor BP ^^^ 21:31:03 i propose that we have a decisive conversation on this during this week’s adv services’ IRC on wednesday 21:31:34 at least a couple of other bp specs (serivice insertion and traffic steering) are also pretty ripe 21:32:03 Sounds good I will do my best to make that meeting 21:32:03 fyi - #link https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan 21:32:21 mestery: nice, i know you will be in the LBaas sprint as well 21:32:37 Yes :) 21:32:48 thats it for this, unless there are questions for the adv services’ team 21:33:03 * mestery waits for a bit for questions 21:33:49 #topic IPV6 21:33:51 mestery: i think cue for you to proceed :-) 21:33:58 sc68cal: hi! 21:35:10 #topic ML2 21:35:26 rkukura: Jow goes NP prioritization? 21:35:26 not much to report yet 21:35:30 How 21:35:33 BP 21:35:38 we’re still working on prioritizing BPs and reviewing specs 21:35:57 check out https://wiki.openstack.org/wiki/Tracking_ML2_Subgroup_Reviews 21:36:02 sorry, was afk for a moment and missed my queue 21:36:04 *cue 21:36:18 sc68cal: well come cback to you 21:36:55 rkukura: Thanks for prioritizing those ML2 BPs 21:36:58 It helps 21:37:04 right, we are using this wiki to track reviews within the subteam prior to recruiting core reviewers 21:37:37 Code and spec reviews? 21:37:38 that’s all I have - Sukhdev, anything else? 21:37:57 rkukura: no, we are good 21:38:07 mestery: I think that is the plan 21:38:10 Thanks ML2 folks! 21:38:22 #topic IPv6 21:38:30 sc68cal: hi! 21:38:47 hello 21:39:01 So there's a couple big items on the agenda that I listed today 21:39:21 we had a meeting today with mestery and markmcclain1 regarding the API, as well as BPs targeted for j-2 21:39:36 Yes that was a helpful meeting 21:40:03 I still have some concerns about the radvd and dnsmasq stuff, but it is primarily around getting somthing done in the juno timeframe 21:40:55 I think at this point I'll let people digest what I've put on the wiki page 21:40:59 That may warrant another meeting :) 21:41:07 https://wiki.openstack.org/wiki/Network/Meetings#IPv6_.28sc68cal.29 21:41:34 hopefully we can get a spec created quikcly for the radvd change 21:41:35 Thanks sc68cal! 21:41:39 thx 21:41:40 Yes 21:42:07 #topic Group Policy 21:42:22 SumitNaiksatam: hi again! 21:42:32 mestery: indeed, hi again 21:42:44 we are getting some good coverage with the intial set of patches 21:42:46 I see new patches pushed which is great! 21:42:49 Yes 21:42:56 i meant review coverage 21:43:02 more patches are on the way 21:43:10 rkukura: you want to chime in as well? 21:43:20 OK 21:43:51 The 2nd series of GP patches maps the initial set of GP resources to neutron resources 21:44:09 These should be pushed for review over the next few days 21:44:40 Thanks rkukura 21:45:31 Anything else on GBP for the team? 21:45:49 mestery: we also good discussions on UT and testing 21:46:01 Very good ! 21:46:12 mestery: i believe we have consensus on moving forward based on everyone’s input 21:46:34 Great! 21:46:47 fy- please join weekly meetings - #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy 21:47:10 mestery: that shuold be it for this week, thanks for giving us the time here 21:47:21 GBP == GP ? 21:47:27 Thanks SumitNaiksatam and team! 21:47:29 yamahata: yes 21:47:42 yamamoto: yes 21:48:00 thank you 21:48:19 #topic FWaaS 21:48:32 SumitNaiksatam: we meet again :) 21:48:41 mestery: ha :-) 21:48:48 ;) 21:48:51 GBP=Great British Pound 21:49:00 we have a high priority bug whose review is curently blocked: #link https://review.openstack.org/#/c/90575/ 21:49:38 we also have a blueprint spec in review for “service objects”: #link https://review.openstack.org/#/c/94133 21:49:59 the expectation is that service objects will be applicable beyond just FWaaS 21:50:05 please review if you get a chance 21:50:18 Yes I encourage folks to review that 21:50:22 and we would like to make progress with the high priority bug noted about 21:50:26 *above 21:50:41 thats it from the FWaaS team 21:50:46 SumitNaiksatam: I'll take another look at the bug 21:50:56 markmcclain1: thanks much! 21:51:05 markmcclain1: i also need to revisit it :-) 21:51:12 Thanks! 21:51:30 #topic Open Discussion 21:51:45 anteaya: here? 21:51:54 Your item is up now. 21:51:55 yes 21:51:58 Ok 21:52:00 what did I have 21:52:15 DriverLog and unreliable info 21:52:26 oh yeah 21:52:33 driverlog is unrelable 21:52:34 Did we cover that earlier today at 3rd party meeting? 21:52:36 don't use it 21:52:38 yes 21:52:40 :) 21:52:42 Ok 21:52:46 and last week too I thought 21:52:48 I encourage folks to read the logs 21:52:52 Ok 21:52:56 read the logs 21:52:56 No worries 21:53:01 sorry 21:53:05 Any other items from folks? 21:53:14 does anyone know the status of multi-node testing/devstack? 21:53:31 In the gate? 21:53:33 well it was discussed last release 21:53:40 It's not there yet 21:53:43 some people were working on it with sdague 21:53:52 lately crickets as far as I know 21:54:17 i think we need to move forward it to support DVR or some other stuff. 21:54:26 amotoki_: infra is good with that 21:54:32 Agreed amotoki_ 21:54:41 amotoki_: put an item on tomorrow's infra agenda 21:54:47 I will sync with carl_baldwin when he's back 21:54:54 And figure that out with infra as well 21:54:56 I will dig through logs to see what was discussed last release 21:55:03 thanks 21:55:07 np 21:55:35 If there is nothing else well close early today. 21:55:41 Thanks everyone! 21:55:42 I think we need multi-node nova network testing 21:55:45 ehm... I also encourage people to check remaining oslo-messaging patches at: https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/oslo-messaging,n,z Some of those patches are already in the tree or in gate now, but still lots of them (and the most important) waiting in the queue for review. So please criticise! :) 21:55:54 and then we can pass those tests with dvr 21:55:58 we shouldn't focus testing only dvr 21:56:04 marun: infra wants multi-node for any testing 21:56:12 Multi ode 21:56:18 not just dvr of flavour of the month 21:56:20 anteaya: testing -> we need tests to actually take advantage of that 21:56:28 marun: agreed 21:56:51 anteaya: violent agreement ;) 21:57:02 I'm all done with violence 21:57:10 weak is the best I can muster today 21:57:12 * mestery loves it when there is agreement 21:57:24 maybe tomorrow 21:57:32 Ok thanks folks, see you all in channel and next week! 21:57:40 #endmeeting