15:00:28 #startmeeting kuryr 15:00:29 Meeting started Mon Jan 4 15:00:28 2016 UTC and is due to finish in 60 minutes. The chair is gsagie. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:32 The meeting name has been set to 'kuryr' 15:00:53 #info irenab, vikasc, fawadkhaliq, banix, gsagie in meeting 15:01:06 #info apuimedo, tfukushima are on vacations 15:01:19 #topic kubernetes integration 15:01:36 #link https://etherpad.openstack.org/p/kuryr_k8s 15:01:41 irenab: want to update on this? 15:01:57 I will try to sum-up what we have 15:02:16 banix: i believe you have more experience on this issue as well, we should use your experience on this subject :) 15:02:22 hi devvesa! welcome 15:02:29 gsagie: o/ 15:02:31 #info devvesa in meeting as well :) 15:02:42 One of the missions for the Mitaka release is to provide kuryr - Kubernetes integration 15:03:17 We started to put ideas on the etherpad ^^ 15:04:06 We should decide on the approach to take here if its another disctinct integration via network plugin or CNI driver 15:04:08 #link https://etherpad.openstack.org/p/kuryr_k8s 15:04:14 One of the ideas irenab brought up and i wrote it there, is that we need to think about ways to expose the extra features Neutron provide to the users, so they could use for example Kubernetes anootation to configure security groups and so on.. 15:04:45 gsagie: I think before extra features, we need to define the integration model 15:05:28 Looks like libnetwork reuse is not applicable at this phase 15:05:34 irenab: agreed, i believe the only option right now is Kubernetes network plugin 15:05:55 irenab: yes, until Kubernetes will support it 15:06:07 banix: any ideas on this subject? 15:06:16 or anyone else of course :) 15:06:18 there is a network plugin that is actually CNI Driver that invokes CNI plugins, I am in favor to explore this option 15:06:32 sorry was away 15:06:36 np 15:07:03 yes have been following up our options with k8s 15:07:29 it seems they have a different network model in mind that may want to build on 15:07:49 I will know more by next week and can report back with a better understanding 15:07:57 So we need 1. Integration approach. 2. Data Model mapping from k8s to neutron 3. Extra features (mainly security) 15:08:34 banix: can you please elaborate? 15:08:52 on they have different approach in mind 15:09:11 yes, the integration through a plugin is the available option right now 15:09:39 there are discussions about how to map/integrate CNI and CNM 15:09:51 former from k8 and later from libnetwork 15:10:08 i haven’t followed the latest discussions in the last two weeks 15:10:38 banix:discussions on kubernetes-sig-network ? 15:10:56 yes 15:11:06 irenab, banix: any chance we can put this task on any of you two to write a short spec for this? or is taku also working on that? 15:11:22 gsagie: I will start this asap 15:11:34 gsagie: yes sure; will talk to irenab 15:11:55 #action irenab, banix start writing a spec for kubernetes integration in terms of 1. Integration approach. 2. Data Model mapping from k8s to neutron 3. Extra features (mainly security) 15:11:57 banix: great! Will be happy to collaborate on this 15:12:02 irenab, banix: thanks! 15:12:18 we all should read more and be ready to discuss more concrete details next week 15:12:29 +1 gsagie 15:12:45 i would like us to also try to talk with deployers and understand missing use cases for networking features when deploying with Kubernetes 15:12:54 i have some team i can check internally 15:13:09 gsagie: I beleive it both deployers and cluster admins 15:13:29 #action gsagie understand use cases for deploying Kubernetes and update the etherpad 15:13:33 irenab: yep 15:13:35 if you can collect data from both, will be great 15:13:58 irenab: yeah i have some people that i can talk with, but would appreciate any more feedback 15:14:12 I can provide useful link of use cases shared in the kubernetes-sig-networking team 15:14:28 irenab: that would be great! 15:14:40 #action irenab provide useful link of use cases shared in the kubernetes-sig-networking team 15:14:40 https://docs.google.com/document/d/1ZCz_MZILzKCbFwF9gjU1YNA1YbNaw0NDsESh1P6Vcnc/edit 15:14:47 #link https://docs.google.com/document/d/1ZCz_MZILzKCbFwF9gjU1YNA1YbNaw0NDsESh1P6Vcnc/edit 15:15:20 so anything else for Kubernetes ? i think Taku will also join you and banix as he also investigated these areas 15:15:27 and we should be smarter next meeting hopefully 15:15:43 sounds good 15:15:53 gsagie: banix : I think we should have initial spec up to next meeting 15:16:19 #topic vif binding 15:16:29 banix, i see you have an action item for linux bridge binding 15:17:02 gsagie: I will get to it. Have been off the grid for last two weeks 15:17:03 i dont think its any urgent task, but was wondering if you have any update 15:17:13 banix: np, understandable :) 15:17:24 one thing that worries me is the cost in terms of latency 15:17:46 what do you mean cost? 15:17:58 using an executable; I think eventually, sooner rather than later we need to load modules for drivers, etc 15:18:27 gsagie: i mean specially for ovs with sec groups, there are many commands to be executed 15:18:42 banix: i agree, executable doesnt scale and there are already examples for that with security groups iptables CLI ;) 15:18:45 with sudo, etc 15:18:51 heh yeah 15:19:07 so i have that in my list of todos 15:19:47 #action banix to investigate linux bridge binding and alternatives to using an executable scripts for binding 15:19:51 banix: ok sounds good 15:20:22 banix: the OVS unbind part was merged while in holiday, seems ok to me but i would verify when you have time that everything works for you too 15:20:37 yes noticed that. will do. 15:20:45 ok, thanks 15:20:55 #topic IPAM 15:21:01 vikasc: any update for this? 15:21:01 https://review.openstack.org/#/c/256211/ 15:21:14 i addressed banix comments on this patch 15:21:16 #link https://review.openstack.org/#/c/256211/ 15:21:40 okie, will review it probably tommorow 15:22:09 vikasc: there is also updating the devref with the implementation details 15:22:15 thanks.. i am spending time understanding kubernetes networking model 15:22:19 yes 15:22:30 last week i was on vacation 15:22:31 just to document things better, i will add fullstack tests for it, unless you want to do it as well 15:22:36 np 15:22:52 was quite 2 weeks with out all of you here :) 15:23:05 #action vikasc update devref for IPAM 15:23:12 #action gsagie add fullstack tests for IPAM 15:23:19 sounds good 15:23:23 #topic packaging 15:23:40 devvesa: any update on that? 15:24:02 No. I didn't get any feedback 15:24:21 I'll try to push this week 15:24:25 devvesa: is there anything i can help with? 15:24:25 and test it better 15:24:56 okie, sounds good 15:24:58 Not now. If I have any question about the service/configuration for packaging, I'll ask in the mailing list or IRC 15:25:00 :) 15:25:08 okie great 15:25:31 ihar from neutron might be able to help with that 15:25:52 #action devvesa continue with packaging task and testing 15:26:02 #topic capabilities 15:26:17 Toni is not here, so i guess no update on that, 15:26:30 #action gsagie check capabilities progress with apuimedo 15:26:50 #topic docker swarm 15:27:19 banix: i see from 2 meetings ago that you conducted a demo with Kuryr and Docker Swarm anything available? 15:27:28 will be cool to post it to the mailing list 15:28:03 gsagie: will do; don’t have a recorded demo but will do it 15:28:41 gsagie: to be more accurate i have recorded a simple demo but will try to make a cleaner and better one in a day or two and post 15:28:42 cool, that will be awesome, let me know when you do 15:29:00 we should link to it for people to see :) 15:29:12 yes will do 15:29:21 #action banix publish a recorded demo of docker swarm with Kuryr 15:29:26 thanks! 15:29:30 np 15:29:35 #topic testing 15:30:14 ok, so regarding testing i would like to ask your premission to merge https://review.openstack.org/#/c/259744/ , apuimedo has -1 on it but he is on long time off 15:30:21 and already approved to merge it in temporary 15:30:29 its blocking the fullstack tests progress 15:30:51 I already have a bug assigned to solve this issue and an idea how to do it but want it to happen in parallel 15:31:02 gsagie: go for it 15:31:15 banix: great 15:31:50 #action gsagie continue on fullstack tests and solve the neutron credential problem in the gate 15:32:17 banix: Baohua is from your team? 15:32:33 gsagie: yes 15:32:36 i guess he was on vacation as well since i havent seen him and i think you said he wants to join the testing efforts 15:32:47 last meeting i directed him to my patches 15:33:13 i will try to sync with him tommorow 15:33:23 gsagie: yes, i will follow up with him too 15:33:27 #action gsagie sync with Baohua regarding testing 15:33:36 #action gsagie add Rally docker plugin 15:34:04 Another thing i wanted to ask you guys, i want to start adding Docker plugin for Rally, do we want to do this as part of Kuryr, or add this directly to Rally? 15:34:09 and only use it from Kuryr 15:34:46 gsagie: adding in Kuryr should be okay and can be managed well. 15:34:48 wanted to ask everyone before sending the question to the list, the rally team said we can go either way where they prefer to have it in the rally repository 15:35:27 fawadkhaliq: yeah i agree 15:35:46 don’t know I am afraid 15:35:47 i think i will also email to the list, so we do this process in the open and get more opinions 15:36:00 unless there is an added benefit of keeping in the Rally repo, which I can't think of right now. 15:36:08 cool. makes sense 15:36:21 fawadkhaliq: the only benefit is that we will have the rally team review it more closely 15:36:38 atleast thats what i can think of 15:36:56 reviews are significant :-) 15:37:01 we can consider it. 15:37:04 okie, will send to the list and we take it from there :) 15:37:19 sounds great! 15:37:28 i still havent got to the magnum integration for nested containers 15:37:39 #action gsaguie magnum integration and nested containers design 15:37:49 #action gsagie magnum integration and nested containers design 15:37:54 on nested containers 15:38:21 Toni gave me an action item 2 weeks ago and we were heading into the holidays 15:38:39 I will take a stab at writing a spec and we can iterate over it. 15:38:44 which one? 15:38:54 okie great! thanks for that 15:39:10 #action fawadkhaliq propose a spec for magnum integration and nested containers 15:39:39 I will reach out for discussions :-) 15:39:54 fawadkhaliq: important to think how we expose all the possible models to the user , for example OVS in the VM, IPVLAN usage with eBPF like you guys did and so on 15:40:09 absolutely 15:40:22 and another point that came up, is how to model the Kuryr service and where, there were questions about how it can reach Neutron API from inside the VM 15:40:37 and points like these.. just bringing them up :) 15:41:07 ok, feel free to discuss about that if you have any questions 15:41:24 yup, thanks! will cater for them and definitely, will discuss over #kuryr 15:41:32 okie 15:41:36 #topic open discussion 15:41:49 Thanks everyone for joining the first meeting of the new year :) 15:42:09 and welcome back everyone that had a good vacation, hope you had fun and managed to get some rest :) 15:42:15 and good to see you all again! 15:42:21 thank you! 15:42:30 thanks and likewise! 15:43:09 okie, good day everyone! bye 15:43:12 #endmeeting