18:03:11 #startmeeting networking_policy 18:03:13 Meeting started Thu Mar 3 18:03:11 2016 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:03:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:03:16 The meeting name has been set to 'networking_policy' 18:03:26 #info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#March_3rd.2C_2016 18:03:41 #topic Bugs 18:04:25 I did not see any critical issues, but there was one significant one reported by magesh yesterday #link https://bugs.launchpad.net/bugs/1552176 18:04:26 Launchpad bug 1552176 in Group Based Policy "GBP Plumbing - Gateway port attached to a VM does not get IP through DHCP" [High,Confirmed] - Assigned to Magesh GV (magesh-gv) 18:04:55 i havent seem a patch but i am guessing he is working on it 18:05:24 rkukura: ivar-lazzaro: any other critical bug on your radar that needs immediate attention? 18:05:44 nope 18:05:51 no 18:05:58 ok 18:06:03 #topic Testing 18:06:25 i noticed that the stable/liberty and stable/kilo UTs were breaking last night 18:06:45 SumitNaiksatam: just saw your email on that 18:06:54 rkukura: yeah, was just going to say 18:07:08 ivar-lazzaro: whenever you get a chance can you take a quick look? 18:07:56 looks like mainly/only APIC failures, right 18:08:01 rkukura: yeah 18:08:04 File "/home/jenkins/workspace/gate-group-based-policy-python27/.tox/py27/src/python-opflexagent-agent/opflexagent/type_opflex.py", line 80, in get_mtu 18:08:04 if physical_network in self.physnet_mtus: 18:08:05 AttributeError: 'OpflexTypeDriver' object has no attribute 'physnet_mtus' 18:08:08 songole: hi 18:08:15 SumitNaiksatam: hello 18:08:48 songole: wanted to follow up if magesh is working on #link https://bugs.launchpad.net/bugs/1552176 18:08:49 Launchpad bug 1552176 in Group Based Policy "GBP Plumbing - Gateway port attached to a VM does not get IP through DHCP" [High,Confirmed] - Assigned to Magesh GV (magesh-gv) 18:09:32 SumitNaiksatam: ok will give a look 18:09:38 ivar-lazzaro: thanks 18:09:44 I will check with him today. 18:09:53 songole: thanks, he assigned it to himself 18:09:59 #topic Packaging 18:10:18 on the mitaka sync front we merged all the patches across the repos 18:10:24 thanks all for reviewing 18:10:26 SumitNaiksatam: Nice! 18:10:59 some UI issues cropped up but we were able to post the fixes within the sync patches themselves 18:11:08 thanks to Ank from songole’s team 18:11:47 rkukura: as before i did not do any more stable releases since the feeling was that patches were still coming in 18:12:06 not sure they’ll ever stop ;) 18:12:14 rkukura: lol! 18:12:39 rkukura: anything you wanted to discuss at your end? 18:12:43 I have been trying to get an update on the RDO/delorean stuff from apevec @ Red Hat, but no luck 18:12:51 rkukura: ah ok 18:13:09 rkukura: being synced with mitaka now, we should be in reasonable shape, right? 18:13:13 I’ll keep trying, and want to let him know if can be turned on for master now as well 18:13:18 I think so 18:13:23 We’ll need to keep it working 18:13:27 rkukura: right :-) 18:14:06 the sanity branches are being rebased on a daily basis, so we will catch things at least in a day’s window 18:14:06 I don’t think Fedora packaging is relevant any more, but will see what else needs to be done to update RDO/CentOS packages 18:14:13 rkukura: okay 18:14:27 We’ll eventually want to deal with puppet/packstack/director integration 18:14:42 that’s it from me 18:14:43 rkukura: ah, thats significant work 18:14:47 rkukura: thanks 18:15:09 oh btw, the mitaka devstack has also been updated 18:15:11 I’m hoping some of the work being done around APIC will be reusable for the ref impl as well 18:15:22 rkukura: that would be nice 18:15:51 hi 18:15:55 so by installing the devstack from the master here: #link https://github.com/group-policy/gbp-devstack/tree/master 18:16:16 you should be able to get GBP mitaka with the rest of OpenStack Mitaka 18:16:19 igordcard_: hi there 18:17:09 at some point the goal is to move all of this into a devstack plugin, but that hasnt happened yet 18:17:26 #topic Design Specs 18:17:39 Qos Support #link https://review.openstack.org/#/c/275358/ 18:17:51 igordcard_: any updates at your end? 18:17:52 I couldn't update the spec to be "reviewable" 18:17:59 igordcard_: okay np 18:18:14 igordcard_: question for you (and for the rest of the team as well) 18:18:15 will do it today though 18:18:34 igordcard_: you mentioned that you wanted to initially experiment with this approach (using NSP) 18:18:46 would you prefer to work on a feature branch for this? 18:18:59 SumitNaiksatam: yes I was planning to update it to reflect that initial PoC 18:19:17 and move the reamining ideas to the alternatives section 18:19:41 igordcard_: okay, i can create a feature branch from the current master that will be dedicated for your work 18:19:57 the only overhead is that we will have to keep syncing the feature branch from the master 18:20:22 but this is standard practice 18:20:32 SumitNaiksatam: hmm, okay, cool... will NSP suffer many changes soon? 18:20:52 igordcard_: i dont think anything changes in the API/model any time soon 18:21:21 igordcard_: most of the work that i know is being planned either on the policy driver’s side or related to NFP 18:21:43 okay 18:21:55 igordcard_: so for the work that you are doing, i think you can expect stablility for the near future 18:22:11 SumitNaiksatam: nice :) 18:22:37 songole: we had a good chat with the team in person last week 18:22:49 songole: i believe hemanth will update the spec 18:23:20 SumitNaiksatam: Yes, hemanth will be posting a new patch today. 18:23:21 songole: any other updates at your end or any design discussion you want to have today? 18:23:55 SumitNaiksatam: implementation is progressing. I don't see any design issues at this time. 18:24:12 songole: okay 18:24:27 songole: any other follow up from the discussion last week? 18:24:34 regarding the “workers” patch? 18:24:50 #link https://review.openstack.org/#/c/282292 18:25:20 We looked at taskflow. Adopting it at this time would be quite some change. 18:26:10 songole: okay, is it a matter of change or a matter of suitability? 18:26:25 it is both. 18:26:30 okay 18:27:07 songole: what about the persistent queue part? 18:28:17 We like to submit the patches first and then look at redis queue as an option. 18:28:25 songole: okay 18:28:43 #topic Open Discussion 18:29:19 i believe the speaker sessions for austin will be announced over the next few days 18:29:42 did anyone get any notification yet? 18:30:08 I have not, but heard 3rd hand that someone else did 18:30:36 rkukura: ah okay 18:30:58 anything else for today? 18:31:28 alrighty, thanks all for joining! 18:31:34 see ya next week! 18:31:36 bye! 18:31:38 bye 18:31:41 thanks SumitNaiksatam! 18:31:46 #endmeeting