18:32:56 #startmeeting Networking FWaaS 18:32:57 Meeting started Wed May 21 18:32:56 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:32:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:33:01 The meeting name has been set to 'networking_fwaas' 18:33:17 #topic bugs 18:34:05 #link https://bugs.launchpad.net/neutron/+bug/1314313 18:34:15 SridarK: you are working on this 18:34:36 SumitNaiksatam: yes - a bit slow this week 18:34:52 i think we may have a corner case timing issue 18:34:54 SridarK: thanks for your effort 18:35:06 SridarK: ok 18:35:09 SumitNaiksatam: no worries - will keep u posted on this 18:35:22 SridarK: per salvatore’s comments, i am glad that this is not hitting the gate as much now 18:35:39 i need to drive the workflow programattically to see if i can reproduce 18:35:49 SridarK: but lets try to wrap this up, if its outside our control, we can create a different bug for the router 18:35:59 SumitNaiksatam: sounds good 18:36:24 #link https://bugs.launchpad.net/neutron/+bug/1320775 18:36:35 not sure if Rajesh is here 18:37:12 Hi Sumit 18:37:13 it was great that he got the fix in quickly: #link https://review.openstack.org/#/c/94516/ 18:37:30 rand738: hi 18:37:55 SumitNaiksatam: I went thru the review - just need to validate on the deferred being turned off 18:37:58 Rajesh’s fix looks good, but i just wanted to check if we can add a UT, so that we catch this 18:38:06 i will also post a review on this 18:38:07 SridarK: nice! 18:39:21 #link https://bugs.launchpad.net/neutron/+bug/1310857 18:40:04 looks like the author needs to address some comments 18:40:14 however this is high, may be we need to follow up with him 18:41:01 Yes - i was not sure on the approach of getting the FWaaS Plugin on the agent 18:41:32 #link https://bugs.launchpad.net/neutron/+bug/1318617 18:42:24 havent investigated this 18:42:32 but its currently low 18:42:37 if anyone wants to take it 18:42:50 Hmm this is odd 18:43:25 fairly easy recreate - let me try a recreate and post comments on the bug 18:43:31 SridarK: nice 18:44:00 #topic Juno planning and feature tracking 18:44:31 so my proposal is that we start tracking things in this meeting 18:44:36 #link https://wiki.openstack.org/wiki/Neutron/FWaaS/JunoPlan 18:44:57 SumitNaiksatam: +1 18:45:04 +1 18:45:08 ok cool 18:45:22 i volunteered your names for a lot of things :-P 18:45:35 these are placeholders 18:45:37 SumitNaiksatam: thats good 18:45:38 +1 18:45:43 others can jump in 18:46:00 but we need to be cognizant of the fact that these aspects need to be covered for every feature 18:46:32 i havent checked if there are any tempest related pending blueprints, we would need to add those here 18:46:48 SumitNaiksatam: spoke to mlavalle as well 18:46:51 so we are in general agreement with the process of tracking here? 18:46:56 SridarK: great 18:47:05 he will be adding something for tempest scenario 18:47:22 yes in agreement 18:47:58 ok 18:48:32 #topic proposed features’ and blueprints 18:49:05 rather than going into each blueprint today, i suggest that we just have a general discussion 18:49:17 SumitNaiksatam: yes that is better 18:49:25 is there any feedback that you folks got after our session 18:49:27 ? 18:49:33 i had to leave to catch the flight 18:49:56 other than dvr, no much from me 18:50:09 SumitNaiksatam: i thought it was well recvd - had a few folks come and talk after and looks like we are on track with our priorities 18:50:10 beyounn_1: ok, again great that you brought it up 18:50:15 SridarK: nice 18:50:34 beyounn_1: suggestion - to get the DVR issue on record, can you send out an email to the mailing list? 18:50:57 I put it in the DVR ether pad already 18:51:10 and had an discussion with DVR forks this morning 18:51:18 i will keep update based on the discussion 18:51:18 beyounn_1: cool, but people might forget the etherpad (and its not searchable via google) 18:51:41 Yes, let me collect all the feedbacks and thoughts then send an email 18:51:49 beyounn_1: i would just say that you can copy paste your input in the etherpad and send to the dev mailer 18:51:53 beyounn_1: thanks 18:51:57 Sure 18:52:22 beyounn_1: is there any solution apparent? 18:52:39 yes 18:52:46 That is what I want to talking about 18:52:55 Do we have time now? 18:53:11 I you prefer that I send an private email among all of us ? 18:53:12 beyounn_1: sure 18:53:33 beyounn_1: may be quick update, so that others who read these logs know what is going on 18:54:13 Since the br-int knows whether a packet has be routed or switched, so we can add something in the br-int to force the traffic to fw before the traffic hits on the DVR 18:54:47 I got two questions that is working on, 1 if we are not on router, then we don't don't have zone but just can use address book 18:55:13 even if we are using address book, how can we get the namespace info is something I'm still not clear 18:55:39 And I took action item to dicuss these with FWaaS team 18:55:52 Ok, this is the summary for this morning's meeting 18:56:50 shot, bad bad typing 18:57:01 can you guys understand what I have typed ? :-) 18:57:06 beyounn_1: ;-) 18:57:12 i am trying to :-P 18:57:20 beyounn_1: perhaps more offline discussion 18:57:31 Ok, let's me send out email :-) 18:57:50 sorry, for the typing... 18:57:56 in a meeting ... :-) 18:58:00 beyounn_1: i did not get the address book part, but that might just be terminology 18:58:13 think about subnets 18:58:17 beyounn_1: ok, sorry to put you on the spot 18:58:34 beyounn_1: you can follow up in your email 18:58:36 SumitNaiksatam: not at all 18:59:07 I will send email later today 19:00:01 SridarK gduan: any other feedback you received? 19:00:35 SumitNaiksatam: had some discussion on Zones with some folks - mostly other vendors 19:00:51 SridarK: ok good, do agree with the idea? 19:01:04 *do they 19:01:04 SumitNaiksatam: yes we are aligned 19:01:42 SridarK: ok good 19:02:25 gduan: any discussions on the flavors? 19:03:28 Hi 19:04:01 Mark commented on the spec review and asked to added detail 19:04:26 Did Eugene put on his spec? 19:05:04 gduan: eugene is on the road 19:05:13 gduan: so he has not updated his spec 19:05:23 gduan: i think he is going to be on the road at least for a week 19:06:11 Gary is on customer call now 19:06:15 once eugene gets back, lets have a focussed meeting with the reviewers and hash out the details once and for all 19:06:21 beyounn_1: sure np 19:06:35 SridarK: is pradeep around? 19:06:54 SumitNaiksatam: Hmm i am not sure 19:07:01 I would like to understand if he has everything he needs to get started for the hit count bp 19:07:23 Based on conversations in the Summit he is good to get started 19:07:26 for starters he needs to file a gerrit spec so that we are all aligned in terms of what we want to do 19:07:31 on the other stuff 19:07:32 SridarK: good 19:07:36 not hit count 19:07:41 SridarK: ah ok 19:07:58 SridarK: perhaps he can join next meeting? 19:08:01 SumitNaiksatam: i think their priority is to get the basic usage stats down 19:08:08 SumitNaiksatam: i will remind him 19:08:14 SridarK: that sounds like a good start 19:08:40 SumitNaiksatam: as they have nothing right now and this was echoed in their Design session as well 19:08:49 SridarK: good 19:10:04 #topic Vendor blueprints 19:10:13 is Karthik here? 19:10:37 ok hopefully he will join next week as well 19:11:35 so can you all add the vendor blueprints as topics on the table as well? 19:11:44 SumitNaiksatam: yes will do 19:11:47 SridarK: thanks 19:11:52 Ok 19:12:22 things that we dont add to the table will fall off the radar and most likely not make it 19:12:25 beyounn_1: thanks 19:12:31 #open discussion 19:12:44 #topic open discussion 19:12:56 Sumit, how to get the bp spec approved? 19:13:01 beyounn_1: :-) 19:13:14 beyounn_1: you mean the service objects? 19:13:17 Yes 19:13:18 beyounn_1: i added some comments to ur review 19:13:25 Saw it 19:13:28 I will updated 19:13:33 s/updated/update/ 19:13:46 beyounn_1: our best chance is as a team 19:14:02 beyounn_1: we can do the internal reviews and get the +1 first to push for cores as Sumit mentioned in the prev mtg 19:14:15 beyounn_1: i mean we all review each other’s blueprints and provide enough information for cores to act on this 19:14:21 yeah like SridarK said 19:14:27 Ok, let's clean up my spec ASAP 19:14:37 SumitNaiksatam: which was really like u said :-) 19:14:38 s/let's/let me/ 19:14:46 beyounn_1: any chance that you can get your potential “users” to look at this as well? 19:14:49 SridarK: :-) 19:14:57 my comment is in general 19:15:11 SumitNaiksatam: don't think so 19:15:17 i would strongly suggest that we involve potential users in this, and let them drive the requirements 19:15:26 beyounn_1: ah, ok 19:15:49 SumitNaiksatam: but I will try, harmless anyway 19:15:57 it becomes much easier to prioritize when its requirements driven 19:16:06 beyounn_1: i think its critical 19:16:18 SumitNaiksatam: agreed 19:16:20 SumitNaiksatam: also perhaps some folks filing bugs now are potential users 19:16:40 SridarK: yes, reach out to them :-) 19:17:03 yes will do 19:17:14 in general, the more people we get to do meaningful reviews, the better our chances 19:17:44 it was mentioned during the summit discussions that meaningful +1s also carry a lot of weight 19:18:07 ok what else? 19:18:20 I'm good 19:18:25 SumitNaiksatam: thats all from me as well 19:18:40 great, thanks eveyrone, it was great meeting you in Atlanta 19:18:49 onward to Juno! ;-) 19:18:51 :-) 19:18:54 yes sam here 19:18:56 see you next week, bye 19:18:57 same 19:18:59 bye 19:19:01 #endmeeting