00:01:07 <sc68cal> #startmeeting networking_fwaas
00:01:08 <openstack> Meeting started Thu Jan  7 00:01:07 2016 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.
00:01:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
00:01:11 <openstack> The meeting name has been set to 'networking_fwaas'
00:01:53 <xgerman> ok, for next week it seems RAX won’t be serving their famous bacon breakfast
00:02:01 <Aish> o/
00:02:05 <xgerman> so you gotta grab that before we meet there
00:02:27 <mickeys> Hi everyone. Sorry I am a couple of minutes late.
00:02:45 <sc68cal> #topic API spec
00:03:16 <xgerman> I think we are done. Lot’s of +2/+1
00:03:23 <SridarK> So i think we are good
00:03:27 <sc68cal> I think the spec is in a good place. Hopefully armax, dougwig or someone else on the neutron-drivers team can approve
00:03:50 <xgerman> dougwig?
00:03:51 <sc68cal> I've taken the spec and have started putting together the RESOURCE_ATTRIBUTE_MAP for the new API - so far so good
00:04:02 <xgerman> link?
00:04:14 <sc68cal> it's not up for review yet, started about an hour ago
00:04:25 <xgerman> oh, ok
00:04:50 <xgerman> you know the saying what’s not in git doesn’t exist
00:04:55 <xgerman> :-)
00:05:02 <sc68cal> it's in my git, just not pushed up yet
00:05:29 <xgerman> k
00:05:31 <SridarK> Aish: if u do push another version pls add in the links for the stats related blueprints and u can state that more details will be covered there
00:05:37 <sc68cal> Once the spec merges into neutron-specs, I also have a commit that pulls it into doc/ in our repo, so we can maintain it into the future, and I'll also push a new patch into neutron-specs once we publish it, to redirect people to the RST file for the API once we publish it
00:05:55 <xgerman> nice
00:06:03 <Aish> Do we need another patch? SridarK
00:06:15 <xgerman> I would rather not with all the +2s/+1s
00:06:30 <SridarK> Aish: only if u are going to - to address dougwig's question
00:06:45 <sc68cal> I think we can update it once we've got the RST over in neutron-fwaas repo
00:06:54 <xgerman> +1
00:06:55 <Aish> +1
00:07:15 <SridarK> Yes only if we had to push another patch, no need to push one just for this
00:07:59 <Aish> SridarK ok.
00:10:10 <xgerman> unrelated to the spec we need to decide how we version and transition users
00:10:28 <xgerman> to the new API
00:10:40 <sc68cal> xgerman: good point.
00:10:46 <SridarK> xgerman: good point, some discussion along the lines of sc68cal: 's email ?
00:10:48 <sc68cal> #topic API versioning and transition
00:11:01 <xgerman> #link https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg72002.html
00:11:30 <SridarK> if we can do something to this effect that will be good
00:12:40 <xgerman> doing a hard break (aka a new extension) made it so that Horizon, heat, stopped working so I am in favor of a compatibility layer
00:13:19 <SridarK> xgerman: yes that was ur concern
00:13:20 <xgerman> but like SridarK if that’s too much work/not enough time I am ok with skipping that
00:14:03 <sc68cal> My thinking is - leave v1 API as it is today. We don't touch it, but we start work on the v2 API
00:14:16 <sc68cal> if we finish work on the v2 API, then maybe we work on a translation layer after
00:14:20 <xgerman> so you can run v1 and v2 in the same install?
00:14:36 <SridarK> perhaps we can try to nail some of this down along with other cores next week ?
00:14:53 <sc68cal> xgerman: most likely people will be running v1 for a while
00:15:16 <sc68cal> we have to make something that works for v2 first, and that could take some time
00:15:22 <xgerman> yep, agreed. So are we allowing v1 and v2 to run on the same system
00:15:33 <sc68cal> there is no v2 to run at this point
00:15:50 <xgerman> I know I am juts planning ahead
00:16:07 <sc68cal> if we got that compat layer - that would make it possible to do v1 and v2 - but let's defer that until we actually have something
00:16:11 <xgerman> because for in parallel we need two different DBs
00:16:15 <xgerman> or schemas
00:16:22 <SridarK> hmm some thought is needed on the data models to have both run both together
00:16:32 <SridarK> yes exactly xgerman
00:16:35 <xgerman> yep, or we decide that’s not an option :-)
00:17:02 <jwarendt_> We should have unique DB schemes and assume both can be run together IHOM.
00:17:20 <sc68cal> Basically I don't think we can just directly modify any of the code we currently have in the neutron-fwaas repo
00:17:52 <jwarendt_> Agreed.  But there is no reason we cannot write V2 to use unique, non-conflicting data.
00:18:01 <sc68cal> jwarendt_: agreed.
00:18:23 <xgerman> so we use a different schema/tables than v1
00:18:33 <jwarendt_> +1
00:18:44 <SridarK> yes that seems to be a good option
00:19:01 <SridarK> we can think in terms of deprecation of v1 at some later point
00:19:50 <SridarK> xgerman: does that seem to align with ur lbaas experience ?
00:20:00 <sc68cal> Data migration from v1 to v2 should be possible - we'll just have to do it as its own task. It's big enough
00:20:21 <sc68cal> v2 feels just like a superset of v1
00:20:23 <jwarendt_> Agree.
00:20:27 <xgerman> SridarK we didn’t do a compatibility layer since we felt nobody was using v1
00:20:36 <SridarK> ok
00:20:44 <mickeys> I think more people are using lbaas v1 than fwaas v1
00:20:59 <sc68cal> true, but there are API clients already in the wild
00:21:17 <sc68cal> my thinking is - build the new boat, then move all the deck chairs over to the new one
00:21:21 <xgerman> mickeys exactly and we didn’t assess that right and got burned a bit
00:21:59 <mickeys> I know internally we are still fighting the lbaas v1 versus lbaas v2 battle, coupled with the heat support issues
00:22:02 <xgerman> sc68cal +1 we make it so both boats can run on the same system and people can move them at their own leisure...
00:22:33 <sc68cal> agree
00:22:37 <jwarendt_> Even if both don't run at same time, avoiding the overlap is useful - ex: db migration scripts.
00:22:45 <SridarK> jwarendt_: +1
00:22:57 <sc68cal> On the microversion front, I talked with kevinbenton a bit and the trouble is we'd have a dependency on work being done in neutron to support microversioning
00:23:18 <sc68cal> so, sadly we have to implement the full v2 API - I was hoping we'd be able to do it in stages and expose microversions to the user
00:23:34 <sc68cal> as actual functionality landed
00:23:56 <sc68cal> but for now looks like it'll have to be where we expose the full api, and in some cases we'll have gaps where it doesn't do anything or returns a Not Implemented error
00:24:04 <xgerman> well, if we are keeping v1 we can mark v2 experimental and do just that
00:24:20 <sc68cal> just like v1 was experimental? ;)
00:24:21 <SridarK> sc68cal: sigh i was hoping that this was a discussion we can have since Kevin wil be there at the midcycle
00:24:41 <xgerman> well, I think we are making good progress here
00:25:08 <xgerman> but the whole micro versioning is a can of worms to begin with
00:25:29 <xgerman> aka since we release as part of neutron any API change mandates a new Neutron microversion
00:26:20 <sc68cal> yeah. It would have been really helpful for fwaas v2, but it would be a lot of work
00:27:04 <SridarK> yes, esp if there are dependent pieces which are also WIP
00:27:11 <xgerman> well, with all the Api changes going on I can almost guarantee each release of Neutron has a new microversion
00:28:43 <sc68cal> anything else on this topic?
00:29:02 <xgerman> no, I think we decided on what we want and how is a technical detail :-)
00:29:16 <sc68cal> #chair SridarK xgerman
00:29:17 <openstack> Current chairs: SridarK sc68cal xgerman
00:29:33 <sc68cal> xgerman: SridarK: if you guys have other topics feel free
00:29:47 <xgerman> besides Happy New Year everybody
00:29:53 <xgerman> nothing from my side
00:30:33 <SridarK> i think we are good on this,  we can thrash out the implementation details
00:32:56 <xgerman> well, should we finish early?
00:33:21 <xgerman> give sc68cal time to code :-)
00:33:26 <SridarK> :-)
00:33:28 <sc68cal> :)
00:34:03 <SridarK> I hope for a productive 4 days next week
00:34:22 <xgerman> +1
00:34:27 <mickeys> +1
00:36:18 <sc68cal> ok then - see you all next week :)
00:36:36 <sc68cal> #endmeeting