18:11:22 <SumitNaiksatam> #startmeeting Networking FWaaS
18:11:23 <openstack> Meeting started Wed Dec 18 18:11:22 2013 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:11:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:11:26 <openstack> The meeting name has been set to 'networking_fwaas'
18:11:42 <SumitNaiksatam> I am anticipating a short meeting
18:11:50 <yisun_> ok
18:12:14 <SumitNaiksatam> RajeshMohan is here i believe
18:12:24 <SumitNaiksatam> we discussed most items last week
18:12:50 <SumitNaiksatam> the only new item this week is the patch posted by RajeshMohan
18:12:54 <yisun_> Yes, Sorry I could not join, we had a release
18:12:55 <SumitNaiksatam> its still WIP
18:13:14 <SumitNaiksatam> yisun_: no worries at all
18:13:14 <SumitNaiksatam> yisun_: i know how it goes
18:13:17 <SumitNaiksatam> yisun_: garyduan was around, so it's all good
18:13:17 <yisun_> :-)
18:13:35 <yisun_> right, he gave me some updates
18:14:03 <SumitNaiksatam> yisun_: great
18:14:48 <SumitNaiksatam> so like I was saying, RajeshMohan has posted a patch which addresses the firewall insertion
18:15:02 <SumitNaiksatam> him and i had a chat yesterday
18:15:47 <SumitNaiksatam> to some extent it deviates from the discussion which we had
18:15:55 <SumitNaiksatam> so he is going to make the changes accordingly
18:16:13 <SumitNaiksatam> he is addressing adding the "service context" and then leveraging it within fwaas
18:16:51 <SumitNaiksatam> the "service context" can be used by other services
18:17:45 <songole> what is service context. Sorry, i didn't read the BP yet.
18:17:59 <SumitNaiksatam> #link https://review.openstack.org/#/c/62599/
18:19:03 <SumitNaiksatam> songole: #link https://docs.google.com/document/d/1fmCWpCxAN4g5txmCJVmBDt02GYew2kvyRsh0Wl3YF2U/edit#
18:19:23 <songole> thanks
18:19:42 <SumitNaiksatam> songole: it is a way for the user to provide context for the provider to insert the service
18:20:15 <SumitNaiksatam> songole: its a pretty simple concept - it includes references to one or more neutron resources (networks, subnets, ports, routers)
18:20:20 <yisun_> Sumit: so we plan to move the service context to a top level resource now?
18:20:35 <songole> ok. got it.
18:21:34 <SumitNaiksatam> songole: the provider looks at the context and infers how to insert
18:21:50 <SumitNaiksatam> songole: the user need not have to care about how the insertion happens
18:22:10 <songole> Sumit: does it steer the traffic from that context to the firewall or it provides access to that context?
18:22:24 <SumitNaiksatam> yisun_: we moved away from the service_context being a first class resource
18:22:57 <yisun_> sumit: ok, i that is what I thought
18:23:45 <SumitNaiksatam> yisun_: it will be an attribute in the service
18:24:11 <SumitNaiksatam> yisun_: we are trying to figure out how we can make it consistent across services
18:24:51 <yisun_> sumit: this makes think if I should make service_group/object as a first class resource or not
18:24:57 <SumitNaiksatam> yisun_: so that each service does not have a different way to provide this context
18:25:33 <SumitNaiksatam> yisun_: that should be
18:25:46 <SumitNaiksatam> yisun_: sorry, i take that back
18:25:57 <SumitNaiksatam> yisun_: i misunderstood
18:26:23 <SumitNaiksatam> yisun_: my thinking was that we will use attribute extension to achieve fwaas service_objects
18:27:09 <SumitNaiksatam> songole: to your question - the current thinking is that how the provider uses the context is left to the provider
18:27:19 <SumitNaiksatam> songole: there are examples in the google doc
18:27:22 <yisun_> sumit: remember during the summit, people asked if the service_object can be used by other services ?
18:27:43 <yisun_> sumit: and I answered yest
18:27:45 <SumitNaiksatam> yisun_: i think we can make that work as well
18:28:07 <yisun_> sumit: my current implementation is to make it a top level resource
18:28:13 <songole> sumit: thanks. I will read the doc
18:28:26 <SumitNaiksatam> yisun_: ok, we might need to discuss
18:28:48 <yisun_> Sumit: how about I shot you an email
18:28:59 <SumitNaiksatam> yisun_: sounds good
18:29:22 <SumitNaiksatam> yisun_: we can get together and brain storm
18:29:46 <yisun_> sumit: sure, but it may need to be later, since I'm sick too
18:29:56 <yisun_> sumit: I don't want to pass it to you :-)
18:30:06 <SumitNaiksatam> yisun_: sure…sorry to hear that
18:30:27 <SumitNaiksatam> yisun_: we can take this item per convenience and at your pace
18:30:44 <SumitNaiksatam> i would encourage everyone to take a look at RajeshMohan's patch once he uploads the second (modified patch set)
18:30:44 <yisun_> sumit: sounds good
18:31:14 <yisun_> sumit: sure
18:31:24 <SumitNaiksatam> the current patch set will change
18:33:06 <SumitNaiksatam> i didn't get into a topic driven agenda today since i wanted to keep it free form and follow up on a couple of items
18:33:55 <SumitNaiksatam> I don't see the Mark McClain (PTL) is around today as well
18:34:28 <SumitNaiksatam> tempest is still top of the mind for the FWaaS team
18:34:59 <SumitNaiksatam> anyone wanting to contribute please let me know
18:35:47 <SumitNaiksatam> does anyone want to bring up anything else?
18:36:53 <SumitNaiksatam> ok so we can finish early today
18:37:00 <yisun_> ok
18:37:17 <SumitNaiksatam> #info we will not meet next week and the week after
18:37:26 <SumitNaiksatam> on account of the holidays
18:37:35 <SumitNaiksatam> keep the discussion going on emails
18:37:43 <SumitNaiksatam> and/or we can meet
18:37:43 <yisun_> sure
18:37:51 <SumitNaiksatam> alright, thanks for joiing
18:37:57 <yisun_> thanks,
18:37:57 <SumitNaiksatam> #endmeeting