18:02:08 #startmeeting networking_policy 18:02:09 Meeting started Thu May 28 18:02:08 2015 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:12 The meeting name has been set to 'networking_policy' 18:02:27 #info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#May_28th.2C_2015 18:03:06 hope everybody is settled back! 18:03:17 Vancouver was too much fun ;-P 18:03:22 yapeng: hi 18:03:37 SumitNaiksatam:hi 18:03:58 #topic Bugs 18:04:09 #link https://bugs.launchpad.net/group-based-policy/+bug/1432779 18:04:09 Launchpad bug 1432779 in Group Based Policy "redirect actions don't work with external policies" [Critical,In progress] - Assigned to Ivar Lazzaro (mmaleckk) 18:04:17 sorry, i lost track of this one 18:04:31 ivar-lazzaro: this is pending for stable/juno? 18:04:50 SumitNaiksatam: I thought it was merged 18:05:14 yeah on the master 18:05:26 #link https://review.openstack.org/#/c/170972/ 18:05:34 i dont see that we tagged it for backport 18:05:47 ivar-lazzaro: ah cool 18:05:58 This is one that needs a proper migration before merging to stable/juno 18:06:15 rkukura: the proper migration was merged afterwards 18:06:31 ivar-lazzaro: right 18:06:35 OK 18:06:40 i need to update the launchpad 18:06:43 rkukura: or is it still pending? 18:06:44 status 18:06:47 So we’d need to backport both 18:07:23 The bug says partially solved because we don't know yet whether we need to enable service providing too 18:07:45 ivar-lazzaro: i was running into this: #link https://bugs.launchpad.net/group-based-policy/+bug/1456058 18:07:45 Launchpad bug 1456058 in Group Based Policy "Service chain update results in sharing error" [High,New] 18:07:45 sorry, late 18:07:50 s3wong: hi 18:08:08 hello 18:08:10 ivar-lazzaro: i believe we ran into the same one for the hands-on-lab as well 18:08:19 rkukura: #link https://review.openstack.org/#/c/175556/ 18:09:08 SumitNaiksatam: that error is policy related apparently 18:09:09 ivar-lazzaro: right 18:09:37 ivar-lazzaro: okay i will try to dig into it 18:09:52 SumitNaiksatam: need to see whether your system didn't have the policy files properly merged or that policy is missing altogether 18:10:15 ivar-lazzaro: i think i had the policy files, but let me check again 18:10:28 SumitNaiksatam: thanks 18:10:31 file* (merged file that is) 18:10:57 any other critical or high priority bugs to discuss? 18:11:14 there are a bunch of high priority ones still pending, but we have mostly discussed those before 18:11:27 we need to fix those though ;-) 18:11:44 is magesh around? 18:11:57 i think #link https://bugs.launchpad.net/group-based-policy/+bug/1421413 is fixed 18:11:57 Launchpad bug 1421413 in Group Based Policy "network-service-policy cannot be reused" [High,In progress] - Assigned to Magesh GV (magesh-gv) 18:12:14 ok moving on 18:12:32 #topic Functional and Integration tests 18:12:50 no update at my end in the last couple of weeks 18:13:11 we did some level setting and had discussions during the design sessions 18:13:17 need to follow up on that 18:13:47 the integrations gate job was breaking on this patch: #link https://review.openstack.org/#/c/167174/ 18:14:03 it was not failing the tests, but due to a setup issue 18:14:29 i tried to investigate but so far havent made progress 18:14:45 i believe this happened after the new pip version release 18:14:54 in case you start seeing this on your patches as well 18:15:18 #topic Packaging Update 18:15:42 we belatedly released k3 on tuesday 18:15:58 SumitNaiksatam: thanks! 18:16:05 this was mostly for rkukura to be able to test our packages with the rest of the kilo release 18:16:07 rkukura: sure 18:16:16 rkukura: over to you for any updates 18:17:05 I’m not able to download the tarballs from launchpad - times out waiting on launchpadlibrarian.net. 18:17:22 I suspect this may be a Cisco VPN issue - same happens with older packages as well. 18:17:42 I need to try without the VPN after this meeting. 18:17:57 rkukura: okay, lets connect offline, i can give you the signed images 18:18:03 One new development is I discussed using “delorean” with Ihar from Red Hat. 18:18:05 or unsigned ones 18:18:14 rkukura: ok good 18:18:41 SumitNaiksatam: I’ll need to put working links for the packages in the RPM spec files. 18:19:02 delorean is their system for doing CI on OpenStack projects. 18:19:45 It tracks the git repos and builds new RPMs whenever there is a commit. 18:20:02 rkukura: is that like OpenStack infra and jobs therein? 18:20:28 Yes, I think it can run test suites against the packages as well, but I’m not sure. 18:20:35 rkukura: okay 18:20:49 rkukura: so we are planning to introduce a CI job for GBP? 18:20:59 They would like us to integrate with delorean, and then to generate the fedora, RDO, and RHEL OSP packages from that. 18:21:43 We need to followup on this. Any reason the existing system tests couldn’t be automatically run against packages? 18:21:43 rkukura: okay 18:22:04 rkukura: we have two sets of tests 18:22:45 one is the gbpfunc tests are already being run against packages in our local environment 18:22:51 so it should be possible to use those 18:23:15 the other set of tests are via the exercise scripts (which are not really tests) 18:23:28 those expect a devstack like environment 18:23:36 but perhaps we could adapt those if required 18:23:49 Sounds like the gbpfunc tests would be most appropriate to start with 18:23:54 but i think we can get sufficient coverage by just running gbpfunc 18:23:57 rkukura: yeah 18:24:30 rkukura: lets connect offline on the logistics of doing this 18:24:40 thanks for keeping us updated on this development 18:24:51 Anyway, I’m hoping to get the fedora packages updated to kilo-3 by next week’s meeting, and then let Red Hat update RDO. We can do delorean integration afterwards. 18:25:03 rkukura: sounds reasonable 18:25:08 rkukura: anything else on the packaging front? 18:25:15 That it from me. 18:25:24 rkukura: thanks 18:25:27 #topic Docs 18:25:28 How about ubuntu packages? 18:25:34 #undo 18:25:35 Removing item from minutes: 18:25:44 rkukura: i believe amit in our team is working on it 18:25:52 Any updates? 18:25:54 i will request him to join the next week and give an update 18:25:59 Thanks 18:26:15 #topic Docs 18:26:29 we are getting requests for developer documentation 18:26:43 specifically on the REST API 18:26:49 and we are really behind on this 18:27:25 there are developers who want to start building on top of GBP by leveraging the API, however we dont have the right documentation to get them started 18:27:38 so anyone wanting to help towards this would be a big help 18:27:59 there is also a request for a python SDK 18:28:15 this exists for other integrated projects 18:28:24 in python-openstacksdk 18:28:47 i believe we can leveragge python-openstacksdk as a library and independently build our own SDK 18:28:56 for python bindings 18:29:06 anyone wanting to work on this please let me know 18:29:16 SumitNaiksatam: I can help on the documentation, if no one else.. 18:29:32 Yi: awesome, thanks for taking it on, i will connect with you offline 18:29:45 SumitNaiksatam: sure 18:29:51 Yi: there is another person who offered to jump in on this (after the hands-on lab) 18:30:04 lets sync with him and see how we can get some team work going on this 18:30:12 good 18:30:44 Yi: thanks 18:30:54 #topic Vancouver Summit Review 18:31:03 #link https://etherpad.openstack.org/p/gbp-liberty-design-summit 18:31:25 in my opinion we had a pretty productive design summit as far as GBP is concerned 18:31:38 however we had a lot more to discuss than the available time 18:31:53 and also the etherpad was acting on us, so could not record a lot of the details 18:32:31 we can spend a few minutes here on following up on any of what was discussed during the summit, or anything big that we missed out 18:32:34 or if anyone has any follow up questions/comments 18:34:31 towards the end of the etherpad we tried to track down the priority items and assign names for action items 18:34:52 feel free to jump in and update the etherpad if you have interest in any of those items 18:35:35 #topic Features 18:35:47 service chain plugin/driver refactor: #link https://review.openstack.org/#/q/status:open+project:stackforge/group-based-policy+branch:master+topic:bp/node-centric-chain-plugin,n,z 18:35:53 ivar-lazzaro: over to you 18:36:08 SumitNaiksatam: thanks 18:36:50 The implementation is still ongoing, we are mostly missing the first Node Driver implementation 18:37:22 The base architecture is there, and the first plumber as well. Hopefully it'll be ready for merging in the next couple of weeks 18:38:00 ivar-lazzaro: has there been any internal discussion on any change of the workflow of instantiating a chain? 18:38:04 ivar-lazzaro: okay 18:38:06 igordcard_ is also giving a look at bringing straffic steering into the picture, which is definitively exciting' 18:38:47 ivar-lazzaro: i reviewed the first two patches in the chain (no pun intended) again 18:38:55 ivar-lazzaro: mostly looks great, had some nit comments 18:39:01 ivar-lazzaro: is this the first plumber you refer to? https://review.openstack.org/#/c/181814/ 18:39:13 igordcard_: can you elaborate about the change in workflow? 18:39:20 igordcard_: nothing major. There are still ongoing discussions on how the service should be plumbed together depending on their type 18:40:01 igordcard_: yes. That's the basic implementation that just creates Service Targets based on the Node request 18:40:12 igordcard_: without really knowing anything about the whole chain 18:40:24 SumitNaiksatam: how the various responsibilities are assigned, from consuming service profiles to materializing a specific node 18:40:31 it's definitively pretty limited 18:40:42 ivar-lazzaro: thanks 18:40:48 igordcard_: ah ok, the service profile is the only new resource 18:41:09 ivar-lazzaro: for the ongoing discussion, is it recorded in the blueprint or spec? 18:41:09 igordcard_: and needs to be available before the node is created 18:41:43 Yi: good point, any changes to the design should go back as updates into the spec 18:42:19 however i think the ongoing discussion relates to the “plumbing” which is more of an evolving implementation detail 18:42:21 Yi: mostly it's just things discussed in person in Vancouver. That's not a design change though, it's mostly to understand how future plumbers should behave and what info they need 18:42:31 SumitNaiksatam: thanks - just wanted to get on par of any, possible, changes you might have discussed 18:42:51 igordcard_: not that i am aware of beyond what is documented in the spec 18:43:09 Yi: and we are still nowhere close to a conclusion :) hopefully I can bring something to the table in the next few weeks for discussion 18:43:17 ivar-lazzaro: any blockers for you at this point (apart from the reviews)? 18:43:39 SumitNaiksatam: nope 18:43:44 ivar-lazzaro: okay good 18:43:53 any other questions for ivar-lazzaro on this? 18:44:15 ivar-lazzaro: thanks for this piece of the update 18:44:16 yeah, in the next few weeks I will come up with a traffic-steering-only plumber together with a list of issues and other challenges it poses :) 18:44:29 ivar-lazzaro: awesome :-) 18:44:38 ivar-lazzaro: awesome 18:44:45 igordcard_: awesome 18:44:46 igordcard_: ^^ 18:44:49 finally :-) 18:44:53 ahah 18:44:54 SumitNaiksatam: eheh, that was hard 18:45:04 difficult* 18:45:10 the client is smarter than i imagined 18:45:27 ususally it tab completes by alphabetical order 18:45:44 but apparently it also remembers the last use 18:45:46 anyway 18:46:03 i dont think magesh is around for the floating ip patch discussion 18:46:19 my request to him was to add an exercise script before we can move forward with the patch 18:46:35 we need to validate that it works end-to-end, and also for everyone to understand the workflow 18:46:52 i am referring to #link https://review.openstack.org/#/c/167174/ 18:47:44 yapeng: yi: regarding the independent server work 18:47:59 we can start work on that right away since we have the feature branch available 18:48:09 ok 18:48:23 so lets get the discussion going on that 18:48:40 sure 18:48:48 yapeng: yi: thanks 18:49:11 #topic “An improved Horizon UI” 18:49:16 igordcard_: over to you 18:49:54 the horizon ui currenty used by gbp is not bad but there are some things that could be improved 18:50:28 from the hands-on lab there was some feedback on some pieces that were not intuitive or rather complicated 18:50:48 igordcard_: very much agree 18:50:59 igordcard_: +1 18:51:02 one of the things that could be improved is the service chaining ui 18:51:35 there is a person from Instituto de Telecomunicações that is actually developing a UI meant for service chaining (which then applies to our current traffic steering impl) 18:52:21 let me introduce you to Mario, mcar - you can show them the screenshot and introduce yourself of course :) 18:52:48 mcar: hi welcome to the team! 18:52:57 mcar: hi! 18:53:02 hi guys I did a short video https://www.youtube.com/watch?v=fHD0JEbjKuU&feature=youtu.be 18:53:30 mcar: oh, it's actually a video! 18:53:52 mcar: hi! 18:54:10 mcar, the gui looks cool :) 18:54:17 * SumitNaiksatam watching the video 18:54:27 thanks 18:54:29 if you think it is interesting and beneficial for GBP to have such an interface, he can forward with it and adapt it to GBP 18:54:52 mcar: indeed pretty cool 18:54:53 mcar: looks very nice! driving the whole workflow (not just SC) that way would be awesome 18:55:12 ivar-lazzaro: +1 18:55:13 mcar: in fact i think this can be extended to the GBP model as well 18:55:19 provide/consume, etc 18:55:33 mcar: it's very nice. But I do have a question on it 18:55:40 Yi: yes please 18:56:00 ask 18:56:15 from workflow point, I thought a SFC is defined as abstract profile first? 18:56:26 SumitNaiksatam: yeah I agree - that interface is not a closed fully-developed product, so it's still evolving and would adapt to the GBP model properly when meant for that 18:56:37 and then map the abstraction to the VM instance? 18:57:04 Yi: correct 18:57:31 i think those things can be adapted in the context of the GBP model 18:57:37 Yi: I think the concept mcar brought is not "GBPfied" yet 18:57:52 ivar-lazzaro: correct 18:58:01 Yi: yes, it's a matter of extending those blocks to allow changing the service types - or doing any other thing that requires further discussion 18:58:16 but that is the idea we are trying to show - a drag-and-drop-like UI for service chaining 18:58:55 igordcard_: yes, i believe we always wanted to do something like this 18:59:00 ivar-lazzaro: exactly, it's not GBPfied... it is only meant for traffic steering between VMs 18:59:19 SumitNaiksatam, ivar-lazzaro, igordcard_, mcar: yes. the idea is drag and drop 18:59:21 mcar: fwiw, also take a look at this patch: #link https://review.openstack.org/#/c/183634/ 18:59:35 mcar: it is prettyfying the display of the chain 18:59:47 Yi: correct 19:00:21 given the dirt in mcar's hands, it is potentially easier for him to fulfill this work for GBP then figuring out ourselves how to do that 19:00:31 igordcard_: :-) 19:01:06 okay we are the hour 19:01:10 mcar: igordcard_: lets discuss offline how to make progress with this 19:01:19 anything else we missed today? 19:01:38 SumitNaiksatam: GBP new name? 19:01:39 alright, thanks all! 19:01:51 ivar-lazzaro: ah 19:02:19 yes please do think about it 19:02:40 will we change the project name? 19:02:43 currently we have a very “imperative” name :-) 19:03:02 yapeng: that is one suggestion 19:03:21 so thats home work for everyone 19:03:21 i see. 19:03:31 alright, thanks all 19:03:34 #endmeeting