18:31:44 <sc68cal> #startmeeting networking_fwaas
18:31:45 <openstack> Meeting started Wed Aug 26 18:31:44 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:31:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:31:49 <openstack> The meeting name has been set to 'networking_fwaas'
18:31:49 <sc68cal> #chair SridarK
18:31:50 <achippa> hi
18:31:50 <openstack> Current chairs: SridarK sc68cal
18:32:05 <njohnston> hi all
18:32:30 <sc68cal> #info Agenda - https://wiki.openstack.org/wiki/Meetings/FWaaS
18:32:30 * mestery lurks
18:32:43 <blogan_> ominous
18:32:56 <SridarK> sc68cal: just to clarify - we will alternate meeting time slots ?
18:33:05 <sc68cal> SridarK: indeed - let me note that
18:33:25 <sc68cal> #info We now have an APAC friendly meeting - alternating weeks - 18:30 UTC and 00:00 UTC
18:33:46 <sc68cal> #link http://eavesdrop.openstack.org/#Firewall_as_a_Service_(FWaaS)_Team_Meeting Meeting times
18:33:49 <SridarK> sc68cal: sounds good thanks, i will update the wiki as well
18:34:08 <sc68cal> So next week will be 00:00 UTC on _thursday_
18:34:25 <sc68cal> Please note this is still on _wednesday_ in North America
18:34:50 <xgerman> ack
18:35:16 <sc68cal> So last week's meeting was light, since I announced it 5 hours before hand ;)
18:35:35 <SridarK> sc68cal: :-) i was on a plane - so i missed it totally
18:35:44 <sc68cal> but I wanted to start building the habit early, so I'd be prepped for next week when we do it for real
18:36:04 <badveli> i was not sure on the time
18:36:13 <vishwanathj> will the agenda differ?
18:36:47 <SridarK> vishwanathj: no, just makes it easier for yushiro, hoangcx and others to join
18:37:10 <vishwanathj> SridarK, ok, Thanks
18:37:10 <sc68cal> vishwanathj: good question - I don't think it will, mostly because I think I'll be relying on the APAC attendees to attend and discuss stuff they want to discuss - I'll probably bring things over the week after if it needs more disucssion. Basically I can be the bridge
18:37:30 <vishwanathj> sc68cal, thanks
18:38:07 <sc68cal> So - the big item that we need to discuss is the logging API, as requested by yushiro and hoangcx
18:38:58 <sc68cal> I'll just drop the link and then we'll go through the agenda
18:39:00 <sc68cal> #link https://review.openstack.org/#/c/203509/
18:39:38 <sc68cal> #topic bugs
18:39:49 <sc68cal> #link https://bugs.launchpad.net/openstack/+bugs?field.searchtext=fwaas&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch
18:39:49 <sc68cal> =&field.has_no_package= Bugs
18:40:03 <sc68cal> hmmm that link is bigger than I thought
18:41:01 <hoangcx> sc68cal: Thanks a lot and sorry for late.
18:41:14 * hoangcx just took a cup of coffee :-)
18:41:27 <SridarK_> sc68cal: nothing major - on my radar
18:41:39 <sc68cal> #action cores - we need to go through the bugs and triage as apropriate
18:41:45 <SridarK_> sc68cal: i know u have been flushing out som sold ones
18:42:14 <sc68cal> SridarK_: yep - low hanging fruit like https://bugs.launchpad.net/neutron/+bug/1487599
18:42:16 <openstack> Launchpad bug 1487599 in neutron "fwaas - ip_version and IP address conflicts are not raised" [Undecided,In progress] - Assigned to Sean M. Collins (scollins)
18:42:45 <sc68cal> Still getting my hands around some of the unit test code and such - had to fix some things here and there to get them running
18:43:18 <SridarK_> sc68cal: sounds good and good to flush out some of these old ones
18:44:16 <sc68cal> Any other bugs? Otherwise I think we can continue on to blueprints
18:44:23 <sc68cal> I think we have some activity to discuss there
18:45:13 <sc68cal> #topic blueprints
18:45:53 <sc68cal> Ah - we got the REJECT action merged - yay! https://review.openstack.org/#/c/148416/
18:46:10 <vichoward> ;)
18:46:23 <jwarendt> +1
18:46:25 <SridarK> +1
18:46:46 <sc68cal> SridarK_ beat me to the puch on approving - I was setting up my gear today and yesterday in order to test it
18:46:58 <vishwanathj> :)
18:47:00 <SridarK> sc68cal: :-)
18:47:22 <sc68cal> #link https://wiki.openstack.org/wiki/Neutron/FWaaS/LibertyPlan Liberty Plan for FwaaS
18:47:23 <xgerman> +1
18:47:36 <sc68cal> just going by what was linked in the wiki
18:47:54 <sc68cal> I think probably https://review.openstack.org/#/c/171340 is going to get moved to Mitaka
18:48:38 <SridarK> sc68cal: yes we needed to get some alignment on the reviews
18:48:47 <sc68cal> Looks like https://review.openstack.org/#/c/94133 - the spec was merged - but I'll have to dig up if the code has been merged
18:49:06 <SridarK> sc68cal: will be good to discuss this at the Summit along with other things to prioritize
18:49:12 <sc68cal> although ... that is pretty old - 1 year+ review
18:49:19 <sc68cal> so the wiki uh, might be a little stale ;)
18:49:26 <badveli> we had a different link
18:49:38 <badveli> not sure how this was changed
18:50:10 <badveli> we had the latest one for liberty
18:50:15 <SridarK> sc68cal: , badveli: - this is the Service Group
18:50:26 <SridarK> badveli: do u think this has a chance for L ?
18:50:27 <badveli> yes let me change the link
18:50:48 <SridarK> badveli: i know u are busy and are bandwidth limited
18:50:54 <badveli> with my limited time i was able to add the extension
18:51:10 <badveli> and my unit test had an issue
18:51:19 <SridarK> badveli: it seems that this is very tight for L
18:51:21 <badveli> when is the deadline for L?
18:51:29 <sc68cal> this week I think.
18:51:53 <SridarK> badveli: yes as sc68cal: mentions u are almost at time
18:52:00 <sc68cal> sorry, Sept 3rd
18:52:03 <blogan_> the deadline is next week no?
18:52:04 <badveli> since i had added this as an extension to neutron
18:52:27 <SridarK> badveli: but u will need a reference backend in FWaaS correct ?
18:52:36 <badveli> correct
18:52:51 <sc68cal> #link https://blueprints.launchpad.net/neutron/+spec/fwaas-customized-service  FWaas extension for customized service and service group
18:52:54 <badveli> sridark initially our plan was to add the extension in neutron
18:52:59 <SridarK> badveli: if u are comfortable - no harm in trying
18:53:19 <sc68cal> is that the right blueprint link?
18:53:30 <sc68cal> I see that linked to the L-3 milestone in launchpad
18:53:32 <SridarK> we can request for an FFE as this has been on the table for a few releases now
18:53:38 <badveli> sridark i am trying to understand if we need both the extension and the reference implementation
18:53:41 <SridarK> in case u just miss time
18:54:12 <SridarK> badveli: usually just having an API without a backing ref implementation is frowned upon -
18:54:25 <SridarK> badveli: my sense is that it will not get support
18:54:28 <sc68cal> #link https://review.openstack.org/#/c/200778/ Add service group as a firewall customized service
18:54:29 <badveli> with my limited time i can try
18:54:42 <SridarK> others can shed more light on this as well
18:55:17 <sc68cal> badveli: do you think it would be easier to push this to Mitaka-1, so you don't have to try and rush?
18:55:21 <badveli> since the service group is a generalized one
18:56:02 <badveli> fine with me if we think we have the extension and the reference implementation
18:56:08 <badveli> as needed
18:56:38 <sc68cal> yeah I think the reference implementation piece is what will be needed for merge, so I'd take the time to iterate
18:57:04 <SridarK_> sorry connectivity issues keep bouncing out
18:57:09 <SridarK_> and in
18:57:27 <sc68cal> we can ping mestery to change the milestone for https://blueprints.launchpad.net/neutron/+spec/fwaas-customized-service to mitaka-1 if there is consensus
18:58:06 <SridarK_> badveli: how do u feel ? I also think we are cutting it really fine now
18:58:25 <badveli> thanks sc68cal but i was thinking we can merge the extension and go from there with my time
18:59:09 <sc68cal> badveli: There have been few, if any API extensions that have been merged without an implementation - and the ones that have merged without don't have a good track record
18:59:23 <badveli> SridarK_: i can try adding the extension if we need in liberty
18:59:24 <SridarK_> sc68cal: +1 yes this is my concern too
18:59:52 <SridarK_> badveli: this can be tricky IMHO as well
19:00:27 <badveli> fine SridarK_ i am trying my best in my time that i can spend
19:00:44 <SridarK_> badveli: totally understand ur situation
19:00:54 <badveli> we can implement both patches in mitaka-1
19:01:10 <sc68cal> badveli: understood - I think we want to give you more time so you don't feel pressured - I'd rather see it get done at a reasonable pace instead of burning you out trying to rush it in
19:01:22 <SridarK_> badveli: yes that may make things easier for u
19:01:35 <badveli> ok thanks
19:01:56 <sc68cal> mestery: looks like we have consensus on the bp https://blueprints.launchpad.net/neutron/+spec/fwaas-customized-service - it can be moved to Mitaka
19:01:57 <badveli> sorry with the amount of time that i had i am always falling behind
19:02:16 <SridarK_> badveli: no thanks for sticking with this on ur own time
19:02:27 <badveli> thanks SridarK_
19:03:22 <sc68cal> hoangcx: we did discuss off-list about the logging API - I want to get everyone up to speed about the proposal, I think based on the timeline it's better to push to Mitaka as well
19:03:58 <xgerman> +1
19:04:21 <hoangcx> sc68cal: Ack.
19:04:46 <xgerman> I think logging needs some F2F discussion in Tokyo
19:05:07 <hoangcx> xgerman: +1000
19:05:11 <annp> +1
19:05:42 <SridarK_> +1
19:07:02 <sc68cal> ok - any other blueprints to discuss?
19:07:15 <hoangcx> xgerman, sc68cal: Thanks for commenting in the spec. Let's discuss about it in Tokyo
19:07:47 <xgerman> y.w. - I am also hoping some of the centralized login people in my corp will give feedback as well
19:07:54 <SridarK_> sc68cal: i believe those were the key ones
19:08:16 <xgerman> we should start creating blueprints for M
19:08:40 <xgerman> mickeys submitted something nice
19:09:03 <mickeys> Not quite a blueprint yet, but I hope a starting point to resolve FWaaS with DVR
19:09:14 <sc68cal> indeed - thanks a ton mickeys
19:09:19 <jwarendt> +1
19:09:32 <SridarK_> +1 and we should spend some time discussing this along with the DVR guys
19:09:37 <sc68cal> I think probably we'll use the etherpad for a design summit session to talk it out
19:09:52 <sc68cal> SridarK_: +1
19:09:52 <SridarK_> mickeys: nice job on capturing the state of things
19:10:25 <mickeys> Do we think there is any chance to get any interaction on the etherpad before Tokyo? Or do most of it in person?
19:10:39 <xgerman> I haven’t heard from mystery on design summit but I doubt we get more than 2 sessions
19:10:43 <SridarK_> mickeys: this is a bit of a complex beast and as u point out as well - we want to arrive at something that does not compromise the performance we get with DVR
19:10:43 <xgerman> mestery
19:11:03 <sc68cal> mickeys: I think we can bump the mailing list thread in the meantime
19:11:09 <xgerman> +1
19:11:38 <xgerman> also we can arrange some hangout meeting with a focused group
19:11:40 <SridarK_> mickeys: +1 lets get something going on the etherpad for sure before and get some participation from the DVR folks
19:11:47 <SridarK_> xgerman: +1
19:12:11 <mickeys> I was not sure whether to use [L3] or [dvr] on the mailing list to get their attention?
19:12:20 <xgerman> try both
19:12:27 <mickeys> ok
19:12:27 <xgerman> :-)
19:12:38 <sc68cal> :)
19:13:34 <sc68cal> anything else - otherwise I'll open the floor to discussion
19:14:08 <sc68cal> #topic open discussion
19:14:28 <xgerman> Tokyo talks came out
19:14:53 <xgerman> OpenStack Neutron FWaaS Roadmap — has been accepted
19:15:01 <SridarK> xgerman: +1
19:15:05 <jwarendt> +1
19:15:08 <vishwanathj> +1
19:15:08 <mickeys> +1
19:15:11 <SridarK> just saw the official email come out
19:15:14 <hoangcx> xgermen +1
19:15:17 <xgerman> same here
19:15:33 <vishwanathj> SridarK, Thanks for initiating the FWaaS roadmap talk
19:15:39 <xgerman> +1000
19:15:41 <SridarK> so we can use this as a forum to communicate our discussions
19:15:54 <sc68cal> woo!
19:16:09 <SridarK> and hopefully get good feedback
19:16:19 <xgerman> +1
19:17:03 <hoangcx> xgerman: do you know any public infor link about that?
19:17:43 <SridarK> hoangcx: it should be on the talks link - there is not much info there other than a skeleton
19:17:53 <xgerman> juts got an e-mail
19:18:09 <xgerman> so will probably be posted there soon
19:18:17 <hoangcx> xgerman: Ack. :-)
19:19:13 <hoangcx> SridarK: ACK. :-)
19:21:30 <SridarK> We should slot a few working group type sessions over the week at Tokyo - once the schedules start coming out - we will have more visibility for times
19:21:42 <xgerman> +1
19:23:34 <badveli> good luck to all in tokyo
19:23:58 <SridarK> badveli: thanks - i wish u could have made it
19:24:11 <badveli> no sridar as usual
19:24:22 <badveli> but i am very excited that we are getting a clear path
19:24:29 <badveli> when compared to where we started
19:24:48 <SridarK> yes i hope at the end of M we will be out of experimental
19:25:03 <badveli> yes
19:25:24 <jwarendt> +1
19:25:34 <xgerman> +1
19:27:20 <sc68cal> one thing we need to figure out - is how to make a release for liberty
19:27:52 <sc68cal> since I think there was an e-mail on the ML today which brought up that question, and I think it's relevant to us
19:28:41 <sc68cal> Subject: [openstack-dev] [neutron] How to make deb and rpm packages for a networking-* project?
19:28:54 <sc68cal> anyway, we're almost out of time
19:29:16 <jwarendt> sc68cal: Will check out that email - thanks for pointing out.
19:29:26 <sc68cal> Until next week everyone - 00:00 UTC next week!
19:29:26 <SridarK> sc68cal: yes missed that too
19:29:33 <SridarK> sounds good
19:29:35 <SridarK> bye all
19:29:36 <badveli> bye all
19:29:39 <annp> bye
19:29:47 <sc68cal> #endmeeting