18:32:08 <SridarK> #startmeeting Networking FWaaS
18:32:09 <openstack> Meeting started Wed Jul  1 18:32:08 2015 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:32:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:32:12 <openstack> The meeting name has been set to 'networking_fwaas'
18:32:17 <hoangcx> Hi all!
18:32:36 <SridarK> #chair badveli vishwanathj pc_m xgerman yanping
18:32:37 <openstack> Current chairs: SridarK badveli pc_m vishwanathj xgerman yanping
18:33:17 <annp> Hello
18:33:29 <SridarK> I am out on PTO and traveling with very little connectivity over last 2 weeks. On a very unreliable connection now so request alternate chairs to pls run thru the usual topics and end the meeting in case i get bounced.
18:33:47 <SridarK> We can run thru things quickly - i am quite disconnected both figuratively and literally over the last 2 weeks so pls chime in
18:33:59 <SridarK> #topic Bugs
18:34:29 <SridarK> I did not see anything very critical pop up -
18:34:56 <yanping> I have two bugs specific to Cisco CSR1kv and need code review
18:35:21 <SridarK> yanping: surely - i will be more connected early next week and will definitely take a look
18:35:29 <SridarK> request others to chime in as well
18:35:34 <yanping> great. Thanks.
18:35:35 <vishwanathj> yanping, please share the links to those bugs
18:35:44 <yanping> https://review.openstack.org/#/c/195253/
18:35:50 <yanping> https://review.openstack.org/#/c/196166/
18:36:31 <vishwanathj> thanks, I have added myself as a reviewer and will look into it
18:36:44 <yanping> thanks a lot !
18:36:51 <badveli> me too
18:37:24 <yanping> thanks !
18:40:26 <badveli> i think sridark is quit
18:40:28 <vishwanathj> looks like SridarK just left
18:40:40 <badveli> yes viswanathj
18:41:01 <jwarendt> Has SridarK dropped?  Would like to discuss use case topic i.e. https://etherpad.openstack.org/p/fwaas_use_cases
18:41:18 <xgerman> jwarendth +1
18:41:19 <vishwanathj> jwarendt, looks like we are still on topic bugs..
18:41:28 <xgerman> ok
18:41:31 <xgerman> just came in
18:41:47 <vishwanathj> I am looking to see if there are any additional FWaaS bugs...give me a couple secs to see if there is any more
18:41:55 <badveli> regularky we go over the bugs, blue prints and then fwaas use case
18:42:16 <vishwanathj> badveli, yes....do you see any additional bugs that needs to be discussed
18:42:39 <badveli> 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=&field.has_no_package=
18:42:54 <badveli> i am not able to see any critical bugs
18:43:32 <badveli> i think your patch got merged, correct?
18:43:37 <vishwanathj> me neither, maybe we can move onto blueprints...
18:43:37 <SridarK> sorry folks my connectivity is real bad
18:43:51 <vishwanathj> badveli, yes my bug patch got merged last week
18:44:08 <SridarK> sorry folks are we done on bugs
18:44:23 <SridarK> pls one of u folks can drive if i bounce again
18:44:39 <badveli> sridark we were checking the bugs and nothing
18:44:40 <vishwanathj> SridarK, looks like we can move onto blueprints, there are no more critical bugs to be discussed
18:44:44 <badveli> critcial
18:44:51 <SridarK> ok
18:45:12 <SridarK> not sure if slawek is here
18:45:32 <SridarK> badveli: lets get into service objects
18:45:39 <SridarK> #topic Service Objects/Group
18:45:56 <badveli> thanks to pc_m i got some info on scenario tests
18:46:06 <SridarK> badveli: all urs - u were going to run thru where u were on this
18:46:50 <badveli> hopefully i will submit two patches one neutron patch and the other one as functional tests/ scenario tests
18:47:04 <SridarK> ok perfect
18:47:21 <pc_m> badveli: You may need to modify tox.ini to setup for functional tests too.
18:47:23 <SridarK> u should keep ur eyes on the micro versioning work being done as well
18:47:30 <badveli> sridark i think liberty -1 is done right?
18:47:37 <pc_m> not sure what is in place for FW. but you can look at LB/VPN.
18:47:52 <SridarK> badveli: yes
18:47:59 <badveli> thanks pc_m for your help, i will keep that in mind
18:48:06 <pc_m> badveli: Yes Liberty-1 is out
18:48:13 <xgerman> yes
18:48:28 * pc_m I could tell by the billon emails of bug status changes
18:48:33 <badveli> pc_m currently we have not yet done with functional tests
18:48:42 <SridarK> badveli: since ur spec is approved - u should be able to move on - u can start putting out some WIP patches
18:49:00 <badveli> yes
18:49:00 <SridarK> badveli: pls ping us if u need some help
18:49:05 <pc_m> badveli: For VPN I had to do some setup stuff to add the test, directories, scripts.
18:49:07 <badveli> thanks sridark
18:49:13 <SridarK> SumitNaiksatam: hi
18:49:31 <SridarK> badveli: anything else that u want to discuss on this
18:49:36 <badveli> thanks pc_m, should we have the functional tests in place before scenario tests?
18:49:44 <SumitNaiksatam> SridarK: hi
18:49:46 <SumitNaiksatam> hi all
18:50:03 <pc_m> badveli: For VPN the scenario tests run under the functional job.
18:50:04 <badveli> hello sumit
18:50:21 <xgerman> in LBaaS we have different jobs
18:50:21 <pc_m> badveli: For VPN I had to setup a functional job in project-config too.
18:50:22 <badveli> yes from the patch i could see that
18:51:14 <SridarK> badveli: cool, thx pc_m:
18:51:23 <pc_m> badveli: FYI:  https://wiki.openstack.org/wiki/Neutron/FunctionalGateSetup
18:51:59 <pc_m> badveli: If you create a new job for scenario tests (whether separate job or under functional), you'll need to do this stuff to set it all up.
18:53:03 <badveli> thanks pc_m,  since my patch will be in neutron can i use the existing function job in neutron
18:54:23 <pc_m> badveli: sure, but if you make a test in neutron-fwaas, you'll likely want a job for it.
18:55:10 <pc_m> badveli: Neutron also has Full Stack tests. You can talk to amuller about those.
18:55:49 <SridarK> badveli: perhaps u can discuss this more with pc_m offline
18:56:05 <pc_m> SridarK: sure
18:56:32 <badveli> should we get the neutron patch first before the scenario tests, will it be fine? since the fwaas will be the user of this generic objects, may be a neutron patch and neutron-fwaas scenario tests?
18:56:33 <SridarK> lets move to the next
18:56:45 <badveli> ok thanks sridark, pc_m
18:57:21 <SridarK> badveli: sorry - perhaps we can pick this up in the open discussion
18:57:36 <SridarK> #topic Logging Spec
18:57:38 <badveli> ok thanks
18:57:45 <hoangcx> hi SridarK
18:57:47 <SridarK> i think yushiro is not here, hoangcx:
18:57:51 <SridarK> pls go ahead
18:57:59 <hoangcx> According to the discussion in the previous meeting: Beside current spec for FWaaS logging, Yushiro has already registered NEW Packet logging API with RFE tags as the following link #link https://bugs.launchpad.net/neutron/+bug/1468366
18:57:59 <openstack> Launchpad bug 1468366 in neutron "RFE - Packet logging API for Neutron" [Undecided,Confirmed] - Assigned to Yushiro FURUKAWA (y-furukawa-2)
18:58:38 <SridarK> hoangcx: sorry - i am out so not been able to take  a look but pls bring up anything u want to discuss
18:58:57 <hoangcx> It will be added to Neutron meeting agenda to get decisions and approve as mestery's suggestion.
18:59:08 <SridarK> hoangcx: perfect
18:59:15 <SridarK> and we can all take a look as well
18:59:21 <hoangcx> Sridark: Thanks for your consideration. It still in proggress :)
18:59:53 <SridarK> hoangcx: no worries - i will hopefully be online enough next week to take a look as well
19:00:12 <hoangcx> SridarK: Yeah. I want you and all of us to help to take a look on it
19:00:41 <SridarK> hoangcx: surely, others anything to chime in here ?
19:00:59 <hoangcx> SridarK: enough for me today.
19:01:06 <vishwanathj> will take a look into the RFE and spec later this week
19:01:46 <hoangcx> I want to inform to all of us about status of Logging spec and need to get more discussion to get approve
19:01:56 <hoangcx> vish: Thanks a lot :)
19:03:06 <vishwanathj> SridarK, you still there?
19:04:21 <xgerman> so should we move on?
19:04:23 <vishwanathj> I think the next topic would be fwaas_use_cases if hoangcx is done
19:04:36 <xgerman> #topic fwaas_use_cases
19:04:39 <hoangcx> Yeah. I'm done today :)
19:04:40 <badveli> yes lets move on
19:04:46 <hoangcx> Please go ahead.
19:04:56 * xgerman already changed topic
19:05:24 <vishwanathj> xgerman, what do you have to share with us today?
19:05:42 <xgerman> jwarendt did some analysis and posted a ton of new use cases
19:06:01 <badveli> xgerman as you had mentioned we need to have the visibility into the traffic
19:06:07 <xgerman> we are looking for some feedback and then we would like to prioritize...
19:06:09 <jwarendt> Again at https://etherpad.openstack.org/p/fwaas_use_cases
19:06:21 <badveli> i am not seeing that in the use case ehterpad
19:06:43 <vishwanathj> badveli, I do see some additional content
19:06:53 <badveli> east west traffic
19:07:16 <SridarK> sigh sorry folks the connectivity is very frustrating
19:07:37 <SridarK> #topic SG - FWaaS alignment
19:07:42 <badveli> i think we are adding it now, thanks xgerman
19:07:43 <xgerman> bedevil added it
19:07:43 <vishwanathj> SridarK, xgerman has set the topic  to fwaas_use_cases
19:08:00 <xgerman> I am good with either topic :-)
19:08:36 <SridarK> xgerman: pls go ahead
19:08:37 <SridarK> thx for taking over
19:08:44 <SridarK> pls go ahead :-)
19:09:03 <xgerman> no worries — I just changed the topic
19:09:22 <SridarK> and pls go to Open Discussion and close out the mtg as well
19:09:49 <xgerman> so I am thinking of sending an e-mail to get more eyes on this use cases and then we can try to map them to existing API’s + prioritize the gaps
19:10:03 <SridarK> after u are done
19:10:12 <xgerman> k
19:10:26 <jwarendt> badveli - adding east/west traffic use case makes sense.  Can you clarify on what type of traffic visibility (deep protocol inspection?) you are asking for?
19:10:36 <SridarK> xgerman: +1 on that
19:11:46 <badveli> jwarendt, deep packet inspection capability right now we do not have
19:12:32 <badveli> previously we tried some blue print that had the details with the dvr
19:13:01 <xgerman> ok, we can probably revisit that. I have also seen some tap blueprint
19:13:28 <badveli> thanks xgerman
19:15:37 <xgerman> ok, I guess we can move on
19:15:45 <vishwanathj> ok
19:16:03 <xgerman> I will let SridarK change the topic now as he is back ;-)
19:16:05 <badveli> there are very good  detailed inputs in etherpad, thanks to all
19:16:14 <mickeys> I am not clear on how this is supposed to progress. Is there any chance of making the Liberty cycle? We are talking about iterating on use cases, then mapping to APIs, then iterating on APIs, and only then getting to development. From Vancouver, we see that there is wide interest well beyond the FWaaS team
19:17:06 <xgerman> mickeys I agree we might not make it in Liberty. It took us in Lbaas about two cycles to go through that process
19:17:36 <jwarendt> +1
19:17:50 <xgerman> but I would like to close the use case discussion pretty quickly so we can get to development...
19:19:02 <mickeys> OK. If anyone has suggestions how to speed this process up, I would like to hear it. Otherwise, will continue to monitor and hope to get involved.
19:20:48 <vishwanathj> xgerman, do you think that in 2 weeks from now we would have closed on use case discussion
19:21:01 <xgerman> I am hoping for that
19:21:16 <SridarK_> xgerman: request u to continue driving to make sure we end the mtg on time - my connectivity is terribly frustrating for me
19:21:26 <xgerman> ok, will do
19:21:45 <SridarK_> xgerman: yes lets hope we can close over the next 2 + weeks
19:22:05 <xgerman> so my goal is to send the e-mail let people weigh in and then close at next meeting
19:22:25 <xgerman> yeah, as mickeys said we need to start moving :-)
19:22:33 <vishwanathj> xgerman, the next step after that would be API mapping, right?
19:22:37 <xgerman> yes
19:23:03 <jwarendt> +1, though understand folks may be gone over US holiday like SridarK and need their input.
19:23:04 <xgerman> and then we need to find the gaps in the API and the prioritize how we tackle those
19:23:47 <xgerman> I expect not to get all gaps filled in liberty but I am hoping to get the most important ones
19:24:04 <mickeys> I see at least three areas of possible extension of APIs: 1) extend to security groups functionality since there are objections to modifying the security group APIs, 2) context such as interface, direction, or groups, 3) DPI, IDS, etc
19:24:57 <xgerman> no objection...
19:26:12 <xgerman> ok, we have 4 minutes left
19:26:14 <vishwanathj> friendly reminder, we have 4 minutes for open discussion and to end the meeting
19:26:16 <badveli> xgerman, some of them like DPI require much more efforts
19:26:50 <xgerman> yes, hence I am saying we need to prioritize :-)
19:26:59 <xgerman> and DPI might land in M
19:27:50 <SridarK> or may be even later as we need to have a sound open source reference implementation
19:28:19 <xgerman> +1
19:28:45 <SridarK> 2 min warning and no timeouts :-)
19:29:52 <xgerman> and 1
19:30:02 <SridarK> if nothing else xgerman: can u pls end the meeting, next time i will be back home and hopefully back to normal connectivity - apologies for today
19:30:12 <xgerman> #endmeeting