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