18:32:56 #startmeeting Networking FWaaS 18:32:56 Meeting started Wed Jul 16 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:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:33:01 The meeting name has been set to 'networking_fwaas' 18:33:04 #info agenda https://wiki.openstack.org/wiki/Meetings/FWaaS 18:33:15 #topic Action Item follow up 18:33:38 the pending action item was to set up a meeting with the DVR folks 18:34:06 thanks SridarK for leading on this, i believe we had two meetings with the DVR team, and we are making good progress 18:34:22 hi 18:34:24 we will get to that specific topic in the DVR related update 18:34:33 SumitNaiksatam: no worries - spec is out - and thanks to Yi & badveli_ as well 18:34:38 lets jump to that 18:34:47 #topic DVR discussion 18:35:16 #link https://review.openstack.org/106225 18:35:32 thanks SridarK badveli_ and yisun for getting posted 18:35:46 SumitNaiksatam: will address ur comment and reflect the minor changes suggested by DVR team 18:35:56 thanks to swami as well for his support and being the liason on the DVR side 18:36:02 SridarK: great 18:36:22 another procedural matter, we need to make sure that this gets discussed in the L3 team meeting as well 18:36:33 the one that is tomorrow 18:36:38 i will send out an email 18:36:54 beyounn: you will be attending that meeting? 18:37:11 I have a conflict meeting 18:37:21 ok, SridarK badveli_? 18:37:22 Wed morning 8:00 is not good for me 18:37:24 SumitNaiksatam: i can attend 18:37:28 yes 18:37:33 SridarK badveli_: nice 18:37:35 i will attend 18:38:08 #action SumitNaiksatam to inform Swami to bring up the FWaaS support proposal in the L3 team meeting 18:38:18 badveli_: you can also help on the implementation, right? 18:38:26 yes 18:38:39 badveli_: nice 18:38:58 SridarK: can you summarize today morning’s discussion for everyone’s benefit here? 18:39:06 SridarK: sorry to put you on the spot 18:39:08 SumitNaiksatam: sure 18:39:22 We will cover N - S usecase 18:39:27 i dont think yapeng is here 18:39:35 We will not break E -W usecases 18:39:54 Target FW rules on the SNAT namespace on network Node 18:40:11 Target FW rules on FIP/IR namespace on the Compute Nodes 18:40:58 We will not try to optimize FW rules for distribution 18:41:08 Focus on correctness 18:41:14 ok that is the rough summary 18:42:22 SridarK: so for FIP, we decided to apply in the IR namespace, right? 18:42:53 SumitNaiksatam: i think Swami's suggestion was to keep that open but yes we will target IR namespace 18:44:04 SumitNaiksatam: mainly for the purposes of the spec but initial attempt is to get it on the IR NS with a tag for traffic on the interface associated with the FIP NS 18:44:14 SridarK: wasnt the suggestion to keep the specifics of the interface names open? 18:44:28 SumitNaiksatam: that as well 18:44:32 SridarK: but we agreed on the IR namespace 18:44:36 SridarK: ah ok 18:44:47 is garyduan here? 18:45:06 SumitNaiksatam: yes but just for now to name it as FIP/IR NS to give us some options just in case ... 18:45:56 Gary is in meeting until now 18:46:08 SridarK: okay 18:46:18 Sorry, he is still in meeting 18:46:24 beyounn: i wanted to check with garyduan if he is comfortable with the approach we are taking 18:46:48 natarajk: have you looked at the proposal? 18:47:11 yes 18:47:17 Sumit: I had a quick chat with him, he is fine 18:47:27 I have been reviewing the DVR FWaas spec udpate 18:47:36 beyounn natarajk: ok 18:48:27 there was also a suggestion from swami for a f2f meeting 18:48:36 i believe after july 25th 18:48:58 lets discuss that offline and decide on date 18:49:12 SumitNaiksatam: +1 - i think that will be useful 18:49:59 so on this topic, our first focus has to be get the spec approved 18:50:50 SridarK badveli_: perhaps good to attempt a DVR installation with the links that were sent out earlier 18:51:12 fine sumit 18:51:18 SumitNaiksatam: Will get the updates in and reach out to FWaaS, DVR team and cores for review by late afternoon 18:51:41 SumitNaiksatam: will try that - badveli_ and i can sync up on this 18:52:07 SridarK badveli_: thanks! 18:52:19 is there anything else we need to discuss on this? 18:52:30 no worries, i think i am good 18:52:41 SridarK: thanks 18:52:55 #topic Service Objects 18:52:55 we need to figure out the fip interface 18:53:20 sorry, will send out a mail on fip interface after testing 18:53:25 please continue 18:54:04 #link https://review.openstack.org/94133 18:54:21 beyounn: there? 18:54:33 yes, he is in a meeting 18:54:45 okay, i have +2’ed the patch 18:54:51 thanks sumit 18:55:02 we need to reach out to nachi, kyle and akihiro 18:55:40 Sumit: Gary sent eamil to akihiro. I will reach out nachi and kyle after my current meeting 18:55:48 beyounn: nice 18:55:53 beyounn: any blockers for you? 18:56:23 hop, I'm real good now 18:56:39 And thanks everyone for the helps !!!!!! 18:57:16 ok moving on 18:57:26 #topic flavors support 18:57:36 i wanted to garyduan’s opinion on this 18:58:19 salvatore has asked a question on the flavor’s spec whether it is feasible for implementation in the juno time frame if the spec is approved 18:58:29 of course this depends on what gets approved 18:58:32 SumitNaiksatam: by the looks of the discussion i wonder if we will be able to move to this 18:58:44 SridarK: okay 18:59:02 but i would like garyduan to respond to that question in the review 18:59:05 even if it gets approved - our time line will be quite tight i guess 19:00:26 SridarK: however garyduan really wanted this to land to enable vendor driver support 19:00:31 SumitNaiksatam: but if it gets delayed we will be asking the same question in K 19:00:38 SumitNaiksatam: my fear 19:00:46 beyounn badveli_: can you please convey to garyduan my earlier request? 19:01:07 yes i will talk to him 19:01:23 badveli_: ok thanks this has to be done today 19:01:36 ok, will talk to him 19:02:24 #action garyduan to respond to salvatore’s question on implementation feasiblity in #link https://review.openstack.org/#/c/102723/ 19:02:40 #topic Bugs 19:03:45 Hi, I am back. Sorry about that. 19:03:45 enikanorov_: has assigned one of the new bugs to himself 19:03:55 SridarK: link? 19:04:15 garyduan: hopefully you can scroll to the discussion earlier on flavors 19:04:28 #link https://bugs.launchpad.net/neutron/+bug/1340735 19:05:01 another issue on tempest: #link https://bugs.launchpad.net/tempest/+bug/1342516 - review is out 19:05:14 those i believe were the new bugs for this week 19:05:23 i dont think we can do anything about #link https://bugs.launchpad.net/neutron/+bug/1340735 19:05:55 since we are at the mercy of the l3 agent kicking in for the firewall deletion 19:06:00 yes 19:06:09 another old one: 19:06:15 #link https://bugs.launchpad.net/neutron/+bug/1310857 19:06:24 SridarK: enikanorov_ might have assigned it to himself for triaging purposes 19:06:43 SumitNaiksatam: yes i think so too 19:06:44 SridarK: he probably does not intend to implement it 19:06:55 SridarK: i will comment on the bug report 19:07:01 ok cool 19:07:25 #link https://review.openstack.org/#/c/90575/ for #link https://bugs.launchpad.net/neutron/+bug/1310857 19:07:28 sridark info how do you look at the bugs assigned in fwaas, is there any link that you have created 19:07:33 i think we are good 19:07:46 on that needs mark to chime in on his comment 19:08:01 sridark or are we search it 19:08:02 badveli_: i have posted a link on the wiki 19:08:29 sumit:new bugs filed that are coming 19:08:35 badveli_: the link is #link https://bugs.launchpad.net/openstack/+bugs?field.searchtext=fwaas&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package 19:08:53 this gives everything related to FWaaS across all the projects 19:08:58 thanks sumit 19:09:01 SridarK: on https://bugs.launchpad.net/tempest/+bug/1342516 19:09:48 its probably not specific to fwaas right? 19:09:53 nothing really specific to us 19:09:53 yes 19:10:06 just lands up on our radar 19:10:11 because of fwaas string 19:10:25 its probably just the case that in this example it shows up with the fwaas test 19:10:27 yeah 19:12:28 SridarK: so for #link https://review.openstack.org/#/c/90575/ mark’s comment has been responded to, right? 19:12:34 SumitNaiksatam: yes 19:12:48 thankfully the -2 is not there any more! 19:12:49 the assignee has fixed it 19:12:58 and Mark took out his -2 19:13:05 and now there is a -1 19:13:11 wow, i think that must be a first! 19:13:18 but this looks good 19:13:20 :-) 19:13:35 we are blessed! 19:13:44 I will ping SridharG (the submitter) to reach out 19:13:55 SridarK: thanks much 19:14:02 no worries 19:14:08 anything else on the bugs radar? 19:14:26 SumitNaiksatam: nothing major to report 19:14:52 SridarK: thanks 19:14:58 np at all 19:15:03 #topic Vendor Blueprints 19:15:41 SridarK natarajk: can you add your blueprint specs here: https://wiki.openstack.org/wiki/Meetings/FWaaS#Blueprint_Tracking 19:16:01 sure 19:16:04 SumitNaiksatam: will do 19:16:08 natarajk SridarK: thanks 19:16:16 SridarK: link to your bp? 19:16:25 SumitNaiksatam: #link #link https://review.openstack.org/#/c/105373/ 19:16:31 SridarK: thanks 19:16:50 SridarK: so we have a dependency here on Bob’s patch? 19:16:51 SumitNaiksatam: also the dependency that i was waiting on just got approved 2 mins ago 19:17:15 SridarK: oh good 19:17:21 SridarK: i can look at it then 19:17:23 SumitNaiksatam: so we are good on the dependency - i will respond to Kyle's -1 and hopefully we will get this moving 19:17:30 SumitNaiksatam: thanks much for ur help on this 19:17:44 SridarK: actually kyle removed his -1 19:17:52 aah great 19:18:32 ok i just seer that too 19:18:36 *see 19:18:43 natarajk: link to your blueprint spec? 19:18:49 we are on real time 19:19:11 Sumit, i am still going through l3 plugin review 19:19:18 natarajk: ah ok 19:19:39 I'll submit the spec, but i am also waiting for flavors framework 19:19:58 natarajk: ok 19:20:19 natarajk: i believe its too late now to submit a new blueprint spec 19:20:31 natarajk: that dealine was on july 10th 19:20:43 Sumit, my focus has been to get the l3 spec and code approved 19:20:46 the spec approval deadline is July 20th 19:20:56 natarajk: sure, sounds like the right priority 19:21:11 i was earlier misreporting the SAD to be july 17th 19:21:41 that means that we have a couple of more days than we expected 19:21:48 so its a good thing 19:22:36 anything else on the vendor blueprints 19:22:37 ? 19:22:43 if l3 code get approved, i can work on firewall plugin (if vendor extensions or flavor is accepted by the community) 19:22:59 natarajk: sure, that i believe will be for K release then 19:23:10 Sumit, yes 19:23:16 natarajk: good 19:24:18 #topic open discussion 19:24:39 SumitNaiksatam: will also reach out to s3wong on plans for service insertion 19:24:50 SridarK: yeah sure, thanks 19:25:00 SumitNaiksatam: will be great if we can get that in 19:25:17 SridarK: yeah! its very frustrating 19:25:56 SumitNaiksatam: the third time is a charm so lets hope that works :-( 19:26:19 SridarK: yeah! 19:26:36 garyduan: so you will respond on the flavors review? 19:27:27 yes 19:27:49 I will add my comment to the spec 19:28:11 garyduan: thanks 19:28:27 okay, if nothing else, lets call it a wrap 19:28:37 thanks everynone for attending, bye! 19:28:45 thanks 19:28:47 bye 19:28:49 bye 19:28:50 not to forget that we have immediate work to do on the DVR front 19:28:55 #endmeeting