Tuesday, 2019-03-19

*** dave-mccowan has quit IRC00:11
*** sapd1_x has joined #openstack-containers00:11
*** sapd1_x has quit IRC00:21
*** mrodriguez has quit IRC00:31
*** chhagarw has joined #openstack-containers01:02
*** chhagarw has quit IRC01:07
*** ricolin has joined #openstack-containers01:08
*** hongbin has joined #openstack-containers01:12
*** absubram has quit IRC01:33
*** dave-mccowan has joined #openstack-containers01:53
*** dave-mccowan has quit IRC02:23
*** ricolin has quit IRC02:44
*** itlinux has joined #openstack-containers03:05
*** janki has joined #openstack-containers03:44
*** sapd1_x has joined #openstack-containers03:52
openstackgerritFeilong Wang proposed openstack/magnum master: [fedora_atomic] Support auto healing for k8s  https://review.openstack.org/63137803:53
*** sapd1_x has quit IRC04:04
*** ykarel has joined #openstack-containers04:05
*** chhagarw has joined #openstack-containers04:08
*** hongbin has quit IRC04:12
*** ykarel has quit IRC04:14
*** udesale has joined #openstack-containers04:14
*** ykarel has joined #openstack-containers04:17
*** ramishra has joined #openstack-containers04:18
*** ricolin has joined #openstack-containers05:23
*** udesale has quit IRC05:31
*** ykarel is now known as ykarel|afk05:32
*** ykarel|afk is now known as ykarel05:55
*** ivve has joined #openstack-containers06:19
*** ricolin has quit IRC06:43
*** mkuf has joined #openstack-containers06:50
*** ykarel has quit IRC06:51
*** ykarel has joined #openstack-containers06:51
*** itlinux has quit IRC06:57
*** itlinux has joined #openstack-containers06:58
*** pcaruana has joined #openstack-containers07:14
*** itlinux has quit IRC07:21
*** pcaruana has quit IRC07:33
*** pcaruana has joined #openstack-containers07:34
*** gsimondon has joined #openstack-containers08:00
*** ramishra has quit IRC08:03
*** mgoddard has joined #openstack-containers08:06
*** ramishra has joined #openstack-containers08:06
*** ttsiouts has joined #openstack-containers08:08
*** jaewook_oh has joined #openstack-containers08:09
*** udesale has joined #openstack-containers08:09
*** gsimondo1 has joined #openstack-containers08:20
*** gsimondon has quit IRC08:22
*** ttsiouts has quit IRC08:25
openstackgerritVishal Manchanda proposed openstack/magnum-ui master: Add nodejs10 jobs on bionic.  https://review.openstack.org/64429008:31
*** alisanhaji has joined #openstack-containers08:36
*** flwang1 has joined #openstack-containers08:43
flwang1strigazi: the resize api patch is ready, pls revisit08:44
openstackgerritFeilong Wang proposed openstack/magnum master: [fedora_atomic] Support auto healing for k8s  https://review.openstack.org/63137808:44
*** ttsiouts has joined #openstack-containers08:49
*** ricolin has joined #openstack-containers08:58
*** ykarel is now known as ykarel|lunch09:02
*** dioguerra has joined #openstack-containers09:02
dioguerraHello!09:02
dioguerraCan we have a revision on https://review.openstack.org/#/c/604823/ please?09:02
openstackgerritMerged openstack/magnum-ui master: Add nodejs10 jobs on bionic.  https://review.openstack.org/64429009:09
flwang1dioguerra: just done a quick glance09:21
*** ramishra has quit IRC09:23
*** ttsiouts has quit IRC09:31
*** ttsiouts has joined #openstack-containers09:32
*** ramishra_ has joined #openstack-containers09:35
*** ramishra_ has quit IRC09:36
*** ramishra_ has joined #openstack-containers09:36
*** ykarel|lunch has quit IRC09:37
*** ykarel has joined #openstack-containers09:37
openstackgerritMerged openstack/magnum stable/rocky: k8s_fedora: Add ca_key before all deployments  https://review.openstack.org/64392409:51
brtknrflwang1: Do you have a sec?10:16
flwang1brtknr: yep10:16
flwang1how can i help10:16
brtknrflwang1: every now and again, I get https curl error in my k8s cluster deployed using magnum... do the certificates need to be renewed?10:17
brtknrI've seen the option to do this on horizon but never understood what it does10:17
brtknrIf I redeploy the same cluster spec from scratch, things are fine again10:17
flwang1the rotate cert menu on horizon doesn't do anything10:18
flwang1because magnum doesn't support it yet10:18
brtknrhttp://paste.openstack.org/show/748004/10:20
brtknrflwang1: oh okay... probably not anything to do with magnum then10:20
flwang1hmm... i never seen that before10:21
openstackgerritFeilong Wang proposed openstack/magnum master: New config option for default Keystone auth policy  https://review.openstack.org/64322510:38
openstackgerritFeilong Wang proposed openstack/magnum master: Add user guide for K8s Keystone auth  https://review.openstack.org/63990410:39
brtknrflwang1: since when did kube_tag support become available?10:39
flwang1brtknr: i don't know, let me check10:40
flwang1brtknr: 2 years ago https://github.com/openstack/magnum/commit/46255dd4b16eccd34b9f53fc5e3dc32eaa62ce5510:41
flwang1i have to go, anything else?10:42
*** janki has quit IRC10:45
brtknrflwang1: awesome, thanks for checking, how do you check so quickly?10:49
*** udesale has quit IRC10:53
*** ttsiouts has quit IRC11:09
*** rcernin has quit IRC11:24
*** janki has joined #openstack-containers11:49
*** dave-mccowan has joined #openstack-containers11:57
*** ykarel is now known as ykarel|afk12:06
*** ttsiouts has joined #openstack-containers12:10
brtknrstrigazi: flwang1: do you know why this is happening: Error from server: Get https://k8s-demo-qrzd3bntjffi-master-0:10250/containerLogs/kube-system/openstack-cloud-controller-manager-55z2s/openstack-cloud-controller-manager?follow=true: x509: certificate is valid for kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, not k8s-demo-qrzd3bntjffi-master-012:48
brtknrDoesnt a certificate get generated for the host during cluster bootstrapping?12:49
brtknrI didn't have this problem last time12:49
brtknrNot sure why its saying this12:49
brtknrThis is in the occm logs12:50
dioguerrabrtknr: are you using the tiller_enable flag?12:51
brtknrNo, this is on OCCM backported to queens12:52
brtknrwhy? what would tiller_enable do dioguerra ?12:52
dioguerrain my environment that error started to appear (just checking if it is from something i'm working on)12:54
*** jaewook_oh has quit IRC13:00
*** udesale has joined #openstack-containers13:02
brtknrdioguerra: since when? have you changed anything?13:03
brtknrwhat is your exact error?13:03
dioguerraI don't know exactly when.13:07
dioguerrajournal kube-apiserver.srv : Mar 18 04:20:02 dash-hldxn4bpaxe2-master-0.novalocal runc[2507]: W0318 04:20:02.299527       1 x509.go:172] x509: subject with cn=system:node:dash-hldxn4bpaxe2-minion-0 is not in the allowed list: [front-proxy-client kube kubernetes]13:08
dioguerraBut this is relative to a bad/missing configuration on the metrics-server for that specific pod13:09
*** jmlowe has quit IRC13:19
*** ykarel|afk is now known as ykarel13:21
*** zul has quit IRC13:26
brtknrFor me, it happens when I swap the order to Hostname,InternalIP,ExternalIP13:27
brtknrIn apiserver args13:27
brtknrBut our problems seem different13:28
*** zul has joined #openstack-containers13:30
*** sapd1_x has joined #openstack-containers14:13
*** hongbin has joined #openstack-containers14:29
*** itlinux has joined #openstack-containers14:47
*** jmlowe has joined #openstack-containers14:54
*** sapd1_x has quit IRC15:19
*** jmlowe has quit IRC15:29
brtknrMy kube-proxy is constantly spitting these out: http://paste.openstack.org/show/748034/15:30
brtknrMar 19 15:29:16 k8s-demo-n7mwfmzoeg2q-master-0.novalocal runc[3922]: E0319 15:29:16.110952       1 proxier.go:1335] Failed to execute iptables-restore: exit status 2 (iptables-resto15:30
brtknrIt doesnt appear to be causing any problems but what does it mean?15:30
*** ykarel is now known as ykarel|away15:32
*** ttsiouts has quit IRC15:38
*** ttsiouts has joined #openstack-containers15:40
*** mrodriguez has joined #openstack-containers15:41
*** gsimondo1 has quit IRC15:45
brtknrAppears related to this: https://github.com/kubernetes/kubernetes/issues/7336015:46
brtknrCan someone check their kube-proxy logs too if you're running 1.13.4?15:47
*** ttsiouts has quit IRC15:54
*** ttsiouts has joined #openstack-containers16:02
*** ramishra_ has quit IRC16:15
*** itlinux has quit IRC16:17
*** ttsiouts has quit IRC16:25
*** ivve has quit IRC16:31
*** ttsiouts has joined #openstack-containers16:36
*** itlinux has joined #openstack-containers16:44
*** udesale has quit IRC16:48
*** ricolin has quit IRC17:01
*** jmlowe has joined #openstack-containers17:01
*** jmlowe has quit IRC17:13
*** ykarel|away has quit IRC17:26
*** janki has quit IRC17:29
*** jmlowe has joined #openstack-containers17:34
*** ttsiouts has quit IRC17:40
*** chhagarw has quit IRC17:56
*** flwang1 has quit IRC17:56
*** itlinux has quit IRC18:02
*** jmlowe has quit IRC18:04
*** ivve has joined #openstack-containers18:07
*** SASAA has joined #openstack-containers18:26
*** jmlowe has joined #openstack-containers18:47
*** jmlowe has quit IRC18:58
*** jmlowe has joined #openstack-containers19:16
*** ttsiouts has joined #openstack-containers19:20
*** SASAA has quit IRC19:43
*** jmlowe has quit IRC19:47
flwangstrigazi: do we have team meeting today?19:56
*** ttsiouts has quit IRC20:01
*** jmlowe has joined #openstack-containers20:07
*** itlinux has joined #openstack-containers20:13
openstackgerritSpyros Trigazis proposed openstack/magnum master: Support <ClusterID>/actions/resize API  https://review.openstack.org/63857220:13
flwangstrigazi: thanks for fixing the typo20:16
*** SASAA has joined #openstack-containers20:16
SASAAhi!20:16
SASAAIs it possible to install Magnum on vmware VIO? or how does this work to implement?20:16
flwangdo you mean a release note to highlight swarm can't support remove specific node?20:16
SASAAVIO = Vmware Integrated Openstack20:16
flwangSASAA: i can't see why it can't be20:17
flwangi'm not familiar with VIO, but magnum is just like the other openstack services20:17
flwangSASAA: if you can get other services work, then magnum is same20:17
SASAAyeah that the question, i don´t know how to install additional services on the vmware infra for openstack20:19
flwangSASAA: we're using puppet, so puppet should work for you as well20:20
openstackgerritFeilong Wang proposed openstack/python-magnumclient master: (WIP) Support resize api  https://review.openstack.org/64467620:22
SASAAthat is puppet ?20:22
SASAAi meen: That is packstack ?20:22
SASAAmean20:22
flwangSASAA: just normal puppet module20:27
flwangi never played packstack, for dev, i use devstack, for prod, we use puppet+ansible20:27
SASAAah ok:)20:30
SASAAthe Vmware VIO works a bit different with the deployment20:31
flwangSASAA: i see, can't you ask your vendor to help?20:31
SASAAi am a student so i have no connections :)20:32
SASAAit´s for a PoC for a school project20:32
flwangif it's a poc, then it should be easy20:34
flwangjust install magnum from source code20:35
flwangand run it as a normal python app20:35
SASAAmagnum is already a additional services that we want20:36
SASAAit´s not required to manage everything with magnum20:36
flwanghmm... so it depends on the scope of your POC20:36
SASAAand we want a to have a nice project :)20:37
flwangif the scope is how to deploy, instead of how to config it, then it's a different story20:37
SASAAvmware vio is already a additional services we are doing20:38
*** alisanhaji has quit IRC20:39
SASAAopenstack is a part of the project20:39
SASAAwe could run openstack on a basic laptop with a few gb of memory for testing purposes20:40
SASAAbut we want to run it on a dedicated host and we found that VIO exists so that would we a nice function to implement20:40
SASAAit more a real usecase20:40
*** ttsiouts has joined #openstack-containers20:54
strigazi#startmeeting containers21:00
openstackMeeting started Tue Mar 19 21:00:05 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: containers)"21:00
strigazi#topic Roll Call21:00
openstackThe meeting name has been set to 'containers'21:00
*** openstack changes topic to "Roll Call (Meeting topic: containers)"21:00
strigazio/21:00
flwango/21:00
ttsioutso/21:00
flwangstrigazi: what's the agenda today?21:04
strigazi#topic Announcements21:05
*** openstack changes topic to "Announcements (Meeting topic: containers)"21:05
strigaziI gave it some mins for anyone else to join.21:05
strigaziin a few hours flwang will be the new PTL :) https://governance.openstack.org/election/21:06
strigazilike in two I think21:06
strigaziis that correct?21:06
flwangstrigazi: i think it's true :)21:07
strigazipremature congrats :)21:07
flwangstrigazi: thanks, man. I still need you're around21:07
ttsioutsflwang: congrats!21:07
strigaziI will be :)21:07
flwangi'm mostly like a coordinator of the team21:08
strigaziit is indeed21:08
strigazinow, for the meeting21:08
strigazi#topic Stories/Tasks21:08
*** openstack changes topic to "Stories/Tasks (Meeting topic: containers)"21:08
strigaziI think for resize we are good to merge21:09
strigaziresize on update failed works fine for me21:09
strigazimaybe we can add later docs that resize works with nova uuid or just the index21:09
strigazifor kube-te5lhgvs36ep-minion-5, you can just say nodes_to_remove = ["5"]21:10
strigazi+221:10
flwangstrigazi: cool, i will add a document to explain the auto scaling, auto healing and includes resize api21:10
strigazijust in the reno we need to say that for swarm is not implemented, the nodes_to_remove part21:11
flwangit could be a useful user guide21:11
flwangstrigazi: i will update the releasenote in the api ref patch, is that ok for you?21:11
strigaziyeah, no prob. I added +221:11
flwangcheers21:11
strigazifor fips, I'm testing the patch: https://review.openstack.org/#/c/641547/ it is a very manual process :(21:12
colin-sorry i'm late21:13
colin-congrats flwang21:13
strigazicolin-: welcome21:13
flwangstrigazi: what is 'very manual'?21:13
flwangcolin-:  thanks21:13
colin-ty strigazi for looking after it this past year (more?)21:13
strigaziflwang: all combinations21:13
strigazicolin-: almost two :)21:13
colin-earned a rest then!21:13
flwangstrigazi: yep, sometimes flexible means complicated :(21:14
strigaziflwang: fips, master_lb, master_lb_fip21:14
strigazicolin-: let's see xD21:14
strigaziflwang: with ttsiouts we incoreporated the chnage in NGs using conditions and queens as tempalte version21:15
*** SASAA has quit IRC21:15
flwangstrigazi: ah?21:16
flwangso we have to upgrade heat to queens?21:16
strigaziflwang: we added this label in the WIP templates.21:16
flwanglabel for what?21:16
strigazifor the new driver. Not for the existing one21:16
flwangah, i see21:17
strigazithis label https://review.openstack.org/#/c/641547/12/doc/source/user/index.rst@38721:17
strigaziflwang: you run heat queens, no?21:17
flwangstrigazi: we're on queens21:18
strigazicool21:18
flwangi haven't got time to test lxkong's FIP patch, does the latest PS work for you?21:18
strigaziI haven't tested all paths21:19
strigaziI'll finish in a bit21:19
flwanggreat, thanks21:20
flwangi know it's a tough job21:20
strigaziI'll stay a bit late today to finish the upgrade patch too21:20
strigaziI can't in the office xD21:20
strigaziflwang: any comments for nodegroups?21:21
strigazicolin-: fyi: https://review.openstack.org/#/q/status:open+project:openstack/magnum+branch:master+topic:magnum_nodegroups21:21
flwangstrigazi: i just left a raw comments to suggest use min_node_count and max_node_count21:21
flwangso that it's consistent with node_count and i'm using min_node_count and max_node_count for auto scaling and healing21:22
strigazithe patches with (zuul +1) are ready.21:22
strigaziok21:22
flwangmin_nodes is a bit blur21:22
strigaziwhich patchset?21:22
flwangstrigazi: i haven't got time go through all of them yet21:22
flwangthe first one, db schema change21:22
strigaziflwang: I deployed with an existing cluster (created before NGs) and it works fine.21:23
strigaziafter the DB migration21:23
flwangincluding all patches?21:23
strigaziall current patches that have +1 from zuul21:23
ttsioutsflwang: thanks for the review, I will update the PS21:23
colin-will take a look at these strigazi thanks21:24
flwangttsiouts: it would be nice if you can add api ref for node groups api21:24
strigazicolin-: the actual changes for custom drives shouldn't be a lot21:24
flwangand user guide about how to use it21:24
ttsioutsflwang: sure, I am on it21:24
flwangttsiouts: great21:25
ttsioutsstrigazi: should I update the spec to reflect the new names in the fields? e.g s/max_nodes/max_node_count?21:25
strigaziyeap21:25
ttsioutscool21:25
flwangstrigazi: ttsiouts: are you happy with the new name?21:26
strigaziflwang: works for me21:26
ttsioutsflwang: I think it's better21:26
ttsioutswhat you proposed21:27
flwangcool21:28
ttsioutsstrigazi, flwang: would an "autoscaled" flag make sense?21:28
ttsioutsor should we treat it as a label in each NG?21:28
flwangi'm going to use 'auto_scaling_enabled'21:28
flwangto be consistent with the other services enabled labels21:28
flwangah, sorry21:29
flwangyou mean a label/flag against a NG?21:29
strigaziflwang: I'm ok with field or label21:29
strigazittsiouts: ^^21:29
ttsioutsflwang: yes, either a field or a label21:29
flwanglabel is better for some reasons, though it's a bit out of control21:30
ttsioutsflwang: in general the nodegroup will inherit labels from the cluster.21:30
ttsioutsflwang: overriding them has some problems..21:31
flwangi'm using 'auto_scaling_enabled' https://review.openstack.org/#/c/631378/16/magnum/drivers/common/templates/kubernetes/fragments/enable-auto-healing.sh@20921:31
flwangif so,  will it cause problems if we have  another field for autoscaling21:31
ttsioutsflwang: it should be fine I think21:32
flwangttsiouts: so you prefer to have it as a field?21:32
ttsioutsflwang: the only thing about labels is that it would be better if we had an operator like "append" to the cluster's labels of sort21:33
strigaziI think it would be better but I don't have a strong opinion21:33
strigazi(swarm doesn't have it, but probably will never have it)21:34
ttsioutsstrigazi: yeah..21:34
strigaziit's up to us :)21:34
strigaziit doesn't matter for swarm, it can be always false21:34
ttsioutsflwang: I don't have strong feelings either21:35
flwangttsiouts: if you do think it's better using 'field', then i'm ok with that21:35
flwangttsiouts: the only thing i'm concerning is the conflicts between auto scaling/healing labels and the field of the NG21:35
flwangif you're sure there is no problem, i'm happy21:36
ttsioutsflwang: I'll try to check more offline and I'll get back to you on that21:36
strigaziwith labels the validation is done in the driver, it doesn't make a difference field/label21:36
flwangttsiouts: cool21:37
strigazianything else on this?21:38
flwangi'm good, i will do more review, thanks for the great work21:39
ttsioutsstrigazi: I'm not sure about the update nodegroup api21:39
ttsioutsresize makes more sense and it already includes nodegroups...21:39
*** itlinux has quit IRC21:40
strigaziflwang: ttsiouts I think if the update of NGs doesn't only resize, we can keep resize21:40
ttsioutsstrigazi: makes sense21:40
flwangstrigazi: yep, agree, for update, it definitely does more21:40
strigaziyou mean, makes more sense?21:41
ttsioutsstrigazi: I meant I agree with you21:41
ttsiouts:)21:42
strigaziflwang: Do you agree too?21:42
flwangkeep both update and resize for NG?21:43
strigazino21:43
strigazikeep resize, if update doesn't do anything else21:43
flwangjust like what we have now for cluster update?21:44
strigaziyes21:44
flwangsure, i agree with that21:44
strigazicool21:44
ttsioutsflwang: strigazicool21:44
strigazittsiouts: anything else for NGs?21:44
ttsioutsstrigazi: I'll update the PS asap21:45
strigazicool21:45
strigaziflwang: ngs (not the new driver necessarily, DB and API) and stein, thoughts?21:46
flwangyou mean get NG api and db change in stein?21:47
strigaziyes21:47
flwangi'm ok with that, if the api can throw a nice error21:48
strigaziwhen trying to add a NG?21:48
flwangsay something like "please go to push strigazi to get it done'21:48
flwangpersonally, i'd like to get NG in stein if we can21:49
flwangttsiouts: ^ are you confident that?21:49
strigaziI'm ok with that :)21:49
colin-when is our deadline for review in that case?21:49
colin-(remind me, plz)21:49
strigaziwhithin 10 days21:49
colin-wow ok21:49
strigaziwithin 10 days21:49
flwanghttps://releases.openstack.org/stein/schedule.html21:49
ttsioutsflwang: we need to review the changes21:50
colin-assuming that is well underway already/21:50
flwangttsiouts: yep, sure21:50
colin-NG peer review21:50
strigaziAPI and DB are implemented21:50
flwangttsiouts: but we also want to understand if the owner is confidient the work is ready ;)21:51
strigaziwe can create a set of test tmr to validate21:51
strigaziwe can create a set of tests tmr to validate21:51
flwangthe db change looks good to me as long as the name being changed21:51
flwangi can approve the db change21:51
ttsioutsflwang: cool21:51
flwangi will start to review the api change today21:52
ttsioutsflwang: thanks!21:52
flwangttsiouts: thank you for your great work21:52
strigaziflwang: ttsiouts I think if we prove that, creating a cluster in rocky, do the migration, scale the cluster in stein is pretty good21:52
strigaziI have tried this two weeks ago21:53
flwangstrigazi: we're running out of time21:53
strigazicorrect21:53
flwangfor release and this meeting ;)21:53
flwangrolling upgrade pls21:53
strigazilet's wrap then21:53
strigaziI'm staying late offline though21:54
strigaziI'll ping you21:54
flwangcool, i really really appreciate that21:54
colin-ttyl, is the link earlier the best view of outstanding ng reviews?21:54
colin-gerrit still confuses me21:54
strigazicolin-: thanks for talking a look to ngs21:54
strigaziyes21:54
strigazithis branch https://review.openstack.org/#/q/topic:magnum_nodegroups+(status:open+OR+status:merged)21:55
flwangcolin-: you guys comments are more than welcome, pls review it21:55
colin-as many as we can think of in the remaining time :)21:55
colin-hopefully others have been generating feedback so far?21:55
flwangi think now only CC, CERN and Blizzard are around21:56
strigaziand brtknr stackHPC :)21:56
flwangah, yes21:56
flwangbrtknr: apologize21:57
strigazisee you around all21:58
flwangstrigazi: thank  you21:58
strigazi#endmeeting21:58
*** openstack changes topic to "OpenStack Containers Team"21:58
openstackMeeting ended Tue Mar 19 21:58:27 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/containers/2019/containers.2019-03-19-21.00.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/containers/2019/containers.2019-03-19-21.00.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/containers/2019/containers.2019-03-19-21.00.log.html21:58
strigaziflwang: I'm diving to my devstack, see you later21:58
*** pcaruana has quit IRC22:08
eanderssono/22:08
eanderssonI keep forgetting about the time change -_-22:08
flwangstrigazi: ping me if you need any help22:10
*** itlinux has joined #openstack-containers22:16
openstackgerritMerged openstack/magnum master: Support <ClusterID>/actions/resize API  https://review.openstack.org/63857222:16
*** rcernin has joined #openstack-containers22:16
openstackgerritSpyros Trigazis proposed openstack/magnum master: ng-1: Add nodegroup representation  https://review.openstack.org/60482322:17
openstackgerritSpyros Trigazis proposed openstack/magnum master: ng-2: Preparation for nodegroups  https://review.openstack.org/64200722:17
openstackgerritSpyros Trigazis proposed openstack/magnum master: ng-3: Adapt conductor cluster handler  https://review.openstack.org/64200822:17
openstackgerritSpyros Trigazis proposed openstack/magnum master: ng-4: Adapt existing drivers  https://review.openstack.org/64200922:17
openstackgerritSpyros Trigazis proposed openstack/magnum master: ng-5: Adapt cluster object  https://review.openstack.org/64201022:17
*** itlinux has quit IRC22:27
flwangttsiouts: still around?22:30
ttsioutsflwang: yeap22:30
flwangwhy do we have to have 'docker_volume_size' for NG>22:30
ttsioutsflwang: it was designed this way so that we can either inherit from the cluster or be able to override in case it is needed22:31
flwangttsiouts: ah, i can see the point now, thanks22:33
ttsioutsflwang: cool22:34
flwangttsiouts: and the role is just a flexible string for user to tag the NG?22:34
flwangi mean the 'role' field22:34
ttsioutsflwang: yes22:34
ttsioutsflwang: actually only the master role will be reserved22:35
flwangwhat do you mean ' the master role'?22:35
ttsioutsflwang: master role means that the nodegroup conatains master nodes22:36
ttsioutss/conatains/contains22:36
flwangttsiouts: interesting, why the NG could include master nodes?22:37
flwangin other words, when we say NG, the N means node and in k8s world, it should be the worker nodes, no?22:38
ttsioutsflwang: a use case would be to have master nodes spread across availability zones22:38
brtknrO/22:39
flwangttsiouts: that's a good reason, what happened if we containerized the master nodes in the future? anything we should keep in mind?22:40
openstackgerritFeilong Wang proposed openstack/magnum master: New config option for default Keystone auth policy  https://review.openstack.org/64322522:40
ttsioutsflwang: hmmm22:41
ttsioutsflwang: I have to think about this one22:41
flwangttsiouts: it would be nice if you can give us some ideas because i think containerize master nodes could be one of good features we will have in Train22:42
ttsioutsflwang: yes sounds really interesting22:43
openstackgerritFeilong Wang proposed openstack/magnum master: New config option for default Keystone auth policy  https://review.openstack.org/64322522:48
*** ttsiouts has quit IRC22:51
brtknrSorry to miss the meeting, I’m very bad at realising what day of the week it is, especially when it gets late! Look forward to more testing with nodegroups ttsiouts! Congrats flwang for ptl. Thanks strigazi for your service so far!22:59
flwangbrtknr: no problem, my friend23:01
flwangand i'm really happy to see you and stackHPC are around with us for the k8s journey, looking forward more contribution/input from your side23:01
*** hongbin has quit IRC23:25
*** henriqueof has joined #openstack-containers23:36
*** mrodriguez has quit IRC23:53

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!