16:00:34 #startmeeting containers 16:00:35 Meeting started Tue Nov 14 16:00:34 2017 UTC and is due to finish in 60 minutes. The chair is strigazi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:38 #topic Roll Call 16:00:39 The meeting name has been set to 'containers' 16:00:53 Spyros Trigazis 16:00:58 Sayali Lunkad 16:01:19 Mark Goddard 16:01:48 Costin GamenČ› 16:01:55 Daniel Abad 16:02:28 Thanks for joining the meeting slunkad mgoddard KwozyMan vabada 16:02:46 Today's agenda: 16:02:46 #link https://wiki.openstack.org/wiki/Meetings/Containers#Agenda_for_2017-11-14_1600_UTC 16:02:52 #topic Announcements 16:03:17 Magnum meeting calendar: You can import this ical file: 16:03:23 #link https://calendar.google.com/calendar/ical/dl8ufmpm2ahi084d038o7rgoek%40group.calendar.google.com/public/basic.ics 16:03:37 #topic Review Action Items 16:03:41 None 16:04:01 #topic Review Blueprints/Bugs/Ideas 16:04:12 Add support of k8s cluster over opensuse distro https://blueprints.launchpad.net/magnum/+spec/k8s-opensuse-support 16:04:45 slunkad: Do you have anything to discuss, can we start testing? 16:04:57 strigazi: sorry there hasn't been much work on it for some weeks because i had taken some time off 16:05:12 strigazi: I am working on the unit tests right now 16:06:04 slunkad: do you have functional tests too? These are equally important 16:06:16 might have to wait a little more for testing as I need to work on providing the image too 16:06:42 strigazi: https://review.openstack.org/#/c/507522/8/magnum/tests/functional/k8s_opensuse/test_k8s_python_client.py 16:07:17 if you have an image I can put it in https://fedorapeople.org/groups/magnum/ temporarily 16:07:48 strigazi: alright I will ping you soon with the image 16:07:54 slunkad: thanks 16:08:19 Next is: Use the heat agent and Software Deployments in heat templates 16:08:32 https://review.openstack.org/#/c/468816/ 16:09:07 I'm investigating how smooth is to use ansible from the container to the host or ssh directly 16:09:36 There is one important operation that can't be executed from the container to the host 16:10:14 Creating a system container on the host requires to create a hardlink per container 16:10:40 and that is not possible since each container has each own namespace 16:11:14 That's it, otherwise the patch is ready, so please test it. 16:11:30 I'm trying to test in our production infra too 16:11:54 "it works on devstack" is not enough xD 16:12:13 And I have one more: Cluster upgrades 16:12:18 WIP: https://review.openstack.org/#/q/status:open+project:openstack/magnum+branch:master+topic:bp/cluster-upgrades 16:12:45 I'll udpate the spec with API examples https://review.openstack.org/#/c/433728/ 16:13:14 Have a look if you haven't already 16:13:55 Oh, one last item that I need some input from mgoddard and slunkad 16:14:21 sure 16:14:41 There is this bug regading the update operation that I mentioned before 16:14:45 #link https://bugs.launchpad.net/magnum/+bug/1722573 16:14:45 Launchpad bug 1722573 in Magnum "Limit the scope of cluster-update for heat drivers" [Undecided,New] 16:15:12 vabada from our team will work on it 16:15:18 +1 16:15:49 and we are thinking if it is better to just change the existing update command or 16:16:21 fix the existing command, deprecate it and add a new scale command too 16:16:30 The reasoning behind it is 16:17:09 That the update commands tries to apply a patch to the cluster object which is just too generic 16:17:40 and at the same time we limit the command explicitly to do scale up/down the cluster 16:17:52 mgoddard: slunkad thoughts? 16:18:26 strigazi: what all is the new command expected to do? 16:18:51 Change the size of the worker nodes resource group 16:19:38 I definitely agree that the current way will not take us far especially because it limits the scope 16:20:10 I would be in favor of adding a new command with more scope 16:21:55 The existing command can work, but if we try to add more functionality to the update command we will start to have redirections for each operation. 16:22:23 ok then we will try some prototype implementation 16:22:56 right, it seems like a one time effort to have a smart method to do that 16:23:43 cool 16:23:53 let's move to open discussion 16:23:58 #topic Open Discussion 16:24:24 any other business? 16:25:27 said once 16:25:40 said twice 16:25:52 let's wrap it up then 16:26:01 bye! 16:26:09 Thanks for joining, see you next week :) 16:26:14 #endmeeting