21:00:32 <strigazi> #startmeeting containers
21:00:33 <openstack> Meeting started Tue Mar 26 21:00:32 2019 UTC and is due to finish in 60 minutes.  The chair is strigazi. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:36 <openstack> The meeting name has been set to 'containers'
21:00:40 <strigazi> #topic Roll Call
21:00:45 <strigazi> o/
21:00:48 <ttsiouts> o/
21:00:50 <jakeyip> o/
21:00:57 <flwang> hi jakeyip
21:00:57 <brtknr> Isn't this channel busy today!? o/
21:01:13 <goldyfruit> I'll shut :D
21:01:16 <flwang> brtknr: it is, probably because v1.14 is out :D
21:01:31 <brtknr> flwang: :D
21:02:18 <strigazi> eandersson: ping
21:03:10 <strigazi> #topic Announcements
21:03:28 <strigazi> magnum stein rc1 is out
21:03:53 <flwang> yeah!
21:03:55 <strigazi> https://github.com/openstack/releases/blob/master/deliverables/stein/magnum.yaml#L12
21:04:33 <strigazi> We should add some highlights this weeks in the releases page
21:05:25 <strigazi> As flwang pointed out, k8s 1.14.0 is out, we can make this default in stein
21:05:25 <jakeyip> hi flwang strigazi :)
21:05:38 <strigazi> flwang: thougths?
21:06:00 <strigazi> jakeyip: hey
21:06:02 <flwang> strigazi: if sonobuoy can pass on v1.14, then we can
21:06:11 <strigazi> is it out?
21:06:43 <strigazi> I don't see it
21:06:57 <flwang> you mean sonobuoy or k8s v1.14?
21:07:00 <strigazi> yes
21:07:09 <strigazi> We can run the tests without it
21:07:39 <flwang> i mean we need to make sure sonobuoy (latest version )can pass on k8s v1.14 cluster
21:07:54 <strigazi> ok
21:07:56 <flwang> then i'm ok to use v1.14 as default version in stein
21:08:12 <strigazi> #topic Stories/Tasks
21:09:09 <eandersson> o/
21:09:35 <strigazi> Cluster upgrades, I have updeted the patch for minion upgrade, I miss smth to make it work with the API https://review.openstack.org/#/c/514960/
21:10:21 <flwang> strigazi: can current patch cover the base OS image upgrade?
21:10:24 <strigazi> The important part is that the agent is doing all the config. Only two scripts are user_data
21:10:27 <flwang> or just cover the k8s version upgrade?
21:11:04 <strigazi> can do OS too
21:11:24 <flwang> and can you briefly explain what's the problem you have now? and anything we can help
21:12:45 <strigazi> the docker_storage_setup doesn't work. it uses the default storage congig which is overlay2
21:13:53 <flwang> strigazi: does that mean if the docker_volume_driver is overlay2, all the other parts work well, is it?
21:14:03 <strigazi> yes
21:14:10 <flwang> cool
21:14:34 <flwang> that's a biiiiiiiiiiiiiiiiiiig milestone, so can i say it's ready for review and testing?
21:15:09 <strigazi> For the minions, should be in a good state
21:15:27 <flwang> master doesn't work at this moment?
21:16:13 <strigazi> master no, It needs some code in the driver part
21:16:32 <strigazi> to select the masters
21:16:56 <flwang> driver part means?
21:16:57 <strigazi> and the batch size is default to 1
21:17:15 <strigazi> magnum/drivers/heat/driver.py
21:17:16 <flwang> i think we should be able to pass in the batch size
21:17:24 <flwang> since it's covered in the api
21:17:41 <strigazi> yes
21:19:00 <flwang> i will think about the master part, we can discuss that part later
21:19:26 <strigazi> thanks
21:19:28 <flwang> based on current status, do you think the master upgrade will be a big task?
21:20:03 <strigazi> not bigger than this one
21:20:20 <flwang> strigazi: i see.
21:20:24 <strigazi> at least to upgrade k8s and OS
21:21:12 <flwang> again, i'd like to take opportunity to say THANK YOU for your big effort on this hardest job, and sorry for all my push
21:21:37 <strigazi> addons, need some effort. Also big jumps in versions of addons, I'm not sure if it is doable to support them
21:22:01 <flwang> i would put addons into a separate patch
21:22:13 <flwang> do you think they have hard dependency
21:22:29 <strigazi> when vX.Y.Z to cX+1.0.0
21:22:41 <strigazi> when vX.Y.Z to vX+1.0.0
21:22:44 <flwang> i mean will the addon upgrade cause big refactor of current k8s upgrade work
21:22:49 <flwang> you mean addon?
21:22:52 <strigazi> yes
21:23:19 <flwang> for that case, i'm pretty sure, the cloud provider must do the entirely testing before release the new template
21:23:28 <strigazi> we can do this after
21:23:35 <flwang> yep
21:23:36 <strigazi> yes, that is the idea
21:24:01 <flwang> and we can learn from current os upgrade and k8s upgrade work
21:24:11 <flwang> which will help us design the addon upgrade
21:24:33 <flwang> we don't have to mix them since they're definitely on different levels
21:24:40 <flwang> at least at this moment
21:24:41 <strigazi> sure
21:25:37 <strigazi> shall we move on?
21:25:39 <flwang> i will heavily test/review it since today
21:25:47 <flwang> yep, i'm good, thank you so much
21:25:52 <strigazi> cheers
21:26:28 <strigazi> nodegroups, I'm good with the current state for the DB and API so far
21:27:00 <flwang> strigazi: i don't worry about the db and conductor api part
21:27:02 <strigazi> ttsiouts did a pretty good job
21:27:23 <strigazi> shall we take it?
21:27:27 <flwang> i'd like to understand if the other parts can be ready in time so that we can get them in Stein if we want
21:28:09 <flwang> so let's double check this, if we want to get NG in stable/stein
21:28:17 <flwang> personally, I'm OK with this
21:28:59 <ttsiouts> flwang: you mean the driver parts?
21:29:01 <strigazi> If we take db/api/conductor, it is easier to iterate after
21:29:24 <flwang> i need a 'promise' :) from ttsiouts to promise he has enough time to get the other patches of NG complete in time
21:29:32 <flwang> strigazi: true, i get that
21:30:03 <ttsiouts> flwang: I'm on it
21:30:06 <ttsiouts> :D
21:30:06 <strigazi> until when?
21:30:40 <flwang> strigazi: https://releases.openstack.org/stein/schedule.html
21:30:53 <flwang> 12 April
21:31:08 <flwang> i'm not sure if we have more time after 12th
21:33:25 <ttsiouts> flwang: I can do it
21:33:41 <flwang> but IIRC, we can still cherrypick patch into stable branch after released
21:33:54 <flwang> though it's not a best practice for new feature
21:34:06 <flwang> but it still doable
21:34:53 <strigazi> we can do it. I don't see openstack as one piece of software since a long time :)
21:34:53 <flwang> ttsiouts: i will do more reviews for NG patches
21:35:01 <ttsiouts> flwang: thanks!
21:35:32 <flwang> strigazi: i understand, so let's try to meet it
21:35:58 <flwang> if we finally missed it for 1 or 2 patches, we can handle it
21:36:06 <flwang> strigazi: are you OK with that?
21:36:24 <strigazi> +1
21:36:31 <brtknr> ttsiouts: sorry, I wasnt able to do any more tests on your patches, my dev server is down :(
21:36:55 <ttsiouts> brtknr: thanks for all your effort!
21:37:53 <strigazi> eandersson: any more input for NGs?
21:37:56 <brtknr> ttsiouts: i havent done anything yet :P
21:38:00 <eandersson> I still need to test it out a bit more
21:38:10 <eandersson> Been a busy couple of weeks for us
21:39:20 <strigazi> ok
21:40:17 <strigazi> Does anyone want to bring something else up?
21:40:26 <flwang> strigazi: autoscaling/autohealing
21:41:06 <eandersson> Who is going to Denver?
21:41:11 <flwang> https://review.openstack.org/#/c/631378/ i break the unit test because of my last patchset, but it's in good shape for review and testing
21:41:40 <flwang> autoscaling/autohealing is also a very important feature we'd like to get it in Stein
21:42:01 <strigazi> could we have two labels?
21:42:09 <flwang> we will have two labels
21:42:27 <flwang> auto_scaling_enabled and auto_healing_enabled
21:42:53 <flwang> the magnum driver will be included in CA v1.14.1
21:42:59 <strigazi> auto_healing_enabled will control only draino?
21:43:15 <flwang> strigazi: and CA
21:43:42 <strigazi> if auto_healing_enabled=false -> no autoscaling?
21:43:43 <flwang> auto_healing_enabled will also deploy CA
21:44:16 <flwang> if auto_healing_enabled = False, but auto_scaling_enabled = True,  autoscaling is still working
21:44:35 <strigazi> sounds good
21:44:44 <flwang> Either auto scaling or auto healing we need CA to be deployed
21:44:45 <flwang> if [ "$(echo $AUTO_HEALING_ENABLED | tr '[:upper:]' '[:lower:]')" = "true" || "$(echo $AUTO_SCALING_ENABLED | tr '[:upper:]' '[:lower:]')" = "true"]; then
21:46:04 <strigazi> ok
21:46:12 <strigazi> sounds good
21:46:29 <strigazi> eandersson: i'm going to denver
21:46:46 <eandersson> Awesome
21:47:13 <eandersson> We will have 5 individuals from Blizzard attending.
21:47:45 <strigazi> cool
21:48:04 <jakeyip> (2 from Nectar but I won't be there :( )
21:48:45 <strigazi> flwang: anything else you want to discuss?
21:48:58 <eandersson> Do we have any particular topics to discuss at Denver, or maybe an ether pad set up?
21:49:21 <flwang> no, im ok
21:49:42 <strigazi> eandersson: flwang let's try to cook something for next week's meeting
21:49:49 <eandersson> Sounds good
21:50:12 <eandersson> Would be nice to have some topics lined up ahead of the event
21:50:34 <flwang> strigazi: again, thank you my friend
21:50:50 <strigazi> flwang: eandersson we will have a room for one day
21:51:10 <flwang> strigazi: it would be nice if you can review this https://review.openstack.org/647618
21:51:20 <strigazi> flwang: for  the afternoon I  guess you can join online
21:51:31 <flwang> yep
21:51:43 <flwang> if time is ok, i can join
21:51:50 <eandersson> https://etherpad.openstack.org/p/magnum-train-ptg <- something like this maybe
21:52:02 <strigazi> eandersson: =1
21:52:04 <strigazi> eandersson: +1
21:53:03 <strigazi> let's add it here https://wiki.openstack.org/wiki/PTG/Train/Etherpads
21:54:56 <strigazi> Let' send the meeting? anything else?
21:55:07 <eandersson> Nope - all good
21:55:27 <eandersson> As always feel free to hit me up with reviewes etc
21:55:52 <flwang> strigazi: thank you
21:56:22 <strigazi> flwang: cheers, eandersson thanks
21:56:28 <strigazi> #endmeeting