04:00:15 <njohnston> #startmeeting fwaas
04:00:16 <openstack> Meeting started Wed Oct  5 04:00:15 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:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:20 <openstack> The meeting name has been set to 'fwaas'
04:00:26 <SridarK> Hi All
04:00:26 <njohnston> Hello everybody
04:00:33 <chandanc_> Hello All
04:00:37 <SarathMekala> Hi all O/
04:01:38 <SridarK> shall we get started
04:01:44 <njohnston> by all means :-)
04:01:57 <SridarK> #topic FWaaS v2
04:02:19 <SridarK> njohnston: can u pls add me to chair
04:02:28 <njohnston> oops forgot
04:02:36 <njohnston> #chair SridarK
04:02:37 <openstack> Current chairs: SridarK njohnston
04:02:38 <SridarK> no worries thx
04:02:45 <njohnston> #chair yushiro xgerman
04:02:46 <openstack> Warning: Nick not in channel: yushiro
04:02:47 <openstack> Current chairs: SridarK njohnston xgerman yushiro
04:02:53 <SridarK> #topic FWaaS v2
04:03:39 <SridarK> I think yushiro is out today
04:04:06 <SridarK> and we are done with the CLI discussion, now it is just a matter of getting the review moving when he is back
04:04:19 <SridarK> so lets move on to L2
04:04:35 <SridarK> padkrish may join in late
04:05:02 <SridarK> but he has been working the L2 Agent side of things and has good progress on that
04:05:08 <SridarK> so lets move to the driver
04:05:19 <SridarK> chandanc_: SarathMekala: pls go ahead all yours
04:05:35 <chandanc_> We have been working on the UT for conntrack and l2 driver
04:06:11 <chandanc_> the Conntrack still has 2 more UT breaks but the ideas provided by Nate and Margaret helped
04:06:24 <SridarK> great
04:06:29 <njohnston> You both were working hard - I saw a blizzard of patchsets come in - nice work!
04:06:33 <chandanc_> On the Iptables driver side we had some 100 + UT breakage
04:06:42 <SridarK> ouch
04:06:44 <chandanc_> we could bring it down to 307 now
04:06:52 <chandanc_> 37 *
04:06:56 <chandanc_> sorry
04:07:03 <SridarK> :-)
04:07:20 <chandanc_> should be able to close the iptable UTs quite soon
04:07:29 <chandanc_> but the contrack one seems a hardnut
04:07:46 <SridarK> excellent - then u can push for core attention on the iptables patch
04:08:03 <chandanc_> even with the threading lock we are not able to fix the last 2 UTs
04:08:30 <chandanc_> yes I think now I will ask for Core attention
04:08:46 <njohnston> I can take a look at those 2 last UTs; I am humble but perhaps I can help.
04:09:02 <chandanc_> sure njohnston
04:09:14 <chandanc_> I can use some help
04:10:10 <chandanc_> I will be pinging Kevin this week
04:10:40 <SridarK_> sorry got bounced, chandanc_: if think it will help we can all get together in a mtg tomorrow to do some debugging
04:11:06 <chandanc_> sure that will be helpful
04:11:48 <SarathMekala> +1
04:11:50 <SridarK_> chandanc_: pls send out an email to all of us, to coordinate on a time
04:12:12 <njohnston> +1
04:12:33 <chandanc_> I will send a mail to the team with the meeting time
04:12:43 <SridarK_> we can get some context as well on this to think thru
04:12:44 <chandanc_> BTW what will be a good time for you guys
04:12:51 <SridarK_> great thx chandanc_:
04:12:51 <chandanc_> yes
04:13:39 <SridarK_> I have a mtg at 9am to 9:30am Pacific time - after that i am fine
04:14:02 <njohnston> chandan: for me sometime between 1300 UTC and 2100 UTC
04:14:09 <njohnston> is optimal
04:15:12 <SarathMekala> 1400 UTC then
04:15:27 <SridarK_> sure i can make that work too
04:15:38 <SridarK_> a bit early for me but should be ok
04:15:56 <njohnston> sounds good
04:16:32 <SridarK_> ok lets carry that fwd to the mtg, meanwhile just send out an email with some context and i can set up a conf call
04:16:49 <chandanc_> Sure
04:16:56 <chandanc_> Will send a mail
04:17:22 <SridarK_> we can get to the fwaas piece after the neutron pieces are getting some review traction
04:17:29 <SarathMekala> meeting for today right?
04:17:32 <SridarK_> this is definitely not the long pole
04:17:56 <SridarK_> SarathMekala: yes so that would be 7:30pm for u guys (i think)
04:18:02 <chandanc_> yes
04:18:14 <njohnston> we appreciate you staying late
04:18:39 <chandanc_> 7:30 is not late :)
04:19:01 <njohnston> my wife would have strong opinions if I stayed until 7:30 ;-)
04:19:06 <SridarK_> ok other things on the L2 driver side of things that u would like to discuss ?
04:19:07 <chandanc_> :)
04:19:11 <SridarK_> :-)
04:19:19 <SarathMekala> :)
04:19:25 <SarathMekala> SridarK_, we are ok till 9 pm if its clashing with your meeting
04:19:33 <SridarK_> no this is fine
04:20:10 <SridarK_> i have to convince someone to take the dog out - thats all :-)
04:20:41 <SridarK_> good lets move on, i will send out conf call details
04:20:42 <SarathMekala> :) my dog takes me out around this time
04:20:48 <SridarK_> :-)
04:20:52 <njohnston> :-)
04:21:40 <SridarK_> other things on v2 - i started looking at tempest, but had to take care of some other things at work so been slow
04:21:41 <njohnston> ok, sounds like we can move on
04:21:57 <SridarK_> will get back on track on this - so we can get some basic coverage in
04:22:06 <njohnston> ecellent!  The tempest change looks like it just needs neutron infra +1 and it will merge
04:22:22 <njohnston> #link https://review.openstack.org/#/c/371749/ tempest change
04:23:08 <SridarK_> njohnston: great, so we can just hook our v2 tests to this
04:23:17 <SridarK_> once i get some done
04:23:39 <njohnston> yes, for every change we will get v1 and v2 test results - both non-voting, but still we'll be able to make sure our changes are working on both sides
04:24:07 <SridarK_> njohnston: great
04:24:37 <SridarK_> ok thats about all i had on v2
04:24:46 <SridarK_> njohnston: anything else to cover ?
04:25:08 <njohnston> nothing on v2
04:25:18 <SridarK_> ok we can move on then
04:25:38 <SridarK_> njohnston: i think my alias got morphed, so can u pls drive
04:25:47 <njohnston> sure thing
04:26:00 <SridarK_> this was the main set of things i wanted to discuss mainly
04:26:15 <njohnston> All right, I have a few other items
04:26:21 <njohnston> #topic Ocata
04:26:21 <SridarK_> njohnston: pls go ahead
04:26:39 <njohnston> I don't know how many people we are going to have in Barcelona
04:27:00 <njohnston> So I am unsure if we should talk about Ocata priorities in one of these meetings, or in person at the summit
04:27:09 <chandanc_> Sorry we will not be able to make it this time :(
04:27:16 <njohnston> #link https://etherpad.openstack.org/p/fwaas-ocata fwaas ocata etherpad
04:27:41 <njohnston> chandanc_: I will regret not seeing you
04:28:01 <SridarK_> chandanc_: sigh - i was hoping both of u will make it
04:28:17 <hoangcx> njohnston, I will be at the summit and looking forward to discuss in person as last Austin summit.
04:28:26 <chandanc_> Ya, but we seem to have budget constrain :(
04:28:37 <SridarK_> hoangcx: ok will yushiro be there too ?
04:28:46 <SridarK_> chandanc_: yes i understand
04:28:53 <hoangcx> SridarK_, Yes. He will be there too
04:29:01 <SridarK_> ok
04:29:14 <njohnston> looking forward to seeing you again, hoangcx!
04:29:21 <njohnston> I have already been pursuing one of the items on the Ocata list, which is an integration with Congress.  I think it is very interesting, and I'll be chatting with the Congress people in one of their work sessions.
04:29:56 <njohnston> #link https://blueprints.launchpad.net/congress/+spec/congress-fwaas Congress integration with FWaaS
04:30:36 <SridarK_> njohnston: cool
04:31:12 <njohnston> It's quite exciting, I have been emailing with Tim Hinrichs on the Congress side
04:32:47 <SridarK_> njohnston: u can give us an outline either at the summit or we can discuss before
04:32:56 <njohnston> SridarK_: definitely
04:33:43 <SridarK_> since all folks will not make it, perhaps we can have a sync mtg with the team to focus on priorities and some level of input for planning and priorities folks would like to see addressed in Ocata
04:33:52 <njohnston> I think that would be very good
04:34:23 <SridarK_> we can do this in this forum or also as separate meeting (even as a conf call if folks so desire)
04:34:24 <chandanc_> +1
04:34:34 <njohnston> And to prep for that, make sure your ideas and info are in the etherpad
04:34:36 <SarathMekala> +1
04:34:42 <SridarK_> +1
04:35:21 <SridarK_> ok we can plan to discuss this next week either here or towards the end of the week if we need more time
04:35:41 <njohnston> sounds good
04:36:03 <njohnston> #topic Other changes
04:36:22 <njohnston> There are a few changes flying about that I wanted to mention
04:36:52 <njohnston> A fix to the periodic job that makes sure fwaas works with the master branch of neutron-lib (stadium prerequisite): https://review.openstack.org/#/c/380648/
04:37:17 <njohnston> Yushiro put in a bug fix for an argument issue: https://review.openstack.org/#/c/373964/
04:37:27 <njohnston> those two just need reviews
04:37:40 <njohnston> and if people are interested in looking at documentation
04:37:45 <SarathMekala> I will review them
04:38:11 <njohnston> please feel free to contribute to an embryonic install guide https://review.openstack.org/375706
04:38:31 <SridarK_> on the reviews
04:38:55 <njohnston> and/or migration of the fwaas docs from the admin guide to the networking guide, per Sam-I-Am's directions https://review.openstack.org/366331
04:39:34 <njohnston> I haven't had much time for the documentation, but I think the things that have been on my plate will start to get completed soon
04:40:36 <njohnston> Does anyone else have changes in-flight that we haven't talked about, that they'd like reviews on?
04:42:25 <njohnston> #topic Bugs
04:42:33 <njohnston> We haven't talked about bugs much in this meeting
04:42:43 <njohnston> But to draw attention to the list:
04:42:46 <njohnston> #link http://tinyurl.com/fwaas-bugs
04:43:32 <njohnston> one of those is from late September, bug 1622460
04:43:33 <openstack> bug 1622460 in neutron "neutron-server report 'FirewallNotFound' when delete firewall under l3_ha mode" [Low,Confirmed] https://launchpad.net/bugs/1622460
04:44:27 <njohnston> But we have bugs going back as far back as 2013 (gasp)
04:44:48 <SridarK_> many of these may just require clean up
04:44:58 <njohnston> So I am hoping that we can take a periodic look at bugs, especially as adoption increases we will start seeing a greater flow
04:45:10 <SridarK_> +1
04:45:36 <njohnston> and nuke bugs that date to a havana/icehouse timeframe
04:45:49 <SarathMekala> I have one observation to discuss on the bug area
04:45:58 <njohnston> Please go ahead, SarathMekala
04:46:22 <SarathMekala> when VPNaaS is installed using devstack it fails to start as it cant locate /etc/neutron/fwaas_driver.ini
04:46:48 <SridarK_> Hmm
04:46:50 <njohnston> Why is VPNaaS looking for the FWaaS config file?
04:47:01 <SarathMekala> I took a cursory glance at their installation script and there seems to be some linkage to FwaaS
04:47:27 <njohnston> I think they tried to create some hokey workaround so that FWaaS and VPNaaS could coexist
04:47:29 <SarathMekala> 1 min will share the paste link
04:47:40 <SridarK_> SarathMekala: the linkage is again embedded in the inheritance hierachy issues on L3Agent
04:47:44 <SarathMekala> http://paste.openstack.org/show/584360/
04:47:57 <SridarK_> VPN inherits from L3Agent class
04:49:27 <njohnston> was VPN's inheritance snipped the same way FWaaS's was?  I realize our inheritance was more sordid, with L3NATAgent inheriting from firewall_l3_agent.FWaaSL3AgentRpcCallback
04:49:42 <njohnston> But I would have thought they would have been given the shove a bit
04:49:44 <SridarK_> now how the ini file comes into play needs some thought - i dont recall why we see this
04:50:01 <SridarK_> i dont believe VPN made any fixes
04:50:36 <SridarK_> earlier, if VPN was configured - L3Agent would run as VPNAgent
04:50:55 <njohnston> https://github.com/openstack/neutron-vpnaas/blob/e9d8afa2d7c778b4c4ba7325b989953726700b0c/devstack/settings#L30-L32
04:51:32 <SridarK_> yes exactly if FWaaS is also enabled
04:51:41 <njohnston> exactly https://github.com/openstack/neutron-vpnaas/blob/e9d8afa2d7c778b4c4ba7325b989953726700b0c/devstack/plugin.sh#L57-L59
04:51:48 <SridarK_> then that too runs in the context of VPNagent
04:52:03 <njohnston> I think that we can propose to them that these bits be excised
04:52:34 <SridarK_> i think if i heard correctly, vpn did not want to make any changes
04:52:39 <SridarK_> i will ask Paul M
04:53:48 <njohnston> #topic Open Discussion
04:53:53 <SridarK_> SarathMekala: were u interested to get VPN up ?
04:53:54 <njohnston> Anything else, anyone?
04:54:23 <SarathMekala> Yes Sridar
04:54:46 <SarathMekala> on the Horizon UI front I will start working from next week
04:55:24 <SridarK_> SarathMekala: ok on VPN - there might not much traction in the community - i will ask and let u know
04:55:34 <SridarK_> one of the cores works with me
04:56:00 <SarathMekala> sure SridarK_.. thanks
04:56:05 <SridarK_> great on the horizon - it will be nice to get that in place, close on the heels of CLI
04:56:30 <njohnston> As far as VPNaaS, I threw up a quick patch to remove the FWaaS-specific bits from their devstack plugin
04:56:43 <njohnston> #link https://review.openstack.org/382141 Disentangle VPNaaS from FWaaS
04:56:53 <njohnston> So we can see how that is received
04:57:03 <SridarK_> sounds good
04:57:05 <SarathMekala> njohnston, you amaze me :O
04:57:14 <SridarK_> +1
04:57:36 * njohnston blushes
04:57:52 <njohnston> OK, I think that sounds like everything.  Last call?
04:58:00 <SridarK_> i am good
04:58:23 <SarathMekala> nothing on my side
04:58:27 <njohnston> excellent.  Thank you so much everyone.
04:58:29 <SridarK_> Thanks all
04:58:29 <njohnston> #endmeeting