18:07:01 <SumitNaiksatam> #startmeeting networking_policy
18:07:02 <openstack> Meeting started Thu Apr 17 18:07: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:07:03 <mandeep> Hi Group policy folks?
18:07:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:07:05 <openstack> The meeting name has been set to 'networking_policy'
18:07:06 <rkukura> hi
18:07:12 <s3wong> hello
18:07:13 <banix> hi
18:07:21 <s3wong> clearly the channel wasn't booked fully
18:07:25 <banix> s3wong: you knew something about this channel :)
18:07:42 <s3wong> but is it available from 17:00 onward?
18:07:44 <SumitNaiksatam> #topic Policy plugin driver update
18:07:53 <s3wong> banix: yeah - but I didn't stay on :-)
18:08:13 <rkukura> I’m working towards a short term goal:
18:08:13 <SumitNaiksatam> rkukura: sorry for cutting your update
18:08:21 <SumitNaiksatam> rkukura: please go ahead
18:08:33 <rockyg> Uh, Refstack has it 1700-1800
18:08:33 <rkukura> o drive creation of the neutron network, subnet, and port resources via the group API, with all traffic allowed
18:09:02 <s3wong> rockyg: I was thinking of doing #openstack-meeting-alt from 1700-1800
18:09:12 <rkukura> Then s3wong and I can work in parallel from that on mapping the policies
18:09:32 <SumitNaiksatam> rkukura: that sounds like a good plan to me
18:09:34 <rkukura> Does this approach make sense?
18:09:52 <banix> rkukura: thanks yes. is this already in your branch?
18:10:09 <s3wong> rkukura: sounds good. The service stuff would need more clarity before I can do into full-mode coding anyway :-)
18:10:17 <rockyg> s3wong:  Ah.  That would work.  Also an fyi for the RefStack: we stay PST/PDT, so the UTC time shifts with daylight savings time.  But that's our problem.
18:10:29 <rkukura> banix: not yes - I’m building the unit tests on top of what SumitNaiksatam has done, and needed to complete some of that first
18:10:44 <rkukura> s/not yes/not yet/
18:10:46 <thinrichs> rkukura: so are we assuming no one has already created their own networks/ports/etc.?
18:10:59 <banix> rkukura: ok. thanks.
18:11:11 <rkukura> thinrichs: I don’t think we need to assume that, but maybe we can defer handling it
18:11:38 <thinrichs> I was just anticipating objections from the people who like the non-policy API.
18:11:56 <thinrichs> If our first use case demonstrates that the two APIs can be used together, it will squash their objections.
18:12:08 <SumitNaiksatam> thinrichs: yes, thats the goal
18:12:19 <banix> i think that will be the case
18:12:34 <rkukura> thinrichs: Fair enough, but making this really work might require the plugin intercept stuff that we are deferring for a bit
18:12:52 <SumitNaiksatam> rkukura: that’s correc
18:12:56 <SumitNaiksatam> *correct
18:13:08 <SumitNaiksatam> thinrichs: we are iterating towards that goal in terms of implementation
18:13:24 <SumitNaiksatam> thinrichs: hopefully the patch we push upstream will have this from the get go
18:13:39 <rkukura> I’m trying to do as little as possible in the 1st iteration so we can get people working in parallel ASAP
18:13:43 <thinrichs> Understood--I was just thinking about making the demo something that helps everyone understand where we are and where we're headed.
18:14:05 <SumitNaiksatam> thinrichs: absolutely, good to have that thought processing going
18:14:10 <rkukura> thinrichs: I’ll at least include TODO comments for this
18:14:25 <thinrichs> rkukura: good plan.
18:15:03 <rkukura> s3wong: Are you on board with the approach I described?
18:15:29 <s3wong> rkukura: yes (as mentioned above :-) )
18:15:48 <rkukura> s3wong: Sorry, see it now
18:16:04 <rkukura> Anything else on the mapping driver for now?
18:16:05 <s3wong> rkukura: thanks for setting the groundwork
18:16:33 <s3wong> rkukura: seems like it's just you and me :-)
18:17:54 <rkukura> SumitNaiksatam: What’s next on the agenda?
18:18:17 <SumitNaiksatam> rkukura: yeah, are you dont with your update?
18:18:27 <SumitNaiksatam> any questions for rkukura s3wong?
18:18:44 <SumitNaiksatam> ok moving on
18:18:55 <SumitNaiksatam> #topic Python Client and CLI
18:19:22 <SumitNaiksatam> hemanthravi: there?
18:19:26 <hemanthravi> SumitNaiksatam: delayed on this, have CLI for end-poing and epg
18:19:40 <rkukura> SumitNaiksatam: Is it advizable to keep pushing updates to my github branch without squashing?
18:19:45 <hemanthravi> will complete the rest next week
18:19:53 <SumitNaiksatam> hemanthravi: nice, i guess delayed is good, since we are evolving the api
18:19:59 <hemanthravi> caught up with a few thins this week
18:20:06 <SumitNaiksatam> hemanthravi: thanks, end of this week is good
18:20:34 <hemanthravi> might be wed of next week, is that ok
18:20:44 <SumitNaiksatam> rkukura: yeah, we need to sort out the branching
18:20:50 <SumitNaiksatam> rkukura: lets talk about it
18:21:25 <SumitNaiksatam> hemanthravi: strech goal, this weekend? just kidding :-)
18:21:31 <mandeep> rkukura: I am deliquent in sending my update on branch usage, I will do so today
18:21:41 <rkukura> mandeep: OK
18:21:44 <SumitNaiksatam> hemanthravi: perhaps just getting one single resource working wil be good for now
18:21:57 <SumitNaiksatam> hemanthravi: after that it will be mechanical
18:22:05 <hemanthravi> SumitNaiksatam: ok will push that out
18:22:17 <SumitNaiksatam> well hopefully
18:22:23 <SumitNaiksatam> hemanthravi: thanks
18:22:37 <SumitNaiksatam> rkukura: btw, thanks for the earlier update, forgot to mention ;-P
18:22:38 <banix> hemanthravi: thanks
18:22:50 <SumitNaiksatam> #topic Horizon integration
18:23:09 <s3wong> SumitNaiksatam: oh? someone is working on Horizon?
18:23:14 <SumitNaiksatam> hemanthravi: did prasad offer to pursue this? or was it Subra?
18:23:20 <SumitNaiksatam> or neither?
18:24:06 <SumitNaiksatam> okay may be we need to check who the owner for this is
18:24:10 <hemanthravi> SumitNaiksatam: need to check on this, haven't started on it for sure
18:24:22 <SumitNaiksatam> hemanthravi: okay, understand
18:24:32 <SumitNaiksatam> anyone else want to jump in, please feel free
18:24:41 <SumitNaiksatam> #topic Design summit session
18:24:55 <SumitNaiksatam> we have requested a session for this
18:25:04 <SumitNaiksatam> not sure that we will get a time slot, we will know soon
18:25:17 <SumitNaiksatam> if we get it, we will be presenting as a team
18:25:28 <s3wong> SumitNaiksatam: hopefully we will be enable to get a design session ;-)
18:25:49 <SumitNaiksatam> s3wong banix i think you commented on the session
18:25:56 <SumitNaiksatam> thanks! need more of those :-P
18:25:57 <s3wong> SumitNaiksatam: also you, banix, and I will have to prep for the general presentation
18:26:06 <SumitNaiksatam> s3wong: yes, thats the next topic
18:26:17 <SumitNaiksatam> #topic Conference Session
18:26:31 <banix> Shall we try to meet on Monday of the sumit week? just us? may be?
18:26:35 <SumitNaiksatam> banix s3wong and mestery got a conference slot to present this
18:26:53 <SumitNaiksatam> mestery wont be able to do it now, since he is swamped
18:26:57 <SumitNaiksatam> he asked me to step in
18:27:11 <SumitNaiksatam> banix: great idea
18:27:15 <s3wong> banix: will there be slides (I would think so) - so we would have to work on that prior to arriving at the Sumit (at least I hope we do) :-)
18:27:21 <SumitNaiksatam> banix: lets do that
18:27:33 <SumitNaiksatam> s3wong: slides for the conference, yes
18:27:39 <banix> meeting on monday will be for design session and discussions
18:27:41 <SumitNaiksatam> s3wong: most probably not for the design session
18:27:58 <banix> for the general conference talk yes we have to have slides ready before getting there :)
18:28:13 <SumitNaiksatam> for the conference session, yes lets all collaborate as a team again to put a coherent message out there, in terms of what we are trying to do here
18:28:23 <s3wong> SumitNaiksatam: Oh - I was confused, I thought banix was talking about the conference presentation
18:28:32 <SumitNaiksatam> s3wong: yes sure
18:28:53 <SumitNaiksatam> i think the meeting will be good in general, not just for preparing for the conf presentation
18:29:21 <banix> s3wong: yeah that comment was for the earlier topic… too slow :)
18:29:26 <SumitNaiksatam> #topic Open Discussion
18:29:31 <SumitNaiksatam> we have a min
18:29:36 <SumitNaiksatam> anything we missed out?
18:29:44 <s3wong> SumitNaiksatam: meeting time
18:29:56 <SumitNaiksatam> s3wong: nice, thats a pain
18:30:03 <SumitNaiksatam> yeah we will have to change again
18:30:04 <s3wong> clearly #openstack-meeting-alt isn't working for 17:30
18:30:17 <SumitNaiksatam> -meeting-3 is also not available at 17.30
18:30:21 <s3wong> it seems like we may want to do 17:00 on #openstack-meeting-alt
18:30:38 <SumitNaiksatam> or 18.00 on -meeting-3
18:30:38 <banix> or 18:00?
18:30:48 <SumitNaiksatam> banix: yeah ^^^
18:30:50 <s3wong> though 1700 may eat into banix's lunch time :-)
18:30:51 * mestery peeks back in for a bit.
18:30:58 <mestery> I can help review slides as well if you guys want! :)
18:31:08 <s3wong> mestery: great
18:31:09 <banix> yeah i prefer 18:00 but 17:00 is ok if we have to
18:31:21 <mandeep> I vote for 18:00 as well
18:31:26 <SumitNaiksatam> mestery: absolutely, thats a given :-)
18:31:33 <banix> mestery: great; will have to start working on them soon. will keep you updated
18:31:47 <SumitNaiksatam> s3wong, others, 18.00 okay?
18:31:48 <s3wong> seems like 1800 it is then
18:31:56 <rkukura> either should be OK for me
18:32:06 <SumitNaiksatam> rkukura: nice, thanks for being flexible
18:32:13 <hemanthravi> 11 pdt?
18:32:18 <banix> yes for me
18:32:23 <SumitNaiksatam> ok done, thursdays 1800 UTC
18:32:28 <s3wong> hemanthravi: yes, that would be 11am pdt
18:32:31 <SumitNaiksatam> hemanthravi: yes, 11 PDT
18:32:38 <SumitNaiksatam> ok lets call it a wrap
18:32:39 <hemanthravi> yes for me
18:32:42 <SumitNaiksatam> thanks all for attending
18:32:45 <SumitNaiksatam> hemanthravi: great
18:32:46 <banix> thanks everybody
18:32:50 <mandeep> thanks
18:32:50 <SumitNaiksatam> #endmeeting