09:01:26 <flwang1> #startmeeting magnum
09:01:27 <openstack> Meeting started Wed Dec 18 09:01:26 2019 UTC and is due to finish in 60 minutes.  The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:01:29 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:01:31 <openstack> The meeting name has been set to 'magnum'
09:01:36 <strigazi> flwang1: we have implemented 12 months ago.......
09:01:36 <flwang1> #topic roll call
09:01:39 <strigazi> or more
09:01:41 <strigazi> o/
09:02:00 <flwang1> o/
09:02:22 <brtknr> o/
09:02:40 <brtknr> dtomasgu:
09:02:49 <flwang1> #topic multi az support
09:02:58 <flwang1> let's continue the az topic ten
09:03:00 <flwang1> then
09:03:20 <flwang1> strigazi: could you please introduce your work? is it upstreamable?
09:03:46 <strigazi> I'm sorry, we did it upstream two years ago https://review.opendev.org/#/c/527663/
09:04:14 <strigazi> we did nodegroups for having an easy way to use this labels.
09:04:15 <strigazi> we did nodegroups for having an easy way to use this label.
09:05:08 <flwang1> i think we are talking different multi az features
09:05:33 <strigazi> in nova there is onlt --availability-zone
09:05:38 <flwang1> strigazi: do you mean we can deploy different node to different AZ for one cluster?
09:05:55 <strigazi> yes.
09:06:02 <flwang1> how?
09:06:11 <strigazi> this was the main reason we implemneted nodegroups
09:07:06 <strigazi> openstack coe nodegroup create --labels availability_zone=the-other-az
09:07:35 <flwang1> you mean when create new NG, user need to specify the AZ so as to create the NEW ng to a different AZ?
09:07:42 <strigazi> yes
09:09:08 <flwang1> it makes me confused, since i don't remember we have a label named availability_zone
09:09:38 <strigazi> https://docs.openstack.org/magnum/latest/user/#availability-zone
09:10:00 <brtknr> :D magnum labels is a box full of hidden treasures
09:10:01 <strigazi> the docs are not up to date.
09:10:25 <strigazi> why did you think we implemneted NGs?
09:10:45 <brtknr> strigazi: GPU flavor nodes? :P
09:10:58 <strigazi> I think we discussed in the channel moving that labels as a field.
09:11:27 <flwang1> ok, that's cool
09:11:32 <strigazi> brtknr: this is the 3% of the use case
09:11:35 <flwang1> i will test this later
09:11:40 <strigazi> 97% is AZ
09:11:41 <flwang1> strigazi: did you try this one?
09:11:56 <strigazi> we are not in train yet
09:12:14 <flwang1> so you can't test it atm?
09:12:44 <brtknr> how do you simulate multiple AZ on devstack?
09:12:55 <flwang1> catalyst cloud are not using multi az but some of our private cloud customers are using multi az
09:13:12 <flwang1> brtknr: i think you have to have at least two 2 nodes
09:13:24 <flwang1> then create 2 host aggr
09:13:29 <flwang1> and then 2 az
09:13:36 <flwang1> i haven't tested it before with devstack
09:14:12 <flwang1> strigazi: this is a fantastic one, i'm very happy to see it's cover by NG
09:14:25 <flwang1> you saved my time :)
09:14:27 <brtknr> hmm okay, i think this one is resolved for now :) lets move to another topic, we have 45 mins left
09:14:49 <flwang1> #topic fc driver on master
09:15:02 <flwang1> based on my testing, i think the current fcos driver is broken
09:15:18 <brtknr> flwang1: is it working for you on 9.1.0?
09:15:39 <flwang1> i don't have time to try, i had 5 meetings today :(
09:15:48 <brtknr> flwang1: also its broken for a  different reason on fcos 31
09:15:51 <flwang1> 6, includes this one
09:16:04 <flwang1> fcos 31 is a broken image, don't try it
09:16:17 <brtknr> oh! how do you mean?
09:16:24 <brtknr> its been released as "stable"
09:16:44 <flwang1> https://github.com/coreos/fedora-coreos-tracker/issues/327
09:16:57 <flwang1> ?
09:17:01 <flwang1> are we talking the same one?
09:17:28 <brtknr> no that is the development image
09:17:41 <flwang1> brtknr: where did you get the stable one?
09:17:55 <brtknr> https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/31.20191210.3.0/x86_64/fedora-coreos-31.20191210.3.0-ostree.x86_64.tar
09:18:14 <brtknr> this is the one they say is stable: https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/31.20191210.3.0/x86_64/fedora-coreos-31.20191210.3.0-openstack.x86_64.qcow2.xz
09:18:32 <brtknr> the second one, not the first
09:18:48 <flwang1> but from the issue above, i won't try it
09:19:00 <flwang1> better try next one
09:19:10 <flwang1> anyway, it's not the main problem we're facing now
09:19:21 <flwang1> strigazi: i'd like to see your comments
09:19:30 <flwang1> did you test the fcos driver recently?
09:19:39 <strigazi> I am completely lost with what you are saying
09:19:49 <flwang1> strigazi: hah
09:19:53 <strigazi> I am testing as we speak
09:19:58 <brtknr> we are talking about 2 different issues
09:20:03 <flwang1> in short, master branch doesn't work for me
09:20:06 <brtknr> 1 is that fcos 31 is broken
09:20:28 <brtknr> 2. on master branch, fcos 30 is broken
09:21:01 <strigazi> I have some ideas about 2.
09:21:09 <strigazi> but i need to verify
09:21:24 <flwang1> strigazi: what i have seen is
09:21:35 <brtknr> strigazi: so for me, it works until the minions spawn
09:21:49 <brtknr> but the network plugins complain about subnet manager
09:21:56 <flwang1> the os will be restarted when the heat agent run the scripts, before or after the configure_kubernetes_master.sh
09:22:49 <brtknr> flwang1: did you try with the latest master branch flwang1? that might have been because of installing empty helm chart
09:23:01 <brtknr> that got fixed in the metrics_server patch
09:23:12 <flwang1> brtknr: i did
09:23:37 <flwang1> and i also tried back to 1 months ago or even older
09:23:57 <brtknr> also only ussuri-dev hca works, because train-stable doesnt have python binary
09:24:07 <flwang1> if strigazi have no idea, then we can discuss this offline
09:24:24 <flwang1> since this may be hard to figure out in this meeting
09:24:27 <brtknr> flwang1: i also see the instance restarting issue
09:24:27 <strigazi> I will fix it today. no worries.
09:24:37 <flwang1> strigazi: hey man
09:24:47 <brtknr> strigazi: can you explain what you think the problem is?
09:24:47 <flwang1> strigazi: what's the problem?
09:25:05 <brtknr> it will save me banging my head against the wall
09:25:11 <strigazi> don't know yet, I'll find soon :)
09:25:39 <brtknr> lol
09:26:05 <flwang1> brtknr: if strigazi can't fix it today, should we ask him to buy a beer for us when we meet at Vancouver?
09:26:05 <brtknr> well, i think we need to hold off 9.2.0 release until we merge the fix
09:26:22 <strigazi> sure thing
09:26:38 <brtknr> flwang1: strigazi: btw i have to tell you guys, i will be off for 1 month in january as i am expecting to be a daddy
09:26:53 <strigazi> xD excellent news
09:27:01 <flwang1> strigazi: cool, i have taken the log as a snapshot with my phone
09:27:16 <flwang1> brtknr: that's great
09:27:25 <flwang1> brtknr: first baby?
09:27:26 <strigazi> brtknr when are you off?
09:27:42 <flwang1> i will be in holiday for next 2 weeks
09:27:42 <brtknr> s/baby/babies
09:27:56 <flwang1> so this should be our last meeting of 2019
09:27:56 <brtknr> they're going to be twins
09:28:18 <flwang1> brtknr: that's fabulous
09:28:33 <brtknr> off from ~27 Dec until 1 Feb ish
09:28:54 <brtknr> I'll be working hard over xmas :P
09:29:29 <flwang1> brtknr:  i know twins is very hard
09:29:33 <flwang1> you're lucky man
09:30:10 <brtknr> :D thanks, looking forward to the sleep deprivation.
09:30:17 <strigazi> congrats again Bharat, this is really cool.
09:30:55 <strigazi> shall we end early? I think we can focus in 9.2.0
09:31:17 <strigazi> and latest fedora coreos
09:31:28 <flwang1> strigazi: did you test v1.17?
09:31:34 <flwang1> brtknr: ^
09:31:48 <brtknr> thanks guys
09:31:51 <brtknr> https://review.opendev.org/#/c/699504
09:32:01 <strigazi> I'm doing them in one shot. fedora core 31, master, v1.17.0
09:32:20 <flwang1> strigazi: ok, good, good luck
09:32:21 <brtknr> strigazi: are you using the "stable" image
09:32:42 <flwang1> strigazi: brtknr: so there is no meeting in the next 2 week
09:32:46 <flwang1> weeks
09:32:51 <flwang1> are you ok with that?
09:33:15 <flwang1> strigazi: what's your xmas plan?
09:33:22 <flwang1> i will be back on 6 Jan
09:33:23 <strigazi> yes, i think it will be more.
09:33:37 <strigazi> I'm back on the 8th not sure ontime for the meeting.
09:33:54 <flwang1> then let's skip that one as well
09:34:16 <flwang1> let's have a quick chat on 15th Jan then, ok?
09:34:17 <brtknr> yes :( so the next one is likely to be 15th Jan
09:34:26 <flwang1> strigazi: ^
09:34:27 <brtknr> I will try to pop by and say hello
09:34:40 <flwang1> brtknr: you don't have to, stay with your babies
09:34:46 <flwang1> and the mom
09:34:51 <strigazi> sure thing
09:34:53 <strigazi> 15th
09:34:56 <flwang1> cool
09:35:06 <flwang1> i will send out an email to community
09:35:08 <strigazi> hm, wait I have a presentation that day
09:35:22 <flwang1> strigazi: oh, yes, i do as well
09:35:22 <brtknr> I'll  have already spent 2 weeks with the family by that time :) so no problem
09:35:48 <strigazi> Let's sort it out via email this week
09:35:49 <flwang1> i will be in Australia for Linux Conf
09:36:00 <brtknr> So 22 Jan
09:36:01 <strigazi> I present some not so exciting news on calico and flannel
09:36:26 <flwang1> so far 22 Jan works
09:36:51 <flwang1> let's say 22nd Jan now
09:37:03 <strigazi> ok
09:38:05 <flwang1> anything else?
09:38:41 <strigazi> that's it for me
09:39:18 <flwang1> ok, i'm happy i can sleep earlier today :) and i'm looking forward to seeing strigazi's patch for master :D
09:39:22 <brtknr> Thats all I'd say, please tick this off: https://review.opendev.org/699504 and look forward to your mystery fix for fcos 31 + k8s 1.17.0 strigazi
09:39:35 <flwang1> hahahahhahahhaha
09:39:48 <brtknr> then we can release 9.2.0
09:40:01 <flwang1> strigazi:  i will buy strigazi a beer if he can fix it tomorrow
09:40:17 <flwang1> his today
09:40:28 <strigazi> well one issue is devstack as always...
09:40:53 <strigazi> do we have a story for this?
09:41:13 <flwang1> (22:24:28) strigazi: I will fix it today. no worries.
09:41:19 <flwang1> strigazi: no we haven't
09:41:27 <strigazi> I'll ping you there
09:42:16 <brtknr> strigazi: btw what happened to the cleanup script?
09:42:41 <strigazi> ?
09:42:50 <strigazi> reviews?
09:43:06 <strigazi> haven't finished it, I'm close
09:43:14 <strigazi> let'
09:43:37 <strigazi> let's end the meeting? I will ping you
09:43:43 <brtknr> ok  thanks
09:44:19 <flwang1> #endmeeting