16:07:18 <hongbin> #startmeeting containers
16:07:19 <adrian_otto> thanks tmorin
16:07:19 <openstack> Meeting started Tue Jul  5 16:07:18 2016 UTC and is due to finish in 60 minutes.  The chair is hongbin. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:07:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:07:23 <openstack> The meeting name has been set to 'containers'
16:07:25 <hongbin> #link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2016-07-05_1600_UTC Today's agenda
16:07:30 <hongbin> #topic Roll Call
16:07:32 <Drago> o/
16:07:34 <muralia> murali allada
16:07:36 <tcammann> o/
16:07:37 <adrian_otto> Adrian Otto
16:07:39 <dane_leblanc> o/
16:07:42 <eghobo> o/
16:07:54 <rpothier> o/
16:07:54 <rochapor1o> Ricardo Rocha
16:08:02 <strigazi> Spyros Trigazis
16:08:05 <hongbin> Thanks for joining the meeting Drago muralia tcammann adrian_otto dane_leblanc eghobo rpothier rochapor1o strigazi
16:08:13 <hongbin> #topic Announcements
16:08:19 <hongbin> I will be on travel next week so unable to chair the next meeting. Looking for a temp chair.
16:08:36 <hongbin> Any volunteer?
16:08:46 <adrian_otto> o/
16:09:00 <hongbin> adrian_otto: you can chair the next meeting?
16:09:02 <adrian_otto> yes
16:09:07 <hongbin> adrian_otto: thanks
16:09:11 <adrian_otto> np.
16:09:15 <hongbin> #topic Review Action Items
16:09:22 <hongbin> 1. hongbin create a wiki session to report a list of Magnum users (DONE)
16:09:28 <hongbin> #link https://wiki.openstack.org/wiki/Magnum#Users
16:09:49 <hongbin> It looks CERN is the only user
16:10:21 <hongbin> For others, we would like to know if you are using Magnum
16:10:46 <hongbin> Just write your name and oragnazation there if you like.
16:10:53 <hongbin> #topic Essential Blueprints Review
16:11:00 <hongbin> 1. Support baremetal container clusters (strigazi)
16:11:06 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/magnum-baremetal-full-support
16:11:48 <strigazi> Not much since last week, we are still working on the gate tests.
16:11:48 <hongbin> strigazi: any update?
16:12:50 <strigazi> Only the patch for fixed networks was merged
16:12:54 <strigazi> that's it
16:13:03 <hongbin> strigazi: thanks
16:13:12 <hongbin> Any question for strigazi ?
16:13:48 <hongbin> 2. Magnum User Guide for Cloud Operator (tango)
16:13:54 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/user-guide
16:13:59 <hongbin> Ton is on vacation. I update you on behalf of him.
16:14:06 <hongbin> (Ton) The session on bay driver and baymodel were merged.
16:14:11 <hongbin> (Ton) The new section on bay is about 75% written
16:14:17 <hongbin> (Ton) I will finish after I return.
16:14:31 <hongbin> That is it from him
16:14:49 <hongbin> Question?
16:15:08 <hongbin> 3. COE Bay Drivers (jamie_h, muralia)
16:15:16 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/bay-drivers
16:15:31 <muralia> Thanks strigazi for updating the swarm driver patch while I was out yesterday.
16:15:47 <muralia> we seem to be really close to getting all the tests passing.
16:16:19 <muralia> there might be an issue with removing the hardcoded path to the swarm templates right now.
16:16:34 <muralia> looking into that. but over all, we are really close to getting it done.
16:16:57 <muralia> I'll switch focus to the kubneters drivers once everything looks fine with the swarm driver.
16:17:03 <muralia> thats all for me
16:17:18 <hongbin> muralia: Thanks for teh update
16:17:24 <strigazi> I have two patches as WIP on that bp, please ignore them.
16:17:40 <muralia> can you abandon them strigazi?
16:17:50 <muralia> the current patch seems to be the right way to go.
16:18:43 <strigazi> Yes, I leave them for a few days if I need to run something on the gate. They helped me a little
16:19:02 <muralia> sure
16:19:04 <mkrai> Hi everyone! I am sorry for being late
16:19:17 <hongbin> mkrai: np
16:19:38 <hongbin> Any comment for the bay driver BP?
16:20:03 <hongbin> 4. Create a magnum installation guide (strigazi)
16:20:09 <hongbin> #link https://blueprints.launchpad.net/magnum/+spec/magnum-installation-guide
16:20:18 <hongbin> strigazi: ^^
16:20:41 <strigazi> The guide for suse is merged, and I'm still trying to package debian
16:21:00 <strigazi> I'll also add a "launch an instance" section
16:21:21 <strigazi> that's all
16:21:36 <hongbin> What is "launch an instance" section for?
16:22:01 <strigazi> like so : http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-heat.html
16:22:39 <strigazi> It's part of the current install guide to actually test that a simple example work after deployment
16:22:42 <hongbin> OK. It looks that section is for launching a bay
16:22:50 <strigazi> yes
16:22:54 <hongbin> I see
16:23:15 <hongbin> Any other comment for the installation guide BP?
16:23:34 <strigazi> to clarify
16:23:47 <strigazi> debian packages also means ubuntu packages
16:23:56 <strigazi> they are the same for magnum
16:24:18 <hongbin> get that
16:24:34 <hongbin> Any problem for packaging the debian packages?
16:25:01 <strigazi> Many, but I'm getting closer :)
16:25:03 <hongbin> strigazi: It looks the debian part is particular challenging?
16:25:15 <hongbin> OK. Sounds good
16:25:43 <hongbin> #topic Magnum UI Subteam Update (bradjones)
16:25:49 <hongbin> bradjones: there?
16:26:11 * hongbin didn't receive any update from magnum-ui so far
16:26:54 <hongbin> It looks Brad is not there. Let's skip this session
16:27:03 <hongbin> #topic Kuryr Integration Update (tango)
16:27:08 <hongbin> (Ton) I did attend the Kuryr meeting on Monday.
16:27:14 <hongbin> (Ton) They have started the code refactoring into 3 repos: kuryr-lib, kuryr-libnetwork, kuryr-kubernetes.
16:27:20 <hongbin> (Ton) I will use the stable fork for our development until the new repos are stable.
16:27:25 <hongbin> That's it
16:27:30 <hongbin> Comment?
16:28:16 <hongbin> #topic Other blueprints/Bugs/Reviews/Ideas
16:28:22 <hongbin> 1. Create a Magnum team account in Docker Hub for hosting official images (strigazi)
16:28:44 <strigazi> There is one, but we don't know who owns it
16:28:45 <strigazi> https://hub.docker.com/r/openstackmagnum/
16:29:18 <hongbin> strigazi: maybe it help to describe the rational to create a magnum repo in Docker Hub?
16:29:44 <strigazi> I pushed a change for cinder swam integration with rexray deploying it
16:29:50 <strigazi> in a container
16:30:28 <strigazi> put we need a docker image for that. I thought that a good option is to have an official magnum repo for that
16:30:41 <strigazi> this is the change https://review.openstack.org/#/c/336594/
16:31:07 <strigazi> I don't see another option since we use atomic
16:31:25 <strigazi> we can't install anything on it
16:31:35 <hongbin> strigazi: How large is the image?
16:32:06 <strigazi> I think 200mb, but i'm not sure let me check
16:32:23 <hongbin> Looks quite large
16:32:42 <strigazi> 954
16:32:53 <strigazi> https://hub.docker.com/r/strigazi/docker-rexray/builds/bh2bmxvfvuqe2mzpdkrzuwf/
16:32:54 <hongbin> 954 mb ?!
16:33:41 <strigazi> I guess 164.6mb
16:33:51 <rochapor1o> it's layered on fedora:23, if we have a common base image (be it fedora:23 or not) the actual rexray part would be much smaller
16:33:52 <hongbin> ok
16:34:11 <muralia> https://hub.docker.com/r/strigazi/docker-rexray/tags/
16:34:14 <muralia> 216 mb
16:34:32 <hongbin> My worry is the gate won't have enough time to pull it down
16:34:52 <strigazi> this size is with fedora:23
16:34:53 <hongbin> Unless there is a way to build the image into the OS
16:35:11 <strigazi> to have it in the image?
16:35:19 <hongbin> maybe
16:35:34 <muralia> do we bake in any other image right now?
16:35:39 <muralia> or will this be the first?
16:35:40 <strigazi> if we do that we can add rexray directly
16:35:58 <adrian_otto> the openstack-infra team has expressed willingness to have a custom image for us
16:36:18 <strigazi> adrian_otto: a custom fedora-atomic?
16:36:24 <adrian_otto> because if they do that, we end up using less time for our gate tests, and that's good for the other projects.
16:36:37 <adrian_otto> strigazi: yes
16:36:45 <strigazi> ok
16:36:55 <rochapor1o> how will we manage updates? everything we put in the image itself will require a new image being pushed on every security update (vs a docker pull on the nodes)
16:37:07 <strigazi> that means we maintain the rexray package in a way
16:37:55 <muralia> rochaporlo: good point. lets try to reduce the size of the docker image and see if that works.
16:38:17 <rochapor1o> the alternative is a ostree rebase, but that requires a node reboot and it's complicated to manage
16:38:21 <strigazi> I'll try to modify the image
16:38:25 <hongbin> I guess it is very hard to reduce the size, unless we switch to fedora 23
16:38:32 <rochapor1o> alpine?
16:39:14 <strigazi> Even with the a smaller image. Where would that image live?
16:39:45 <muralia> we should send a ML email to find out who created the docker hub account
16:39:46 <hongbin> strigazi: Could we build the docker image in the post-devstack hook?
16:40:14 <strigazi> It will down load the fedora:23 image anyway
16:41:06 <hongbin> OK. Push the discussion in ML?
16:41:16 <adrian_otto> what if we had a local mirror (caching reverse proxy) of the docker hub in each of the clouds that openstack-infra exists, and enter host entries into the local /etc/hosts files to use that for the hub dns names
16:41:50 <adrian_otto> that would speed up the load of the dociker image considerably in the general case, and allow for them to be updated without our participation
16:43:13 <hongbin> If the infra team agree, this could be a solution
16:43:42 <strigazi> and in which account we'll host the image?
16:44:01 <adrian_otto> is there one the upstream owns?
16:44:09 <adrian_otto> or is this magnum specific?
16:44:25 <strigazi> magnum specific
16:44:37 <adrian_otto> then we can put a tarball of the image on tarballs.openstack.org
16:44:38 <strigazi> I asked about an official
16:44:46 <adrian_otto> and just load it from that
16:45:00 <adrian_otto> leverage the existing mirror infrastructure
16:45:22 <strigazi> put the docker image in a tarball?
16:45:26 <adrian_otto> yes
16:45:37 <adrian_otto> you can create one with docker export
16:45:48 <adrian_otto> and you re-create it with docker import
16:46:04 <hongbin> OK, then we can run docker build as part of the gate, then upload it to tarballs.openstack.org
16:46:10 <rochapor1o> would we use that for the installation on production sites?
16:46:10 <strigazi> ok, I'll check if I can upload it there
16:46:16 <adrian_otto> that should work
16:46:37 <adrian_otto> rochapor1o: we should have a variable for the source of this
16:46:52 <adrian_otto> that way each cloud operator can select the location that makes the most sense for them.
16:47:07 <rochapor1o> that sounds good
16:47:23 <hongbin> #topic Open Discussion
16:47:46 <strigazi> So we won't have a magnum account on docker hub
16:48:12 <adrian_otto> that's a future option
16:48:13 <hongbin> strigazi: I guess it is unnecessary, if we can run docker build instead
16:48:25 <strigazi> ok
16:48:39 <strigazi> bay drivers passed the gate
16:48:48 <adrian_otto> whoot
16:48:49 <muralia> yes!
16:49:01 <hongbin> awesome
16:49:21 <strigazi> it's only swarm but it's progress
16:50:35 <hongbin> Drago: I have a question for https://review.openstack.org/#/c/333383/9/magnum/templates/kubernetes/fragments/api_gateway_switcher_kubemaster.yaml
16:51:27 <hongbin> Drago: It looks we implemented a custom Heat resource for mixing the inputs to outputs
16:51:41 <hongbin> Drago: Would it possible to contribute this resource to Heat?
16:52:32 <hongbin> That is OS::HEAT::ApiGateWaySwitcher instead of Magnum::ApiGatewaySwitcher
16:53:21 <Drago> Hm, interesting idea
16:53:35 <Drago> I will have to discuss it on #heat
16:53:49 <hongbin> Drago: thx
16:54:50 <hongbin> Anything else to discuss?
16:55:26 <hongbin> If no, I will close the meeting a little earlier
16:56:13 <hongbin> All, thanks for joining the meeting. The next meeting will be chaired by adrian_otto at the same time next week
16:56:13 <adrian_otto> fine with me
16:56:19 <hongbin> #endmeeting