18:08:17 #startmeeting networking_policy 18:08:17 Meeting started Thu Jan 8 18:08:17 2015 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:08:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:08:21 The meeting name has been set to 'networking_policy' 18:08:44 #info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#Jan_8th.2C_2014 18:09:16 oh firstly, Happy New Year to all (our first meeting of the year)! 18:09:30 Great job you all for getting the first release out 18:09:38 banix: thanks 18:09:42 good segue 18:09:51 #topic GBP Release 18:10:14 indeed, congratulations to the team! 18:10:39 yeah! 18:10:51 ivar-lazzaro: mageshgv: you guys did some enormous amount of heavy lifting towards the end, BIG thank you! 18:11:10 +2 18:11:58 rkukura is also making excellent progress with the packaging, but will come to that in the next topic 18:12:29 just want to give it a few minutes here to digest exactly what is in the release 18:13:06 we put some very basic release notes here: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/ReleaseNotes/Juno 18:13:29 this is missing the bit on the “external connectivity” model 18:13:33 among other things 18:14:23 so once we add those details and (rkukura is done with the fedora packaging) i think we should be ready to formally announce the release 18:14:25 thoughts? 18:14:26 * ivar-lazzaro looks around 18:14:54 sounds good to me 18:15:24 SumitNaiksatam: I can take care of the external connectivity (or at least I can help if someone else is brave enough to volunteer :) ) 18:15:42 SumitNaiksatam: sounds great, will there any debian package activity for Juno release? 18:15:45 ivar-lazzaro: i will not take the bait ;-) 18:15:56 SumitNaiksatam: :D 18:15:56 yapeng_: hi 18:16:17 yapeng_: yes, mandeep has release the release candidates to PPA 18:16:28 one sec, let me post the link 18:16:57 #link https://launchpad.net/~group-based-policy-drivers/+archive/ubuntu/ppa 18:17:16 SumitNaiksatam: thanks. 18:17:23 you will see the release tarballs here 18:17:37 he just did not get a chance to post it, but its ready 18:17:57 yapeng_: thanks also for your fantastic effort on the ODL front! 18:18:38 yapeng_: and for keeping the devstack branch in sync through all the churn 18:19:02 at some point (sooner than later) we will target the installers as well 18:19:19 but first get the packages in place, and then the installers 18:19:43 currently the easiest way obviously is to use devstack 18:20:07 any thoughts/comments/suggestions/questions on the release details on the process? 18:20:32 Using RDO will be the easiest by the end of today, I think 18:20:44 rkukura: ah ok 18:20:57 rkukura: packaging next topic coming up 18:21:16 #topic GBP Packaging 18:21:46 like i mentioned earlier, rkukura has been deligently pursuing the fedora/RH side of things 18:21:52 rkukura: over to you 18:22:03 OK 18:22:26 The final server package for Fedora rawhide (f22) is at https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/x86_64/os/Packages/o/openstack-neutron-gbp-2014.2-1.fc22.noarch.rpm 18:22:49 So anyone running f22 can just do “yum install openstack-neutron-gbp”. 18:23:43 The other three packages (CLI, UI, automation) are still based on the latest RCs, but should all be updated to final releases today. 18:24:38 The horizon integration works, but the Red Hat Horizon maintainer may think we should be doing some things a bit differently. I’ll continue to work with him on this, but I hope my current approach will be acceptable for now. 18:25:10 So I’m building all these packages for Fedora 20, 21, and 22, as well as EPEL7 which should work on RHEL 7 and CentOS 7. 18:25:49 Until GBP gets incorporated into RDO, these packages can be installed manually on top of an existing RDO deployment on any of those platforms. 18:26:17 I’ll update the RDO GBP wiki instructions once all packages are ready. 18:26:27 rkukura: awesome 18:26:38 Then we’ll work with Red Hat to get the packages included in RDO, which will make things a bit easier. 18:26:40 rkukura: so they did not like the Horizon sub packages? 18:27:30 SumitNaiksatam: The sub package is needed, but they also do some stuff with compressing stuff and may have a different way of installing the panels that what we are currently doing. 18:27:45 rkukura: oh ok 18:27:51 i guess we learn :-) 18:28:29 I think we should be able to update to our release tarballs with the existing approach, then figure out whether we need to change something for in an update to Juno and/or in our Kilo versions. 18:28:53 rkukura: ok 18:28:55 We’ll also need to get working on puppet support that can be used by RDO’s packstack and foreman installers. 18:29:01 That’s it for me. 18:29:15 rkukura: yes, once we have the packages we can do that 18:29:43 rkukura: for puppet, i am guessing we have to push some patches somewhere, to where is that? 18:29:52 rkukura: and for foreman as well 18:30:22 SumitNaiksatam: I think we need to start with patches to the upstream puppet modules 18:30:46 Unless RDO has forks of these, but I think upstream first will be the way to go 18:31:08 rkukura: is upstream in stackforge or something totally different? 18:31:20 Then packstack and foreman will need to be patched to use the updated puppet modules 18:31:34 SumitNaiksatam: Not sure. 18:32:05 Would be great to get someone with some puppet experience involved in that. 18:32:44 rkukura: sure, i had done bit of puppet before, but have forgotten since 18:33:12 rkukura: but we have ratnakar in the team, lets check with him once we are done with the packaging 18:33:25 SumitNaiksatam: right 18:33:30 anyone else wanting to take a stab at it, you are more than welcome! 18:33:58 rkukura but the cool thing is you were able to test end-to-end with the UI packages on fedora, right? 18:34:13 SumitNaiksatam: definitely! 18:34:28 rkukura: nice 18:34:47 any other questions for rkukura or packaging in general? 18:35:08 rkukura: so fedora packages today, right? 18:35:39 that’s the plan, unless the person at Red Hat insists we hold off on the horizon integration 18:35:48 rkukura: ah ok, got it 18:35:59 #topic GBP Kilo 18:36:10 so at this point we have two branches 18:36:14 Anyone want to test the RDO instructions when I’ve updated them? 18:36:27 #undo 18:36:28 Removing item from minutes: 18:36:37 rkukura: definitely 18:36:44 rkukura: you will be updating the wiki page? 18:36:48 yes 18:37:04 #link https://openstack.redhat.com/Neutron_GBP 18:37:08 I’ll update it to include the horizon and heat parts, and with links to the final RPMs 18:37:31 rkukura: I can spend time with RDO testing ... 18:37:43 KrishnaK_: great - thanks! 18:37:57 all installation instructions are currently linked from: #link https://wiki.openstack.org/wiki/GroupBasedPolicy#Try_Group-based_Policy 18:38:37 KrishnaK_: thats great, and also thanks to you for fix bugs, even during the official shutdown! 18:39:11 #topic GBP Kilo 18:39:21 so as i was saying - at this point we have two branches 18:39:39 master continues to Kilo 18:39:49 and we have stable/juno 18:39:56 so any bug fixes can be backported 18:40:23 standard process like other projects 18:40:47 we already have a few blueprints proposed which we delayed on account of this release 18:40:55 is louis or cathy here? 18:41:21 my bad, i have not fixed the specs repo for a UT failure, so havent created the kilo directory yet 18:41:23 will do 18:42:11 i think most of us have been pretty much heads down into the release effort, did not get much chance to plan beyond that 18:42:44 anything to discuss here? 18:43:00 bouthors: hi, great timing 18:43:14 SumitNaiksatam: hi 18:43:24 bouthors: we were just touching on the topic of kilo blueprints 18:43:43 bouthors: we are just wrapping up the Juno release, and Kilo branch is open 18:43:59 bouthors: hopefully we will get to reviewing the specs soon and making progress 18:44:14 bouthors: feel free to post code patches if you have gotten that far 18:45:20 SumitNaiksatam:ok 18:45:32 bouthors: and we can sync up offline as well 18:45:59 #topic Open Discussion 18:46:21 How can we sync up with ODL GBP on L7 extensions ? 18:46:38 bouthors: sure 18:47:02 bouthors: you mean leverage current ODL GBP integration? 18:47:14 yes 18:48:04 bouthors: okay, one thing i would suggest is deploying based on the instructions provided by yapeng: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/InstallODLIntegrationDevstack 18:48:27 SumitNaiksatam: I will have a look 18:48:41 bouthors: once you are at that point, it might be easier to have an informed discussion, since that way you will know exactly what is available today 18:49:04 bouthors: and we can explore how we can extend that in implementation to match the L7 classification spec 18:49:23 bouthors: we can involve some of the folks on the ODL side as well 18:49:30 bouthors: sound okay? 18:49:33 SumitNaiksatam: excellent. This gives me a way to go 18:49:43 SumitNaiksatam: excellent. This gives me a way to go ahead 18:49:48 bouthors: cool 18:50:20 at my end, i wanted to propose an addition to the GBP core team 18:51:03 mageshgv has contributed an enormous amount, and is very familiar the GBP codebase, so i would like to propose him to the GBP core team 18:51:24 SumitNaiksatam: +1! 18:51:26 what does the team think about it? 18:51:31 SumitNaiksatam: +1 18:51:46 SumitNaiksatam: +1 for Mageshgv 18:51:59 SumitNaiksatam: +1 for Mageshgv 18:52:08 ok great 18:52:09 +1 18:52:28 per standard process, i will send out an email to the openstack-dev with the proposal 18:52:42 just want to get some preliminary consensus here 18:52:58 you can respond in the dev ML if you have any objections 18:53:08 thanks again mageshgv for the great work! 18:53:17 thats all i have for today 18:53:20 Thanks Everyone !! 18:53:28 anything anyone else want to bring up? 18:54:20 thanks everyone for joining 18:54:23 see you next week! 18:54:25 bye 18:54:26 SumitNaiksatam: +1 18:54:28 bye 18:54:31 bye 18:54:32 bye 18:54:33 banix: thanks :-) 18:54:35 ciao! 18:54:37 bye 18:54:37 bye 18:54:40 bye 18:54:41 thanks SumitNaiksatam! 18:54:48 #endmeeting