18:31:18 #startmeeting Networking FWaaS 18:31:19 Meeting started Wed Dec 3 18:31:18 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:31:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:31:23 The meeting name has been set to 'networking_fwaas' 18:31:34 #info SPD: Monday 12-8-2014 SAD: Monday 12-15-2014 18:31:54 #info Kilo-1 is 12-18-2014 18:32:17 any other related announcements anyone would like to share for the benefit of the team? 18:32:51 #topic Bugs 18:33:11 SumitNaiksatam: nothing new 18:33:32 SridarK: yes 18:33:51 i did a quick review on this: #link https://review.openstack.org/#/c/104132/ 18:33:58 hi 18:34:20 Swami: hi 18:34:45 SumitNaiksatam: yes u beat me to it - i was trying to understand when i saw ur review go by :-) 18:34:55 Swami: hi 18:35:12 SridarK: ah ok, do you disagree with the change? 18:35:16 SumitNaiksatam: seems fairly straight forward 18:35:36 SumitNaiksatam: no was just trying compare the change with the original 18:35:46 SumitNaiksatam: it is good 18:35:53 SridarK: i thought the change was trying to make things consistent 18:36:01 SumitNaiksatam: yes 18:36:04 i however did not have a chance to actually test it out 18:36:16 it would be nice if some actually can 18:36:29 SumitNaiksatam: i will try to get to this later today 18:36:35 SridarK: sweet 18:36:53 i guess we are missing badveli not sure if anything showed up on his bug triage radar 18:37:09 #topic Docs 18:37:23 i guess we have three pending items here 18:37:44 SumitNaiksatam: yes - i could not even look at any of this trying to get specs out 18:37:44 Swami: anything for us to review or contribute in terms of DVR? 18:38:08 SridarK: np, that definitely is high priority too 18:38:45 SumitNaiksatam: I have created a document for the documentation folks to consume. 18:39:01 I have added a section for the services and added a high level note for all the services. 18:39:06 #link https://docs.google.com/document/d/1qmKoP4GVdjeEEVvqf3tYptVuvUzVIeQmJiTPWPoi_E0/edit 18:39:31 If you can take a look at the services part and if you feel like I have missed anything please fill in the gap. 18:40:02 I am working with "Elke Vorgheise" on the documentation. I think she is the tech writer for the networking guide. 18:40:10 Swami: ah ok 18:40:17 thanks for the link 18:41:26 Swami: thx - overview on services covers major points - will see if we need to add any more details 18:41:29 Swami: perhaps we need to add some notes on the migration to the legacy mode (or the lack of when using FWaaS) 18:41:58 Swami: over the the quick scan of the doc for DVR - looks really good and comprehensive 18:42:00 but the team here can this a little more detailed read, and provide feedback 18:42:12 SridarK: +1, great job Swami! 18:42:24 Yes, we can add a section on migration and how the services are handled. 18:42:41 I will take a first stab at it and you can add your feedback or data to this document. 18:42:52 Swami: i see a book deal coming :-) Swami signing DVR books at Vancouver :-) 18:42:56 SumitNaiksatam: sure. 18:43:11 lol! 18:43:34 SridarK: Sure, I like the idea. 18:43:38 Swami: also, conf is missing, not sure that is meant for this document thought 18:43:41 :-) 18:44:00 SumitNaiksatam: When you say config, are you talking about multinode config or single node config. 18:44:29 I think I had a section on configuration that deals with the DVR specific configurations. 18:44:32 yeah, and specifically in the context of FWaaS what needs to be set on which node 18:45:10 i dont think that is terribly different from the DVR base configuration, but i vaguely recall that we had one or two extra things in there 18:45:19 just need to confirm 18:45:22 SumitNaiksatam: i don't think we need to set anything specific for FWaaS 18:45:33 SridarK: okay 18:45:41 For DVR there is no specific action that is required for Firewall configuration. As far as the firewall service is enabled, it should work. 18:46:03 FWaaS just looks at the 'distributed' flag 18:46:03 next doc item - #link https://bugs.launchpad.net/openstack-manuals/+bug/1373674 18:46:12 SridarK: okay 18:46:48 i am not sure if we need address the “openstack-api-site” related documentation 18:47:20 third doc item was: #link https://bugs.launchpad.net/openstack-manuals/+bug/1346986 18:47:31 i believe there isnt an update on this 18:47:41 SumitNaiksatam: not sure on that the second one - but i recall last week we saw that it was fixed 18:48:03 SridarK: it was fixed in one of the documents but it shows open in the other 18:48:15 SumitNaiksatam: hmm ok 18:48:20 sorry missed that 18:48:34 SridarK: if this doesnt swap out of my memory i will try to ping the guy :-) 18:48:42 #topic Kilo Blueprints 18:48:56 we have to post the blueprints by Dec 8th 18:49:06 SumitNaiksatam: badveli just sent an email - he is running late 18:49:33 SridarK: thanks, yeah i saw that earlier, was hoping he would make it 18:49:46 make it before we get to security groups 18:49:54 *service groups 18:50:02 what do you mean by "post the blueprints by Dec 8th"? 18:50:04 SumitNaiksatam, SridarK: I will upload a patch later today to address your comments 18:50:07 I pushed some comments out on service groups a little early today 18:50:08 commute is bad today! 18:50:48 RuiZang: i meant post a gerrit spec for review; i think you are good since you already posted your blueprint 18:50:52 vishwanathj: sure, np 18:51:00 SridarK: nice, i did not notice that 18:51:07 SumitNaiksatam: mostly nits on service groups 18:51:07 so lets take one bp at a time 18:51:31 SumitNaiksatam: oops sorry - are we on service groups ? 18:51:40 SumitNaiksatam> Oh OK 18:52:00 lets start with hot spec of the day - FWaaS Insertion Model on a Single Router - #link https://review.openstack.org/#/c/138672/ 18:52:10 :-) 18:52:16 SridarK: your baby :-) 18:52:32 SumitNaiksatam: thanks for the comments 18:52:37 hot spec puts you in the hot seat ;-P 18:52:41 :-) 18:52:42 SridarK: sure 18:52:49 probably folks havent had a chance to review it 18:52:58 please do so and provide comments at the earliest 18:53:22 SumitNaiksatam: i think i have tried to capture most of the discussions from the summit and also in the mtgs 18:53:24 this is probably the most important bp/spec for FWaaS for Kilo 18:53:51 SridarK: and very articulated at that! 18:54:07 :-) 18:54:40 hello all 18:54:51 sorry delayed due to weather 18:55:17 I am hoping that if we get most things thrashed out this week - next week can get some core attention 18:55:20 badveli: hi 18:55:28 badveli: yes, glad you could make it, and pretty much at the right time 18:55:28 hello sridark 18:55:35 oh..thanks 18:55:45 SumitNaiksatam: of course thanks of the core attention from u 18:55:52 *for 18:56:08 SridarK: yeah, i would say we pre-emptively approach some of the other cores 18:56:21 SumitNaiksatam: ok sounds good - will do that 18:56:23 SridarK: i think we should add all the cores to the review 18:56:31 SridarK: you want me to do that? 18:56:35 SumitNaiksatam: ok sure 18:56:57 SridarK: ok done :-) 18:57:27 did anyone else get a chance to look at Sridar’s spec? 18:57:36 in case we want to spend a few mins discussing here 18:57:40 SumitNaiksatam: definitely want to thrash out some of the extensions related areas - i have left that a bit open as i am not sure how to proceed there with all the changes 18:57:44 just going through 18:58:04 is glebo here? 18:58:41 no i do not see him here 18:58:44 the next bp is Service group and Service Object for firewall as a service: #link https://review.openstack.org/#/c/131596 18:59:20 badveli: looks like we again have some formatting and grammar nit issues 18:59:32 badveli: i provided some comments earlier today 18:59:34 looking at SridarK’s comment 18:59:38 *comments 18:59:46 ideally we should have been way past this point now 18:59:48 badveli: mostly looks good except for the nits 18:59:49 taking a look 19:00:23 badveli: did you or glebo hear from any of the other cores that glebo had approached to review this? 19:00:37 we did not get anything 19:00:44 we are still waiting 19:00:45 badveli: hmmm 19:01:00 badveli: once you get a new rev out, i will review immediately 19:01:03 badveli: possibly the 2 issues i have listed - if u change the wording on that or clarify and with the nits fixed - i am good 19:01:29 badveli: would appreciate if you can send a headup when you do to the entire team 19:01:40 *headsup 19:01:49 ok 19:02:03 i will give a heads up on the new review 19:02:09 the third bp is regarding FWaaS for E-W traffic when deploying DVR 19:02:14 badveli: thanks 19:02:33 Swami sent out a proposal last week: #link https://docs.google.com/document/d/11Gp62Yfyi1WH6yM6E_308OB4CC9A6xhxKZJ8B5jOwLc/edit 19:02:42 and we had a brief discussion 19:03:07 Swami: have you identified a preferred path in terms of what is feasible on the DVR side of things? 19:03:30 SumitNaiksatam: I was counting on vivek to give me some feedback on proposal 1. 19:03:38 Swami: ah ok 19:03:44 But he was busy on something else. 19:04:06 so i am a bit concerned that we are cutting too close to the SPD, since we dont have a spec in place yet 19:04:18 how do we want to go about pursuing this? 19:04:25 SumitNaiksatam: So I have to take up the task to investigate the pros and cons of option 1> 19:04:25 Option 2: is prety much straight forward and DVR will not have any impact. 19:04:43 But I personnally like option1 since the firewall rules will be in one single place. 19:05:07 yes swami, i think option 1 is looking good 19:05:10 we need to firm on both - (1) the technical path that we want to take, and (2) the logisitics of who will post the spec 19:05:19 Did you guys do a round table discussion on both options? If so what do you like or see as a valuable going forward. 19:05:53 on (2) we need to decide whether we need 2 specs (one for DVR and another for FWaaS) or 1 19:06:21 Swami: a meeting dedicated to this would definitely be helpful, lets take that offline and set up one for the earliest 19:06:41 SumitNaiksatam: Swami: Yes i think that will be good 19:06:45 In either case, if we choose either of the options mentioned above, this addition of a new bridge or addition of a new rule to redirect the packets to the router should only happen if there is a firewall enabled. 19:06:50 #action SumitNaiksatam to setup DVR E-W traffic discussion meeting 19:07:09 Swami: so seems like we are shooting for two specs? 19:07:10 SumitNaiksatam: Yes I agree with you on having a separate chat on this. 19:07:56 SumitNaiksatam: No at this point let us keep the implementation decision out of the spec. 19:08:18 Let us file a blueprint of applying the firewall rules for the DVR East-West. 19:08:36 I don't think we are going to introduce any API change at this time or any database change for this feature. 19:09:11 Swami: A sort of tangential but related question 19:09:15 Swami: okay lets discuss further in the meeting 19:09:35 to me it lloked like option 1 is better 19:09:36 Yes sounds good. 19:09:46 Swami: do you think Vivek needs to attend the meeting or you would sync up offline with him? (that will help to set the time for the meeting) 19:09:54 badveli: Swami: yes i agree 19:10:10 Swami: With DVR is there some significance for an interface that carries the E -W traffic ? 19:10:26 thanks sumit 19:10:27 SumitNaiksatam: Yes I will investigate it further and if we need viveks help we can pull in as required. He seems to busy in some other work. 19:11:06 Swami: or is the interface just a logical entity and we cannot discriminate or associate E - W traffic with a specific Router interface ? 19:11:10 Swami: okay some i am shooting for 9 AM PST tomorrow (if that works for everyone) 19:11:31 SridarK: I don't think there is any significane on interface that is driving traffic for E-W. But we can easily sort out there are different ports that direct traffic for North-South and for East-West. 19:11:31 19:11:59 Tomorrow 9 a.m should work. 19:12:08 19:12:28 sumit, can we do a bit late 19:12:31 9AM PST works 19:12:35 Swami: ok lets discuss more on this, i am trying to think in terms of the router insertion work that we are planning to see if we can leverage that for handling this case 19:13:20 SumitNaiksatam: i am okay with any time in the morning 19:13:25 SridarK: Yes we can discuss this in futher details in the meeting tomorrow. 19:14:04 okay i will send out an invite accordingly 19:14:18 next vendor blueprints 19:14:25 i have a doctor appointment in the morning 19:14:34 badveli: okay lets discuss offline 19:14:39 i will try to attend it 19:15:03 we currently have only one vendor spec posted on the wiki: #link https://wiki.openstack.org/wiki/Meetings/FWaaS#Vendor_Blueprints 19:15:12 #link https://review.openstack.org/#/c/129836/ 19:15:13 however we have at least a couple of more 19:15:30 SridarK: ah i guess we need to update the link 19:15:33 Do I have to post the review on wiki by myself? 19:15:37 SumitNaiksatam: ok will do 19:15:40 vishwanathj: RuiZang: can you update the wiki page 19:15:40 Sorry, I am totallynew to this 19:15:52 Sure, I can 19:15:57 RuiZang: no worries, it wil be great if you can update the wiki 19:16:01 SumitNaiksatam, will update 19:16:29 RuiZang: this not a required step, its a nice to have since it will be visible to other FWaaS team member for ready reference and they can provide reviews 19:16:29 RuiZang: pls feel free to reach out if u have any questions 19:16:37 we will also track every week 19:16:55 RuiZang: i did a quick read through, and provided a couple of high level comments 19:17:01 RuiZang: but mostly looks good to me 19:17:04 SumitNaikstam: Sridark: thanks you guys, I will update the wiki 19:17:26 RuiZang: are you the one shepherding this spec or is it isaku? 19:17:42 Isaku is on relocation to U.S 19:17:46 RuiZang: sorry, i know you have two specs 19:17:50 So currently it is me 19:17:58 RuiZang: i was referring to the first one, which is the L3 plugin 19:18:09 RuiZang: i have not yet read through the fwaas driver 19:18:29 SumitNaiksatam: yes I am responsible for both of them 19:18:33 RuiZang: great 19:18:54 RuiZang: as SridarK mentioned please feel free to reach out to this team if you need any help 19:19:03 vishwanathj: any blockers for your spec? 19:19:27 SumitNaiksatam: Sridark: Sure, thanks very much 19:19:54 SumitNaiksatam, None at this time, I need to upload the next patch set addressing SridarK and your comments 19:20:02 vishwanathj: ok great 19:20:28 btw, Spec for introducing Brocade Vyatta Firewall solution using a new vendor specific device driver for Neutron L3 agent: #link https://review.openstack.org/136953 19:21:03 and Ruiz’s specs are: l3-router: add mcafee ngfw l3 router plugin #link https://review.openstack.org/134198 19:21:05 SumitNaiksatam, I have updated the wiki and added link to brocade vyatta firewall spec 19:21:28 and, firewall: add mcafee ngfw driver support: #link https://review.openstack.org/#/c/91286/ 19:21:39 vishwanathj: nice, thanks! 19:22:07 the other blueprint/work we need to discuss with high priority is the L3 agent refactoring 19:22:17 #topic L3 Agent refactoring 19:23:44 #link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:bp/restructure-l3-agent,n,z 19:23:55 this will affect the firewall agent 19:24:07 so just want to confirm who signed up for this 19:24:16 SridarK: was it you and pc_m? 19:24:26 yup 19:24:36 pc_m: okay great, thanks! 19:24:38 I'm doing VPN 19:24:43 pc_m: ah okay 19:24:54 And have started on the refactoring. 19:24:55 pc_m: who is doing firewall? 19:25:13 I thought SridarK signed up. 19:25:22 pc_m: okay 19:25:50 badveli: i vaguely recall glebo mentioning that you were going to look at this too 19:26:10 pc_m: i am guessing that the scope of this work in the context of fwaas is pretty limited, right? 19:26:27 sumit, i am planning to do the e-w spec side 19:26:41 badveli: ah okay, got it 19:26:51 SumitNaiksatam: yes. 19:26:58 i will get the details from pc_m 19:27:25 SumitNaiksatam: Mostly will be determining the hook points for L3 agent notifications to the services 19:27:39 pc_m: right 19:27:48 19:27:48 i think we lost SridarK for a bit there 19:27:50 sorry network glitch 19:27:53 SumitNaiksatam: And of course, teasing apart the inheritance tree 19:27:55 SridarK: np 19:28:07 #link https://review.openstack.org/#/c/131535 19:28:12 Is the BP spec. 19:28:12 SridarK: we were discussing the l3 agent refactor and its implications for the fwaas agent 19:28:18 pc_m: is there design doc for this hook points 19:28:28 SridarK: trying to nail down who signed up for this at our end 19:28:34 SridarK: did you? 19:28:38 on this L3 refactor, Carl pinged me on the fwaas side to see if i can take a look - so will look into that 19:28:40 Swami: no. There was some discussion on the ML and some info in the BP 19:28:59 SumitNaiksatam: so i have signed up 19:29:04 Please look at the BP spec and comment from a FW POV 19:29:21 * pc_m just check - it's approved 19:29:30 pc_m: yeah, was going to say :-) 19:29:39 Still would give the main points. 19:30:16 so i think we proposed in the adv services’ meeting yesterday we will target this for Kilo-2 19:30:23 ok folks we are out of time 19:30:30 hope we didnt miss anything 19:30:34 thanks for joining 19:30:35 bye! 19:30:39 #endmeeting