13:01:54 #startmeeting openstack-salt 13:01:55 Meeting started Tue Aug 2 13:01:54 2016 UTC and is due to finish in 60 minutes. The chair is newt_. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:59 The meeting name has been set to 'openstack_salt' 13:01:59 hello 13:02:07 #topic roll call 13:02:15 o/ 13:03:13 o/ 13:03:44 anyone else 'round? :) 13:03:52 ok moving on 13:03:59 #topic Introduction 13:04:04 This meeting for the openstack-salt team 13:04:12 This meeting for the openstack-salt team 13:04:21 if you're interested in contributing to the discussion, please join #openstack-salt 13:04:26 #link http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting 13:04:34 #link https://wiki.openstack.org/wiki/Meetings/openstack-salt 13:04:40 #topic Review past action items 13:05:14 * newt_ newt to add the salt-formula-kubernetes 13:05:35 this one is being processed by openstack governance team 13:06:00 and is being accepted so far, I think it will be integrated within a week 13:06:18 * newt_ tux to update the documentation on bootstrap for vagrant and docker 13:06:25 is Tux around? 13:07:21 * newt_ apuimedo to contact jpavlik about the kuryr integration 13:07:30 is apuimedo around? :o 13:08:37 I dont think jakob got any message, but i'll have to ask him 13:09:01 and the last item from past issues is ACTION: create deployments for docker and kubernetes and synchronise with Tux on docs 13:09:44 This one has not moved forward much 13:10:07 we have added the metadata for the deployment but it is not tested yet 13:12:04 #topic Today's Agenda 13:13:02 well today's issues are follow on past weeks issues, get the kubebased/docker deployments up-2-day on doc and deployment level 13:13:13 newt_: I am around 13:13:17 I wrote to him on IRC but I don't think he saw it 13:14:12 apuimedo: hello, can you write him an email? jakub.pavlik@tcpcloud.eu 13:14:47 sur 13:14:49 *sure 13:14:50 as there's not much folk around we can start discussion now 13:14:57 about the kuryr needs 13:15:32 to setup the formula basis, get to know the architecture and services/roles 13:16:01 well, the libnetwork integration already has a container 13:16:21 we are now finalizing support for keystone v3 13:16:27 since kolla requires it 13:16:42 then it needs to know where Neutron is 13:16:48 and have admin role credentials 13:16:53 (the info is passed as env vars 13:17:32 https://hub.docker.com/r/kuryr/libnetwork/ 13:17:45 do you have some architecture pic 13:17:46 ? 13:18:04 I do 13:18:19 can you please share? 13:18:45 http://paste.openstack.org/show/545625/ 13:18:52 this is the parameters the container takes 13:18:58 and now I'll pass the diagram 13:19:02 and the formula think - we use it to cover both container and vm deployments and to define the metadata and tests 13:20:01 https://gitlab.com/celebdor/design/blob/master/diagrams/fosdem/libnetwork_diagram.svg 13:20:13 https://gitlab.com/celebdor/design/blob/master/diagrams/fosdem/libnetwork_rd_diagram.svg 13:20:28 but it can be run just as container from source - where the metadata layer is thinner 13:21:02 newt_: what do you mean as running a container from source? 13:21:12 Do you mean from a container registry? 13:23:03 if the formula is defined - it serves as deploy script both for container and vm service 13:23:23 and has metadata definition - to which endpoints it connects 13:24:02 ah, cool 13:24:28 and there is a validation layer for it as welll 13:24:43 and you can make definitions for varius backends you have 13:24:44 newt_:so it would be creating an openstack/salt-formula-kuryr 13:24:52 yes 13:24:55 ok 13:25:08 how long does it typically take to do that? 13:25:35 where is your dockerfile? :) 13:26:09 https://github.com/openstack/kuryr-libnetwork/tree/master/contrib/docker/libnetwork 13:26:10 usually not long [hours] 13:26:15 but I need to update it 13:26:22 we were splitting the repository 13:26:41 openstack/kuryr got split into openstack/kuryr and openstack/kuryr-libnetwork 13:26:43 yes this looks pretty straightforward 13:27:00 is it just 1 service if I read the architecture right? 13:27:29 yes 13:27:36 brb 13:27:37 it's a single service with different endpoints 13:27:48 it answers both ipam and remote driver endpoints 13:27:58 the kubernetes integration is a bit more involved 13:28:32 but we're still polishing the prototype to put it in openstack/kuryr-kubernetes 13:32:15 yes, the formula should be easy to implement as seen in dockerfile, then we can proceed the setup deployemnt params in new stacks that will represent the various deployment screnarios, starting with the current one 13:32:39 you can create the formula repo in your namespace on github and give me access 13:33:12 newt_: alright 13:33:20 I can setup the skeleton and get the basic services up and running 13:33:41 I am flying to Prague on Thursday, so I think probably I'll have time next Monday-Tuesday night 13:34:03 #action apuimedo create the kuryr formula repo 13:34:10 +1 13:34:12 :-) 13:34:58 what are the other requirements on openstack side? 13:35:33 I'd sum it up in a blueprint which we can tune 13:35:36 none 13:35:46 just the neutron backend 13:35:47 kuryr-kubernetes will need lbaas 13:36:03 it supports midonet now, do i remember right? 13:36:05 but kuryr-libnetwork has enough with just plain Neutron 13:36:24 it supports Midonet, ovs, plumgrid, ovn and dragonflow 13:36:33 kuryr-kubernetes only midonet for now 13:37:46 kuryr-kub brindges kube and os deployments, right? 13:38:02 and kuryr-libn does what? 13:38:13 sorry for the ignorance :) 13:38:48 right 13:38:57 kuryr-libnetwork is useful for swarm deployments 13:39:05 it gets them neutron networking 13:39:25 (even without swarm, single docker engine setups also get neutron networking) 13:41:04 yes, I understand better now :) 13:41:18 ;-) 13:43:23 and the kur-libn and kur-kube are 2 different containers now, or one with different parametrisation 13:44:56 they will always be different containers 13:45:16 and together or either or 13:45:18 kuryr-kube is currently as a midonet proto at midonet/raven 13:46:44 a#link https://blueprints.launchpad.net/openstack-salt/+spec/salt-formula-kuryr 13:47:05 here I'd outline the params and the setup needed for testing 13:47:34 params = complete metadata - the identity, network endpoints for libnet 13:47:44 good 13:47:53 and if the service has any internal params that are worth tuning 13:49:09 there's some configuration options like the scope of the networks 13:49:19 I'll add it to the blueprint 13:49:58 yes, let me know when the repo is ready and I will fill it up with base formula 13:52:55 the kuryr is accepted, does anyone have any other issue? 13:53:19 thanks newt_ 13:58:11 #topic Open Discussion, Bug and Review triage (submit modules to triage here) 13:58:35 well anything else from anyone :) 13:59:13 If not, thank you apuimedo, and well see each other over kuryr :) 13:59:21 very well 13:59:23 thanks 13:59:40 #endmeeting