04:00:11 <njohnston> #startmeeting fwaas
04:00:12 <openstack> Meeting started Wed Aug 31 04:00:11 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:16 <openstack> The meeting name has been set to 'fwaas'
04:00:20 <njohnston> Hi everyone!
04:00:27 <yushiro> Hi all!
04:00:27 <njohnston> #chair SridarK_ xgerman yushiro
04:00:27 <openstack> Current chairs: SridarK_ njohnston xgerman yushiro
04:00:45 <yushiro> njohnston: thanks
04:00:51 <SridarK_> Hi All - we can try to run thru quickly as we are almost there
04:01:07 <njohnston> SridarK_: The floor is yours.
04:01:16 <SridarK_> firstly thanks to everyone to pull together to get a whole hunk of things merged
04:01:20 <SridarK_> njohnston: thx
04:02:10 <SridarK_> #topic FWaaS v2 - L3 Agent extension refactor
04:02:21 <SridarK_> njohnston: pls go ahead
04:02:47 <njohnston> #link https://review.openstack.org/#/c/355576/ FWaaS L3 agent patch
04:03:02 <njohnston> So here is what we have been working on - mainly SridarK this evening
04:03:12 <njohnston> with much support from chandanc_ during the day
04:03:27 <njohnston> At this point, we have determined that the L3 agent is loading the FWaaS extension
04:03:35 <chandanc_> +1
04:03:43 <SridarK_> +1
04:03:57 <SridarK_> i can see the __init__ of the right class
04:04:02 <SridarK_> that is greate
04:04:05 <SridarK_> *great
04:04:57 <njohnston> But the FWaaS agent extension is not receiving the firewall rule and firewall group updates
04:04:58 <njohnston> After going back to the drawing board, we figured out that the reason for this is because there were not specific mechanisms set aside to forward them from the L3 agent
04:05:40 <njohnston> Previously we didn't need to worry about this; because FWaaS managed to be both ancestor and descendant L3NATagent class so the FWaaS code was in charge and was listening to whatever we wanted.
04:06:04 <njohnston> So the idea on the table is this
04:06:37 <njohnston> 1. Change the RPC topic for firewall_* updates coming from neutron server to l3 agent to something like 'L3_FWAAS'
04:07:41 <njohnston> 2. Add code to the initialization of the FWaaS agent extension that subscribes to that RPC topic.  After all it is still in the same running executable as the L3 agent, it's just a separate object.  But it still has access to that facility.
04:08:21 <njohnston> then we can see firewall_* updates coming in through that facility, but we will also see the regular router status updates coming in via the l3 agent extension
04:08:32 <SridarK_> +1
04:08:37 <njohnston> SridarK_ has been working on some POC code, as has mfranc213
04:08:45 <njohnston> SridarK_: Did that pretty well cover it?
04:08:56 <SridarK_> yes absolutely njohnston
04:09:00 <SarathMekala> Sounds good +1
04:09:01 <chandanc_> ok got it
04:09:16 <SridarK_> so interestingly, (1) is simple enough
04:09:35 <SridarK_> and (2) as well - but at some point the brain plays tricks on u :-)
04:09:51 <chandanc_> :) +1
04:10:10 <SridarK_> thx to mfranc213 for looking over my shoulder - just need to debug this a bit
04:11:05 <SridarK_> chandanc_: may be we can continue as it is really late for njohnston & mfranc213
04:11:18 <chandanc_> sure
04:11:26 <SridarK_> i think once we have this in we are good
04:11:36 <chandanc_> ya
04:12:12 <SridarK_> njohnston: anything else u want to add on this
04:13:50 <SridarK_> njohnston: also #link https://review.openstack.org/#/c/357503 (the neutron piece) is almost ready to get in
04:14:52 <yushiro> njohnston, SridarK_ : on L3, are you going to implement (1)?
04:15:13 <SridarK_> yushiro: yes just testing that
04:15:29 <SridarK_> (1) as such is just changing the topic
04:16:28 <SridarK_> ok if nothing else lets move on
04:16:46 <SridarK_> lets come back to it in open discussion
04:17:00 <chandanc_> SridarK_, does it me we will need change to the fwaas plugin for the RPC topic ?
04:17:01 <njohnston> Nope
04:17:02 <njohnston> Shall we talk about the other patches in motion?
04:17:02 <njohnston> #topic Other patches
04:17:38 <njohnston> OK, that's wierd, I got nothing for a long time, then my program crashed and it sent the things from when I heard nothing
04:17:57 <SridarK_> njohnston: ok - i was awaiting a response from u
04:18:15 <SridarK_> and began to sense that something odd was going with ur connectivity
04:18:26 <chandanc_> IRC is non responsive :(
04:18:32 <njohnston> So yes, https://review.openstack.org/#/c/357503 has one +2, just waiting for another one
04:18:52 <SridarK_> hopefully we will get that in soon tomorrow
04:19:00 <njohnston> and the other patch that I think is getting a lot of attention right now is yushiro's client patch
04:19:16 <SridarK_> yes lets get to that
04:19:17 <njohnston> #link https://review.openstack.org/#/c/351582/ client patch
04:19:27 <yushiro> njohnston: Yes. I updated yesterday midnight.
04:20:15 <SridarK_> yushiro: i started looking too - i think u just need the Jenkins failure to be addressed
04:20:41 <njohnston> I agree, I was looking at the jenkins failures since that looks like the main thing in the way
04:21:00 <yushiro> SridarK_: Yes. However, UT is not completed..
04:21:09 <SridarK_> yushiro: oh ok
04:21:23 <njohnston> ah
04:21:25 <SridarK_> yushiro: will u be done soon
04:21:36 <SridarK_> i think tomorrow is the last day
04:22:25 <SridarK_> Since Akihiro is looking at it - i am hoping once we are good - it will go thru quickly
04:22:28 <yushiro> Yes, so I need help to review and UTs.
04:22:34 <SridarK_> could u pls be in sync with him as well
04:22:55 <yushiro> SridarK_: yes, I'll do it after finishing this meeting.
04:23:01 <njohnston> yushiro: Would you like help debugging the UTs, or are they still under construction?
04:24:20 <yushiro> njohnston: hmm, I think they are debugging UTs.
04:24:35 <njohnston> ok
04:24:52 <yushiro> And now, I got up early and trying to fix UTs.
04:26:03 <njohnston> The other patch that is needed is the policy.json changes, which I don't think have gotten a lot of attention.  But they are the required complement to the client patch
04:26:11 <njohnston> #link https://review.openstack.org/#/c/355755/ policy.json patch
04:26:24 <njohnston> I'll see if I can drum up reviews for this tomorrow
04:26:41 <SridarK_> njohnston: yes, i think that looked to be straightfwd
04:27:17 <SridarK_> i think these are the critical ones we are looking at
04:27:27 <yushiro> OK.  Thanks.
04:27:29 <SridarK_> for tomorrow
04:28:10 <SridarK_> On L2, i think a good chunk of the work is done from the FWaaS perspective
04:28:36 <SridarK_> we will still need to move fwd on the neutron side patches for peaceful coexistence with SG
04:28:46 <chandanc_> yes
04:29:24 <SridarK_> we discussed this earlier and felt it is a stretch and we would rather invest time in testing out and fixing L3 related issues
04:29:53 <SridarK_> rather than get the patches in and leave it disabled etc
04:30:37 <SridarK_> njohnston: were there any other patches we needed discussion on
04:31:06 <njohnston> No, I don't think so
04:31:13 <SridarK_> ok lets move on
04:31:21 <SridarK_> #topic Open Discussion
04:31:54 <SridarK_> if there are things to discuss we can do that or we can get back to debugging
04:32:07 * njohnston has nothing else
04:32:17 <chandanc_> +1 debugging
04:32:38 <SridarK_> ok then lets call it a wrap, we can continue on openstack-fwaas
04:32:45 <chandanc_> sure
04:32:46 <SridarK_> thanks all again
04:32:47 <njohnston> thanks all!
04:32:51 <chandanc_> thanks all
04:32:52 <yushiro> thanks
04:32:57 <njohnston> #endmeeting