18:30:17 #startmeeting networking_fwaas 18:30:17 Meeting started Wed Mar 30 18:30:17 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:30:21 The meeting name has been set to 'networking_fwaas' 18:30:23 #chair SridarK 18:30:24 Current chairs: SridarK sc68cal 18:30:24 Hi All 18:30:29 #chair xgerman 18:30:30 Current chairs: SridarK sc68cal xgerman 18:31:50 The status for me - pretty much the same. Haven't been able to focus on fwaas. I fear it's become the new normal 18:32:52 Some quick updates on Observer Hierarchy 18:33:07 #link https://review.openstack.org/#/c/278863/ 18:33:17 I have been working with the submitter 18:33:35 i have some comments but i think we are making progress 18:34:40 we may need to do some rework on how we handle the notifications 18:34:54 perfect. getting that work done would be very good, since we can decouple from the neutron l3 agent 18:35:06 I think we will continue to push to get this in next couple of weeks 18:35:37 excellent 18:36:07 Some other updates on vendor decomp 18:36:40 vArmour - the prime contact is out and said he will reach out next week for a discussion 18:37:15 vyatta - in conversation - dont have a final thing to report back 18:38:01 SridarK: thank you for reaching out to these groups 18:38:06 cisco - we can get it out - as we have already moved out the L3 implementation - so this is not a problem - we will target by N2 just to make sure if any documentation is needed 18:38:20 sc68cal: no worries - so we should be cleaned up 18:38:28 this cycle 18:38:44 I suppose what concerns me is the fact that we don't know off the top of our heads what the status of these drivers are, by their respective companies 18:39:10 we are basically the maintainers of code that may or may not be a priority for any of these companies 18:39:20 sc68cal: yes agreed - it is likely that there is some outside implementation existing as well 18:39:57 We're all in agreement that the v1 API and driver API is not going to undergo any change, perhaps ever again 18:40:12 sc68cal: yes 18:40:14 so sure, people can develop drivers for it, we'll honor that contract 18:40:23 +1 18:40:41 but these drivers in our tree - can be moved into big tent repos that each company has, or could have 18:40:51 +1 18:40:51 and they can control their own destiny 18:41:21 +1 it is much easier from the vendor perspective too 18:42:55 anything else to discuss? 18:43:08 design sessions? 18:43:27 should we ask for one and if so how (other than the ether pad) 18:44:17 i think the session or discussion regarding iptables that xgerman: added would be good 18:45:04 xgerman: good u added that given that having a clean i/f and not stepping other features is imp 18:45:31 yeah, I got some pushback to rather use the ML 18:45:50 but will try to work our contacts 18:46:30 yes agreed - a quick whiteboard discussion could be fruitful for mickeys 18:47:52 If we need design summit sessions, is armax who to contact? 18:48:11 yes 18:48:19 unless he delegated that -- 18:48:29 we can also ask dougwig to lobby own our behalf 18:49:14 ok. Let's try and give them a firm idea of what we need quickly so we don't make them scramble 18:49:26 my sense is that we may need some fwaas specific discussions across the contributors anyways 18:49:42 from the broader audience - perhaps iptables interactions is the key thing 18:50:11 Also while on this, what needs to be done with the v2 spec - do we just carry that forward 18:50:30 i mean in terms of approvals etc 18:51:41 yeah, I think we carry forward 18:51:54 ok 18:52:25 unless we learn new things at the summit which would make us change it 18:52:59 there might be some new projects we can leverage… though I doubt it 18:53:09 ok may be we can freeze on what we have and keep that as the target for N 18:55:26 that makes sense 18:55:35 +1 18:57:32 I have to head out in a couple minutes 18:57:42 ok, I think we are done anyway 18:57:55 yes i did not have much more to add either 18:58:06 #endmeeting