18:30:29 #startmeeting networking_fwaas 18:30:30 Meeting started Wed Jan 27 18:30:29 2016 UTC and is due to finish in 60 minutes. The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:30:31 Hi 18:30:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:30:34 The meeting name has been set to 'networking_fwaas' 18:30:43 #chair xgerman SridarK 18:30:44 Current chairs: SridarK sc68cal xgerman 18:30:48 o/ 18:31:36 I've been a little busy with multinode grenade and MTUs this week and haven't had a chance to do any fwaas stuff 18:32:04 SridarK and xgerman - if you guys have anything to drive today's meeting please do 18:32:11 same here - lot’s of internal stuff for me + getting used to versioned objects takes time 18:32:15 o/ 18:32:30 Hi 18:32:30 we need to figure out who does the versioned objects... 18:33:02 I might be able to but will be a while 18:33:12 so if somebody has spare cycles... 18:33:14 i too have been on some internal stuff, but i am beginning to get something basic for fw policy going then i can get a basic fw group methods in 18:33:24 cool 18:33:35 then we can look at the agent communication 18:34:06 yes i have not started looking at the versioned objects either - i need to get a basic fw group standing b4 even getting there 18:34:21 i will try to have something up by end of the week 18:34:30 yeah, they seem like a pain 18:34:42 then we can start discussing the agent interface 18:34:48 so i will keep poking at those then... 18:34:56 yes seems like more understanding is needed on that 18:35:50 will Aish have some cycles to help as well 18:36:23 yep 18:36:44 ok that is good 18:36:46 I will try to loop her in… 18:36:52 great 18:37:29 jwarendts said he will have some CLI patch up soon 18:37:30 sc68cal: i will add some stuff around policy and fw group to the db patch 18:37:37 SridarK: ok 18:37:53 yeah, I think we all will need to chain on that patch 18:38:05 which brings me to our dev startegy 18:38:18 in LBaaS we were running a 8 patch deep chain for V2 18:38:36 alternaticely we can merge things since they don’t do anything (especially DB) 18:39:10 lets defer that decision. 18:39:11 dependency chains are painful… so I would prefer merging whenever possible 18:39:40 sc68cal ok 18:39:40 I don't think we should merge things just for the sake of merging. We'd need to have very good unit test coverage before considering that 18:40:00 well, can we get the DB part to get there? 18:40:04 yes having some things merge make it easier to deal with but i think this is something that is frowned upon to push things without the backend 18:40:28 dependency chains it is ;-) 18:40:36 :-) 18:41:23 I have also been sidetracked by other stuff over the past week, but I have managed to spend some cycles bringing my colleague Sukanya up to speed. She will be helping me out with the firewall driver. 18:41:40 yeah!! 18:41:44 also - please make sure you are setting your topic correctly when pushing patches to gerrit - the -t option of "git review" 18:41:48 oh good that we can add another resource 18:41:59 SridarK: yes, I shall work along with xgerman 18:42:23 We need to focus on changes to Neutron security groups first. Two changes we are looking at. One is singleton for conntrack management, with some restructuring to get all the conntrack stuff under the conntrack manager. 18:43:01 The other one is the jump to the firewall chain. We want to investigate a singleton approach, should be a lot cleaner than a jump from security groups to firewall and sprinkling is_sg_enabled all over the place. 18:43:03 is anyone going to the neutron mid cycle to champion those patches? 18:43:21 (anyone with travel budget:-) 18:43:30 Not planning to 18:43:40 or mickey u can make ur boss a proxy ;-) 18:43:59 Not a bad thought ... 18:44:52 sc68cal: on the topic - it should be fwaas_v2_api correct ? 18:44:57 well, our lt. dougwig should also be working for us there :-) 18:45:00 skath_: yep 18:45:03 SridarK: yep 18:45:14 good thx 18:45:30 For the driver, I put fwaas_v2_driver through the patch, after pushing the first patch set 18:45:36 through the web 18:46:32 I think one of the other patch sets was just fwaas_v2 18:46:47 I am I think I ignored that alltogether 18:48:20 xgerman: Your patch set currently has topic "l2_agent" 18:48:38 Roey's is the one with topic "fwaas_v2" 18:48:38 yep, that’s what I meant... 18:49:02 let's try and fix our topics up - so that we can easily see the whole chain of patches 18:49:23 the easiest thing to do is create a branch in your local git repo - git review uses that for the topic 18:49:30 so ... fwaas_v2_api as your branch 18:49:34 err 18:49:38 fwaas_api_v2 18:49:44 * sc68cal grumbles 18:49:53 ok, will do for future patches 18:50:06 and also chain mine on top of FDB 18:50:11 DB 18:50:19 since I need the versioned objects 18:51:21 i think the dependency chain is like: REST -- DB -- Plugin -- Agent -- Driver 18:51:53 well, then we need another patch 18:52:06 REST-DB-versioned Objects - Plugin -... 18:52:26 sc68cal: has the resource ext patch out i believe 18:53:11 ok so for this versioned obj now will need another patchset ? 18:53:33 or we shoehorn that into the plugin 18:53:43 we can do that too 18:54:09 I just thought if Aish/I work on that an extra patch would be better 18:54:30 thats fine - whichever is easier 18:54:51 I think an extra patch gives us more flexibility 18:55:07 +1 18:57:29 other things to discuss ? 18:57:39 I am good 18:58:14 if no one has other points to discuss we can get some time back 18:58:37 +1 18:58:45 #endmeeting