18:03:01 <SumitNaiksatam> #startmeeting networking_policy
18:03:02 <openstack> Meeting started Thu Aug 21 18:03:01 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:03:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:03:05 <openstack> The meeting name has been set to 'networking_policy'
18:03:11 <SumitNaiksatam> rkukura: no, just in time :-)
18:03:21 <rkukura> SumitNaiksatam: Thanks to your reminder!
18:03:40 <SumitNaiksatam> #info reminder - the feature proposal freeze deadline is today
18:04:03 <hemanthravi> SumitNaiksatam, eod PST?
18:04:05 <SumitNaiksatam> anything that we had planned to post and has not yet made it?
18:04:43 <SumitNaiksatam> hemanthravi: ATE (anywhere on earth) #link http://en.wikipedia.org/wiki/Anywhere_on_Earth ;-)
18:04:53 <SumitNaiksatam> ATE -> AOE
18:05:20 <SumitNaiksatam> hemanthravi: so a little more time than PST :-)
18:05:40 <SumitNaiksatam> perhaps good to plan around PST as the deadline though ;-P
18:05:41 <s3wong> Hello
18:05:53 <SumitNaiksatam> s3wong: hi, glad you could make it
18:05:54 <hemanthravi> :)
18:06:16 <SumitNaiksatam> ok any more thoughts/questions on today’s deadline?
18:06:28 <SumitNaiksatam> #info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy
18:06:55 <SumitNaiksatam> #topic Discussion on the path forward
18:07:43 <SumitNaiksatam> so we are currently posting the patches for review into main neutron
18:08:05 <SumitNaiksatam> and we should continue to do that until an explicit change in plans is noted
18:08:39 <SumitNaiksatam> we are all aware of the discussions around incubator/labs and potentially moving this feature to that
18:08:50 <SumitNaiksatam> however, that is still in discussion
18:09:10 <SumitNaiksatam> we can hopefully get closure on that soon
18:09:38 <SumitNaiksatam> any thoughts/comments or any additional information anyone has on this that they would like to share?
18:10:45 <SumitNaiksatam> oh before i forget (or get bumped out) -
18:11:08 <SumitNaiksatam> #chairs rkukura hemanthravi LouisF songole
18:11:50 <SumitNaiksatam> no questions on this topic? :-)
18:12:09 <hemanthravi> SumitNaiksatam, waiting for the decision on the path forward
18:12:50 <SumitNaiksatam> hemanthravi: sure, i definitely feel your frustration and anxiety, and i hope that the decision is something that we collectively take
18:13:05 <SumitNaiksatam> hence wanted to have the discussion here
18:13:24 <rkukura> we really need to get discussion of this neutron-incubator proposal going, here, and on openstack-dev
18:13:36 <SumitNaiksatam> rkukura: +1
18:14:09 <SumitNaiksatam> rkukura: any specific topics that you would want to bring up here?
18:14:20 <rkukura> I think silence is being interpretted as agreement with the details of the current proposal
18:14:33 <hemanthravi> I had couple of concerns reg how the incubator code will be consumed...
18:14:41 <hemanthravi> added this as comments in the etherpad
18:14:45 <rkukura> hemanthravi: Thats my main concern as well
18:15:07 <rkukura> Is the etherpad still actively being use for this?
18:15:45 <hemanthravi> rkukura, not sure but I see some comments posted a few days back
18:15:52 <SumitNaiksatam> rkukura: hemanthravi: yeah i am not sure why the discussion was moved from the etherpad to the wiki page, even before the etherpad was opened up in the ML for discussion
18:16:09 <rkukura> hemanthravi: Havn’t looked at the etherpad since the wiki pages was created
18:17:11 <SumitNaiksatam> i believe also that a path forward here is to actually try this out (creating the repo, to posting the patches, to building the packages) and then factor that experience into any process or policies we formalize on
18:17:25 <rkukura> The current proposal doesn’t seem to address making specific features within the repo consumable by OpenStack distributions.
18:18:04 <songole> SumitNaiksatam: link to the wiki page?
18:18:08 <hemanthravi> https://wiki.openstack.org/wiki/Network/Incubator
18:18:14 <hemanthravi> is this the wiki page?
18:18:23 <SumitNaiksatam> #link https://wiki.openstack.org/wiki/Network/Incubator
18:18:53 <SumitNaiksatam> songole: hemanthravi ^^^
18:19:06 <songole> thanks
18:20:01 <SumitNaiksatam> ok moving on then
18:20:17 <SumitNaiksatam> #topic patches currently in review
18:20:22 <LouisF> i have not seen any heat patches
18:20:30 <SumitNaiksatam> #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches
18:20:51 <SumitNaiksatam> LouisF: do heat patches have the same FPF deadline as Neutron?
18:21:19 <LouisF> SumitNaiksatam: dont know
18:21:25 <SumitNaiksatam> LouisF: okay
18:21:56 <SumitNaiksatam> my understanding was that songole and hemanthravi had also signed up for this earlier
18:22:02 <hemanthravi> LouisF, SumitNaiksatam I think susaant posted the heat patches will check with him
18:22:17 <LouisF> hemanthravi: thx
18:22:17 <SumitNaiksatam> hemanthravi: my bad, yes Susaant posted a patch
18:22:27 <SumitNaiksatam> hemanthravi: can you please inform Susaant to update the wiki page
18:22:30 <hemanthravi> and generally they can lag the feature patch
18:22:41 <hemanthravi> SumitNaiksatam, will do
18:23:03 <SumitNaiksatam> LouisF: this was done more than a week back and right after the client patches in place
18:23:09 <SumitNaiksatam> it kind of slipped my mind
18:23:31 <s3wong> hello
18:23:34 <s3wong> sorry I am late
18:23:38 <SumitNaiksatam> s3wong: welcome back
18:23:43 <mandeep> s3wong: hello
18:23:50 <s3wong> struggled to get onto the network at Big Switch :-)
18:24:17 <songole> heat patches: https://review.openstack.org/#/c/111417 & 111419
18:24:26 <SumitNaiksatam> songole: great thanks
18:24:37 <LouisF> songole: thx
18:24:39 <mandeep> songole: Can you add it to https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches
18:24:45 <SumitNaiksatam> heat patches #link https://review.openstack.org/#/c/111417 https://review.openstack.org/#/c/111419
18:24:48 <mandeep> songole: (Thanks)
18:25:04 <songole> mandeep: yes, I will.
18:25:19 <SumitNaiksatam> LouisF: please review and follow up with Susaant on the missing pieces :-)
18:25:30 <SumitNaiksatam> LouisF: i know you wanted to get involved with this from the beginning
18:26:05 <SumitNaiksatam> #topic Resource Model/API/DB/Plugin Update
18:26:26 <SumitNaiksatam> some last week i rebased the whole series in Neutron, add the db migration, etc
18:26:38 <LouisF> SumitNaiksatam: i will review
18:26:39 <SumitNaiksatam> at that point i think all patches had passed jenkins
18:26:48 <SumitNaiksatam> LouisF: thanks
18:27:06 <SumitNaiksatam> point being that you should consider the series to be fairly current
18:27:14 <mandeep> SumitNaiksatam: +1
18:27:23 <SumitNaiksatam> we dont have the name changes in the series yet
18:27:59 <SumitNaiksatam> but we first want to make sure that the downstream patches like s3wong’s are not affected immediately
18:28:22 <SumitNaiksatam> did not want to disrupt s3wong’s work prior to aug 21st
18:28:58 <SumitNaiksatam> and of course the old story is that the -2 is still present on the first patch (but i dont think that excites anyone anymore!)
18:29:13 <SumitNaiksatam> #topic Mapping Model/Driver Update
18:29:21 <SumitNaiksatam> rkukura: anything new happening here?
18:29:40 <SumitNaiksatam> i did rebase those patches as well
18:29:50 <rkukura> Nothing new here - I’ve been working on trying to get an ML2 BP implemented for today’s FPF.
18:29:59 <SumitNaiksatam> rkukura: ok thanks
18:30:07 <SumitNaiksatam> #topic Security Groups mapping update
18:30:09 <SumitNaiksatam> s3wong: ?
18:30:12 <s3wong> Yes
18:30:15 <rkukura> SumitNaiksatam: Thanks for doing the rebasing! I think there may be one or two comments I’ll want to incorporate.
18:30:28 <s3wong> So I have been trying to get db migration going for my patch
18:30:29 <SumitNaiksatam> rkukura: sure, i just did a mechanical rebase
18:30:48 <s3wong> unfortunately my patch was prior to Ronak's fix on --mysql-server option, thus it fails
18:30:50 <SumitNaiksatam> s3wong: ok
18:31:05 <SumitNaiksatam> is ronak here?
18:31:22 <s3wong> and thus I was trying to rebase to SumitNaiksatam 's latest Contract patch, but couldn't get that to work neither
18:31:49 <s3wong> (git review -d 103789 keeps on trying to get revision 1 instead of revision 7)
18:31:51 <SumitNaiksatam> s3wong: i will work with you on that after this
18:32:05 <SumitNaiksatam> s3wong: i need to understand the steps that you were following
18:32:16 <SumitNaiksatam> s3wong: lets keep that issue aside
18:32:22 <SumitNaiksatam> s3wong: are you set otherwise?
18:32:31 <s3wong> and the last resort I attempted was to just get latest neutron on devstack, checkout SumitNaiksatam 's contract revision 7, and manually patch my stuff in to get db migration to work
18:32:42 <s3wong> but for that I got "Database not up to date"
18:32:47 <SumitNaiksatam> s3wong: ok
18:32:53 <s3wong> so exhausted all options at this moment :-)
18:33:05 <SumitNaiksatam> s3wong: but are you able to run UTs in your setup?
18:33:15 <s3wong> SumitNaiksatam: yes, UTs are fine
18:33:19 <s3wong> SumitNaiksatam:
18:33:22 <hemanthravi> SumitNaiksatam, when you get some time can you send out an e-mail for the list of steps for the rebase.. our driver patch ended up posting on all the ancestors
18:33:24 <SumitNaiksatam> s3wong: ok good
18:33:41 <hemanthravi> a week ago
18:33:42 <s3wong> SumitNaiksatam: but can't get patch off of WIP unless I get DB migration
18:33:43 <SumitNaiksatam> hemanthravi: that cannot be avoided (i dont think you did anything wrong)
18:34:00 <SumitNaiksatam> s3wong: ok we will work on that after this meeting, sound okay?
18:34:02 <hemanthravi> SumitNaiksatam, :(
18:34:12 <SumitNaiksatam> hemanthravi: but we will discuss that as well
18:34:33 <s3wong> SumitNaiksatam: also, my current patch does NOT have rule/classifier/actions update support yet
18:35:12 <SumitNaiksatam> s3wong: you mean only “update”, right?
18:35:54 <s3wong> well, creating rules and attaching to contracts --- in that sequence --- works
18:36:05 <SumitNaiksatam> s3wong: ok
18:36:11 <s3wong> SumitNaiksatam: but I don't have mapping of policy-rule => SG rules
18:36:34 <SumitNaiksatam> s3wong: i am a little confused
18:36:47 <SumitNaiksatam> s3wong: so what are you mapping to what?
18:36:55 <s3wong> SumitNaiksatam: thus can't update / delete individual ones, since the mapping driver doesn't maintain the mapping
18:37:19 <SumitNaiksatam> s3wong: so you mean you are not persisting the mapping association?
18:37:49 <s3wong> SumitNaiksatam: when you create classifier/actions -> rules and associate with contract, then create contract with those, that sequence works as contract has reference for me to create those entries for SG
18:38:14 <s3wong> SumitNaiksatam: but since I don't have the mapping of individual rules -> SG rules, update doesn't work
18:38:22 <SumitNaiksatam> banix: welcome, thought you were going to be MIA today ;-)
18:38:44 <banix> SumitNaiksatam: I am :) 6000 miles or so sawy
18:38:52 <banix> away
18:39:12 <SumitNaiksatam> s3wong: okay maybe this is a longer discussion for the lenght of this meeting
18:39:23 <s3wong> SumitNaiksatam: sure
18:39:31 <SumitNaiksatam> s3wong: lets sync up on this after we get to resolving your rebase issues
18:39:39 <SumitNaiksatam> banix: europe?
18:39:41 <s3wong> SumitNaiksatam: sure
18:40:01 <SumitNaiksatam> #topic API Intercept
18:40:05 <SumitNaiksatam> kevinbenton: there?
18:40:15 <SumitNaiksatam> kevinbenton: were you able to sync up with rkukura?
18:40:16 <kevinbenton> SumitNaiksatam: hi
18:40:31 <banix> SumitNaiksatam: 6000 miles from New York. Tehran, Iran to be more specific. Visiting my parents.
18:40:31 <kevinbenton> SumitNaiksatam: yeah, we just decided to lift the WIP to get feedback on it
18:40:50 <SumitNaiksatam> banix: oh wow!
18:41:15 <SumitNaiksatam> kevinbenton: ok nice, thanks for staying on message on this, and ploughing through
18:41:22 <mandeep> kevinbenton: +1
18:41:38 <kevinbenton> SumitNaiksatam: no prob
18:41:47 <SumitNaiksatam> rkukura: so you are okay with the current state of the patch?
18:41:57 <SumitNaiksatam> #link https://review.openstack.org/#/c/109901
18:42:06 <rkukura> Its been a long time since I looked at it. Need to re-review.
18:42:17 <SumitNaiksatam> rkukura: ok
18:42:23 <rkukura> But it is in by the FPF!
18:42:43 <SumitNaiksatam> rkukura: yes, thanks to kevinbenton, yay!
18:42:53 <SumitNaiksatam> #topic CLI/Client Update
18:42:58 <SumitNaiksatam> songole: hi
18:43:07 <SumitNaiksatam> any new updates?
18:43:19 <SumitNaiksatam> you got some feedback last week
18:43:23 <SumitNaiksatam> how is that coming along?
18:43:32 <songole> Naming change?
18:44:09 <SumitNaiksatam> yeah, but that hasn’t made it to the API
18:44:19 <songole> I would wait for plugin changes
18:44:21 <SumitNaiksatam> but things like the “gp-“ prefix
18:44:58 <songole> prefix change I haven't incorporated. I would all the changes at once
18:45:09 <SumitNaiksatam> songole: okay makes sense
18:45:31 <songole> Magesh is adding unit tests
18:45:33 <SumitNaiksatam> #topic Tempest tests
18:45:43 <SumitNaiksatam> songole: nice, thanks for the update
18:45:54 <SumitNaiksatam> i dont have any updates on the tempest tests
18:46:11 <SumitNaiksatam> will add more API tests at the earliest
18:46:24 <SumitNaiksatam> #topic Vendor/Open Source Controller Drivers
18:46:42 <SumitNaiksatam> so at this point i know one convergence has posted their driver
18:47:08 <hemanthravi> will do a rebase and remove the wip today
18:47:09 <SumitNaiksatam> hemanthravi songole: nice work you guys in at least meeting the FPF
18:47:17 <SumitNaiksatam> hemanthravi: great
18:47:28 <SumitNaiksatam> anyone else want to discuss their drivers?
18:47:49 <SumitNaiksatam> i am guessing that the incubator discussion sucked the momentum out of this effort a little bit
18:48:11 <banix> We are going to wait and see how the incubator discussion pans out
18:48:17 <SumitNaiksatam> banix: ok sure
18:48:36 <banix> great to see the driver by hemanthravi though!
18:48:42 <SumitNaiksatam> i think the code will be useful regardless of where it lands
18:49:10 <SumitNaiksatam> #topic Horizon update
18:49:31 <SumitNaiksatam> not sure if ronak is here
18:49:54 <SumitNaiksatam> but i think he updated the patch a week ago
18:50:08 <SumitNaiksatam> and i think abishek was reviewing it from the horizon side
18:50:20 <SumitNaiksatam> #link https://review.openstack.org/#/c/93590/
18:50:32 <SumitNaiksatam> LouisF: did you get a chance to take a peek at this?
18:51:24 <SumitNaiksatam> perhaps not
18:51:28 <SumitNaiksatam> #topic open discussion
18:51:37 <SumitNaiksatam> we might actually finish a little earlier today
18:51:50 <SumitNaiksatam> anything anyone else wants to discuss?
18:52:09 <LouisF> SumitNaiksatam: yes
18:52:12 <SumitNaiksatam> otherwise i can go back to s3wong and work with him on the rebase issue
18:52:14 <SumitNaiksatam> LouisF: thanks
18:52:47 <rkukura> I’m curious, if we go with the incubator option, whether we would want to base our development on the juno version of the neutron repo for a while, rather than tracking master? Would that enable vendors to complete their drivers and make them available to early adopters using the juno release?
18:53:14 <SumitNaiksatam> rkukura: that makes sense to me
18:53:20 <hemanthravi> rkukura, +1
18:53:27 <SumitNaiksatam> rkukura: however would that mean that we would have to wait for juno to release?
18:53:31 <mandeep> rkukura: I agree, that is very helpful
18:53:32 <SumitNaiksatam> rkukura: i hope not
18:53:52 <rkukura> SumitNaiksatam: I mean once Juno is tagged, and open for Kilo development
18:53:54 <SumitNaiksatam> can we base it off J3, for instance
18:53:54 <banix> well that seems the logical way of doing this
18:54:11 <mandeep> SumitNaiksatam: I assume that by "tracking Juno" you imply "tracking Juno Milestones"
18:54:13 <SumitNaiksatam> rkukura: yes, but that seems a long way away
18:54:38 <SumitNaiksatam> mandeep: i did not mention about tracking Juno
18:54:46 <SumitNaiksatam> mandeep: i think rkukura mentioned about tracking master
18:54:49 <rkukura> If this is what makes most sense, we need to influence the neutron-incubator proposal to support this sort of thing.
18:55:18 <SumitNaiksatam> rkukura: so lets start we had to start on the incubator/labs today
18:55:24 <mandeep> SumitNaiksatam: Ooops ;-)
18:55:31 <banix> I think vendors will have different approaches, some try to follow all cycle milestones some stick to the final release
18:55:34 <SumitNaiksatam> rkukura: we would still need to base it off the master, right?
18:55:36 <rkukura> We could also do ongoing development on labs master, tracking neutron master, and back-port to stable-juno
18:55:44 <SumitNaiksatam> rkukura: we dont have J release tagged yet
18:56:30 <rkukura> I’m making the assumption we will have something merged to the labs repo before juno ships, but it will need more work
18:57:07 <s3wong> rkukura: SumitNaiksatam: is the labs package going to be released the same time as Juno release?
18:57:28 <rkukura> So does consuming that ongoing work mean using neutron-master post-juno, or can it be consumed as an add-on to juno neutron?
18:57:37 <SumitNaiksatam> s3wong: i think that is still worked on
18:57:54 <SumitNaiksatam> rkukura: good point
18:58:00 <rkukura> If this is something we care about, we need to get discussion going on the openstack-dev ML
18:58:05 <SumitNaiksatam> rkukura: that would depend on what strategy we adopt
18:58:25 <SumitNaiksatam> rkukura: so we will need to start with the dependency on the master
18:58:53 <SumitNaiksatam> rkukura: but i think per your suggestion, we eventually get to a point where base the development on the labs off the milestones
18:58:54 <mandeep> rkukura: Yes, I agree
18:59:05 <SumitNaiksatam> rkukura: i think you are explicitly pinning that to the stable branch
18:59:14 <mandeep> rkukura: (on starting a larger discussion quickly)
18:59:28 <SumitNaiksatam> rkukura: i am wondering if this should be more granular, and we can base that of the milestone releases as well (like K1)
18:59:59 <rkukura> I’m just trying to get everyone thinking about the options for how we’d go forward with the labs repo, how we’d deliver stuff, and what might need changing in the current proposal.
19:00:09 <SumitNaiksatam> rkukura: so in that sense the labs releases can lag the neutron master releases by one milestone
19:00:45 <SumitNaiksatam> rkukura: and i am not sure that anyone should agree to any one proposal as is
19:00:59 <rkukura> If the goal is getting beta versions of new features into the hands of early adopters that are using packaged juno releases, lagging might make sense
19:01:06 <SumitNaiksatam> rkukura: i believe this is going to be a learning and evolving experience (and we would need to factor that feedback in)
19:01:38 <SumitNaiksatam> true to our tradition, we have gone over now :-)
19:01:45 <SumitNaiksatam> lets wrap it here
19:01:57 <SumitNaiksatam> thanks everyone
19:01:58 <rkukura> I’d hate to see the proposal adopted with its focus on PyPI as the release mechanism, supporting multiple neutron versions simultaneously (without branching), etc.
19:02:05 <SumitNaiksatam> rkukura: +1
19:02:14 <rkukura> thanks SumitNaiksatam!
19:02:39 <banix> agree but that discussion seems to be happning outside the ML I am afraid ….
19:02:52 <SumitNaiksatam> rkukura: my suggestion would be that we should treat this as an evolving process and formulate the policies as we go along
19:03:06 <rkukura> banix: I’m not sure the discussion is really happening at all ;)
19:03:18 <SumitNaiksatam> but we need to get started, else we are discussing in a vaccuum
19:03:20 <mandeep> banix: Yes, let us follow up on that issues on the ML thread
19:03:26 <rkukura> SumitNaiksatam: +1
19:03:37 <banix> rkukura: i wont be surprised if that is the case.
19:03:58 <SumitNaiksatam> ok thanks all
19:04:07 <banix> sorry for logging in in the middle of the call. talk to you all later.
19:04:08 <SumitNaiksatam> #endmeeting