*** dave-mccowan has quit IRC | 00:11 | |
*** sapd1_x has joined #openstack-containers | 00:11 | |
*** sapd1_x has quit IRC | 00:21 | |
*** mrodriguez has quit IRC | 00:31 | |
*** chhagarw has joined #openstack-containers | 01:02 | |
*** chhagarw has quit IRC | 01:07 | |
*** ricolin has joined #openstack-containers | 01:08 | |
*** hongbin has joined #openstack-containers | 01:12 | |
*** absubram has quit IRC | 01:33 | |
*** dave-mccowan has joined #openstack-containers | 01:53 | |
*** dave-mccowan has quit IRC | 02:23 | |
*** ricolin has quit IRC | 02:44 | |
*** itlinux has joined #openstack-containers | 03:05 | |
*** janki has joined #openstack-containers | 03:44 | |
*** sapd1_x has joined #openstack-containers | 03:52 | |
openstackgerrit | Feilong Wang proposed openstack/magnum master: [fedora_atomic] Support auto healing for k8s https://review.openstack.org/631378 | 03:53 |
---|---|---|
*** sapd1_x has quit IRC | 04:04 | |
*** ykarel has joined #openstack-containers | 04:05 | |
*** chhagarw has joined #openstack-containers | 04:08 | |
*** hongbin has quit IRC | 04:12 | |
*** ykarel has quit IRC | 04:14 | |
*** udesale has joined #openstack-containers | 04:14 | |
*** ykarel has joined #openstack-containers | 04:17 | |
*** ramishra has joined #openstack-containers | 04:18 | |
*** ricolin has joined #openstack-containers | 05:23 | |
*** udesale has quit IRC | 05:31 | |
*** ykarel is now known as ykarel|afk | 05:32 | |
*** ykarel|afk is now known as ykarel | 05:55 | |
*** ivve has joined #openstack-containers | 06:19 | |
*** ricolin has quit IRC | 06:43 | |
*** mkuf has joined #openstack-containers | 06:50 | |
*** ykarel has quit IRC | 06:51 | |
*** ykarel has joined #openstack-containers | 06:51 | |
*** itlinux has quit IRC | 06:57 | |
*** itlinux has joined #openstack-containers | 06:58 | |
*** pcaruana has joined #openstack-containers | 07:14 | |
*** itlinux has quit IRC | 07:21 | |
*** pcaruana has quit IRC | 07:33 | |
*** pcaruana has joined #openstack-containers | 07:34 | |
*** gsimondon has joined #openstack-containers | 08:00 | |
*** ramishra has quit IRC | 08:03 | |
*** mgoddard has joined #openstack-containers | 08:06 | |
*** ramishra has joined #openstack-containers | 08:06 | |
*** ttsiouts has joined #openstack-containers | 08:08 | |
*** jaewook_oh has joined #openstack-containers | 08:09 | |
*** udesale has joined #openstack-containers | 08:09 | |
*** gsimondo1 has joined #openstack-containers | 08:20 | |
*** gsimondon has quit IRC | 08:22 | |
*** ttsiouts has quit IRC | 08:25 | |
openstackgerrit | Vishal Manchanda proposed openstack/magnum-ui master: Add nodejs10 jobs on bionic. https://review.openstack.org/644290 | 08:31 |
*** alisanhaji has joined #openstack-containers | 08:36 | |
*** flwang1 has joined #openstack-containers | 08:43 | |
flwang1 | strigazi: the resize api patch is ready, pls revisit | 08:44 |
openstackgerrit | Feilong Wang proposed openstack/magnum master: [fedora_atomic] Support auto healing for k8s https://review.openstack.org/631378 | 08:44 |
*** ttsiouts has joined #openstack-containers | 08:49 | |
*** ricolin has joined #openstack-containers | 08:58 | |
*** ykarel is now known as ykarel|lunch | 09:02 | |
*** dioguerra has joined #openstack-containers | 09:02 | |
dioguerra | Hello! | 09:02 |
dioguerra | Can we have a revision on https://review.openstack.org/#/c/604823/ please? | 09:02 |
openstackgerrit | Merged openstack/magnum-ui master: Add nodejs10 jobs on bionic. https://review.openstack.org/644290 | 09:09 |
flwang1 | dioguerra: just done a quick glance | 09:21 |
*** ramishra has quit IRC | 09:23 | |
*** ttsiouts has quit IRC | 09:31 | |
*** ttsiouts has joined #openstack-containers | 09:32 | |
*** ramishra_ has joined #openstack-containers | 09:35 | |
*** ramishra_ has quit IRC | 09:36 | |
*** ramishra_ has joined #openstack-containers | 09:36 | |
*** ykarel|lunch has quit IRC | 09:37 | |
*** ykarel has joined #openstack-containers | 09:37 | |
openstackgerrit | Merged openstack/magnum stable/rocky: k8s_fedora: Add ca_key before all deployments https://review.openstack.org/643924 | 09:51 |
brtknr | flwang1: Do you have a sec? | 10:16 |
flwang1 | brtknr: yep | 10:16 |
flwang1 | how can i help | 10:16 |
brtknr | flwang1: 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 |
brtknr | I've seen the option to do this on horizon but never understood what it does | 10:17 |
brtknr | If I redeploy the same cluster spec from scratch, things are fine again | 10:17 |
flwang1 | the rotate cert menu on horizon doesn't do anything | 10:18 |
flwang1 | because magnum doesn't support it yet | 10:18 |
brtknr | http://paste.openstack.org/show/748004/ | 10:20 |
brtknr | flwang1: oh okay... probably not anything to do with magnum then | 10:20 |
flwang1 | hmm... i never seen that before | 10:21 |
openstackgerrit | Feilong Wang proposed openstack/magnum master: New config option for default Keystone auth policy https://review.openstack.org/643225 | 10:38 |
openstackgerrit | Feilong Wang proposed openstack/magnum master: Add user guide for K8s Keystone auth https://review.openstack.org/639904 | 10:39 |
brtknr | flwang1: since when did kube_tag support become available? | 10:39 |
flwang1 | brtknr: i don't know, let me check | 10:40 |
flwang1 | brtknr: 2 years ago https://github.com/openstack/magnum/commit/46255dd4b16eccd34b9f53fc5e3dc32eaa62ce55 | 10:41 |
flwang1 | i have to go, anything else? | 10:42 |
*** janki has quit IRC | 10:45 | |
brtknr | flwang1: awesome, thanks for checking, how do you check so quickly? | 10:49 |
*** udesale has quit IRC | 10:53 | |
*** ttsiouts has quit IRC | 11:09 | |
*** rcernin has quit IRC | 11:24 | |
*** janki has joined #openstack-containers | 11:49 | |
*** dave-mccowan has joined #openstack-containers | 11:57 | |
*** ykarel is now known as ykarel|afk | 12:06 | |
*** ttsiouts has joined #openstack-containers | 12:10 | |
brtknr | strigazi: 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-0 | 12:48 |
brtknr | Doesnt a certificate get generated for the host during cluster bootstrapping? | 12:49 |
brtknr | I didn't have this problem last time | 12:49 |
brtknr | Not sure why its saying this | 12:49 |
brtknr | This is in the occm logs | 12:50 |
dioguerra | brtknr: are you using the tiller_enable flag? | 12:51 |
brtknr | No, this is on OCCM backported to queens | 12:52 |
brtknr | why? what would tiller_enable do dioguerra ? | 12:52 |
dioguerra | in my environment that error started to appear (just checking if it is from something i'm working on) | 12:54 |
*** jaewook_oh has quit IRC | 13:00 | |
*** udesale has joined #openstack-containers | 13:02 | |
brtknr | dioguerra: since when? have you changed anything? | 13:03 |
brtknr | what is your exact error? | 13:03 |
dioguerra | I don't know exactly when. | 13:07 |
dioguerra | journal 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 |
dioguerra | But this is relative to a bad/missing configuration on the metrics-server for that specific pod | 13:09 |
*** jmlowe has quit IRC | 13:19 | |
*** ykarel|afk is now known as ykarel | 13:21 | |
*** zul has quit IRC | 13:26 | |
brtknr | For me, it happens when I swap the order to Hostname,InternalIP,ExternalIP | 13:27 |
brtknr | In apiserver args | 13:27 |
brtknr | But our problems seem different | 13:28 |
*** zul has joined #openstack-containers | 13:30 | |
*** sapd1_x has joined #openstack-containers | 14:13 | |
*** hongbin has joined #openstack-containers | 14:29 | |
*** itlinux has joined #openstack-containers | 14:47 | |
*** jmlowe has joined #openstack-containers | 14:54 | |
*** sapd1_x has quit IRC | 15:19 | |
*** jmlowe has quit IRC | 15:29 | |
brtknr | My kube-proxy is constantly spitting these out: http://paste.openstack.org/show/748034/ | 15:30 |
brtknr | Mar 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-resto | 15:30 |
brtknr | It doesnt appear to be causing any problems but what does it mean? | 15:30 |
*** ykarel is now known as ykarel|away | 15:32 | |
*** ttsiouts has quit IRC | 15:38 | |
*** ttsiouts has joined #openstack-containers | 15:40 | |
*** mrodriguez has joined #openstack-containers | 15:41 | |
*** gsimondo1 has quit IRC | 15:45 | |
brtknr | Appears related to this: https://github.com/kubernetes/kubernetes/issues/73360 | 15:46 |
brtknr | Can someone check their kube-proxy logs too if you're running 1.13.4? | 15:47 |
*** ttsiouts has quit IRC | 15:54 | |
*** ttsiouts has joined #openstack-containers | 16:02 | |
*** ramishra_ has quit IRC | 16:15 | |
*** itlinux has quit IRC | 16:17 | |
*** ttsiouts has quit IRC | 16:25 | |
*** ivve has quit IRC | 16:31 | |
*** ttsiouts has joined #openstack-containers | 16:36 | |
*** itlinux has joined #openstack-containers | 16:44 | |
*** udesale has quit IRC | 16:48 | |
*** ricolin has quit IRC | 17:01 | |
*** jmlowe has joined #openstack-containers | 17:01 | |
*** jmlowe has quit IRC | 17:13 | |
*** ykarel|away has quit IRC | 17:26 | |
*** janki has quit IRC | 17:29 | |
*** jmlowe has joined #openstack-containers | 17:34 | |
*** ttsiouts has quit IRC | 17:40 | |
*** chhagarw has quit IRC | 17:56 | |
*** flwang1 has quit IRC | 17:56 | |
*** itlinux has quit IRC | 18:02 | |
*** jmlowe has quit IRC | 18:04 | |
*** ivve has joined #openstack-containers | 18:07 | |
*** SASAA has joined #openstack-containers | 18:26 | |
*** jmlowe has joined #openstack-containers | 18:47 | |
*** jmlowe has quit IRC | 18:58 | |
*** jmlowe has joined #openstack-containers | 19:16 | |
*** ttsiouts has joined #openstack-containers | 19:20 | |
*** SASAA has quit IRC | 19:43 | |
*** jmlowe has quit IRC | 19:47 | |
flwang | strigazi: do we have team meeting today? | 19:56 |
*** ttsiouts has quit IRC | 20:01 | |
*** jmlowe has joined #openstack-containers | 20:07 | |
*** itlinux has joined #openstack-containers | 20:13 | |
openstackgerrit | Spyros Trigazis proposed openstack/magnum master: Support <ClusterID>/actions/resize API https://review.openstack.org/638572 | 20:13 |
flwang | strigazi: thanks for fixing the typo | 20:16 |
*** SASAA has joined #openstack-containers | 20:16 | |
SASAA | hi! | 20:16 |
SASAA | Is it possible to install Magnum on vmware VIO? or how does this work to implement? | 20:16 |
flwang | do you mean a release note to highlight swarm can't support remove specific node? | 20:16 |
SASAA | VIO = Vmware Integrated Openstack | 20:16 |
flwang | SASAA: i can't see why it can't be | 20:17 |
flwang | i'm not familiar with VIO, but magnum is just like the other openstack services | 20:17 |
flwang | SASAA: if you can get other services work, then magnum is same | 20:17 |
SASAA | yeah that the question, i don´t know how to install additional services on the vmware infra for openstack | 20:19 |
flwang | SASAA: we're using puppet, so puppet should work for you as well | 20:20 |
openstackgerrit | Feilong Wang proposed openstack/python-magnumclient master: (WIP) Support resize api https://review.openstack.org/644676 | 20:22 |
SASAA | that is puppet ? | 20:22 |
SASAA | i meen: That is packstack ? | 20:22 |
SASAA | mean | 20:22 |
flwang | SASAA: just normal puppet module | 20:27 |
flwang | i never played packstack, for dev, i use devstack, for prod, we use puppet+ansible | 20:27 |
SASAA | ah ok:) | 20:30 |
SASAA | the Vmware VIO works a bit different with the deployment | 20:31 |
flwang | SASAA: i see, can't you ask your vendor to help? | 20:31 |
SASAA | i am a student so i have no connections :) | 20:32 |
SASAA | it´s for a PoC for a school project | 20:32 |
flwang | if it's a poc, then it should be easy | 20:34 |
flwang | just install magnum from source code | 20:35 |
flwang | and run it as a normal python app | 20:35 |
SASAA | magnum is already a additional services that we want | 20:36 |
SASAA | it´s not required to manage everything with magnum | 20:36 |
flwang | hmm... so it depends on the scope of your POC | 20:36 |
SASAA | and we want a to have a nice project :) | 20:37 |
flwang | if the scope is how to deploy, instead of how to config it, then it's a different story | 20:37 |
SASAA | vmware vio is already a additional services we are doing | 20:38 |
*** alisanhaji has quit IRC | 20:39 | |
SASAA | openstack is a part of the project | 20:39 |
SASAA | we could run openstack on a basic laptop with a few gb of memory for testing purposes | 20:40 |
SASAA | but we want to run it on a dedicated host and we found that VIO exists so that would we a nice function to implement | 20:40 |
SASAA | it more a real usecase | 20:40 |
*** ttsiouts has joined #openstack-containers | 20:54 | |
strigazi | #startmeeting containers | 21:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:00 |
*** openstack changes topic to " (Meeting topic: containers)" | 21:00 | |
strigazi | #topic Roll Call | 21:00 |
openstack | The meeting name has been set to 'containers' | 21:00 |
*** openstack changes topic to "Roll Call (Meeting topic: containers)" | 21:00 | |
strigazi | o/ | 21:00 |
flwang | o/ | 21:00 |
ttsiouts | o/ | 21:00 |
flwang | strigazi: what's the agenda today? | 21:04 |
strigazi | #topic Announcements | 21:05 |
*** openstack changes topic to "Announcements (Meeting topic: containers)" | 21:05 | |
strigazi | I gave it some mins for anyone else to join. | 21:05 |
strigazi | in a few hours flwang will be the new PTL :) https://governance.openstack.org/election/ | 21:06 |
strigazi | like in two I think | 21:06 |
strigazi | is that correct? | 21:06 |
flwang | strigazi: i think it's true :) | 21:07 |
strigazi | premature congrats :) | 21:07 |
flwang | strigazi: thanks, man. I still need you're around | 21:07 |
ttsiouts | flwang: congrats! | 21:07 |
strigazi | I will be :) | 21:07 |
flwang | i'm mostly like a coordinator of the team | 21:08 |
strigazi | it is indeed | 21:08 |
strigazi | now, for the meeting | 21:08 |
strigazi | #topic Stories/Tasks | 21:08 |
*** openstack changes topic to "Stories/Tasks (Meeting topic: containers)" | 21:08 | |
strigazi | I think for resize we are good to merge | 21:09 |
strigazi | resize on update failed works fine for me | 21:09 |
strigazi | maybe we can add later docs that resize works with nova uuid or just the index | 21:09 |
strigazi | for kube-te5lhgvs36ep-minion-5, you can just say nodes_to_remove = ["5"] | 21:10 |
strigazi | +2 | 21:10 |
flwang | strigazi: cool, i will add a document to explain the auto scaling, auto healing and includes resize api | 21:10 |
strigazi | just in the reno we need to say that for swarm is not implemented, the nodes_to_remove part | 21:11 |
flwang | it could be a useful user guide | 21:11 |
flwang | strigazi: i will update the releasenote in the api ref patch, is that ok for you? | 21:11 |
strigazi | yeah, no prob. I added +2 | 21:11 |
flwang | cheers | 21:11 |
strigazi | for fips, I'm testing the patch: https://review.openstack.org/#/c/641547/ it is a very manual process :( | 21:12 |
colin- | sorry i'm late | 21:13 |
colin- | congrats flwang | 21:13 |
strigazi | colin-: welcome | 21:13 |
flwang | strigazi: what is 'very manual'? | 21:13 |
flwang | colin-: thanks | 21:13 |
colin- | ty strigazi for looking after it this past year (more?) | 21:13 |
strigazi | flwang: all combinations | 21:13 |
strigazi | colin-: almost two :) | 21:13 |
colin- | earned a rest then! | 21:13 |
flwang | strigazi: yep, sometimes flexible means complicated :( | 21:14 |
strigazi | flwang: fips, master_lb, master_lb_fip | 21:14 |
strigazi | colin-: let's see xD | 21:14 |
strigazi | flwang: with ttsiouts we incoreporated the chnage in NGs using conditions and queens as tempalte version | 21:15 |
*** SASAA has quit IRC | 21:15 | |
flwang | strigazi: ah? | 21:16 |
flwang | so we have to upgrade heat to queens? | 21:16 |
strigazi | flwang: we added this label in the WIP templates. | 21:16 |
flwang | label for what? | 21:16 |
strigazi | for the new driver. Not for the existing one | 21:16 |
flwang | ah, i see | 21:17 |
strigazi | this label https://review.openstack.org/#/c/641547/12/doc/source/user/index.rst@387 | 21:17 |
strigazi | flwang: you run heat queens, no? | 21:17 |
flwang | strigazi: we're on queens | 21:18 |
strigazi | cool | 21:18 |
flwang | i haven't got time to test lxkong's FIP patch, does the latest PS work for you? | 21:18 |
strigazi | I haven't tested all paths | 21:19 |
strigazi | I'll finish in a bit | 21:19 |
flwang | great, thanks | 21:20 |
flwang | i know it's a tough job | 21:20 |
strigazi | I'll stay a bit late today to finish the upgrade patch too | 21:20 |
strigazi | I can't in the office xD | 21:20 |
strigazi | flwang: any comments for nodegroups? | 21:21 |
strigazi | colin-: fyi: https://review.openstack.org/#/q/status:open+project:openstack/magnum+branch:master+topic:magnum_nodegroups | 21:21 |
flwang | strigazi: i just left a raw comments to suggest use min_node_count and max_node_count | 21:21 |
flwang | so that it's consistent with node_count and i'm using min_node_count and max_node_count for auto scaling and healing | 21:22 |
strigazi | the patches with (zuul +1) are ready. | 21:22 |
strigazi | ok | 21:22 |
flwang | min_nodes is a bit blur | 21:22 |
strigazi | which patchset? | 21:22 |
flwang | strigazi: i haven't got time go through all of them yet | 21:22 |
flwang | the first one, db schema change | 21:22 |
strigazi | flwang: I deployed with an existing cluster (created before NGs) and it works fine. | 21:23 |
strigazi | after the DB migration | 21:23 |
flwang | including all patches? | 21:23 |
strigazi | all current patches that have +1 from zuul | 21:23 |
ttsiouts | flwang: thanks for the review, I will update the PS | 21:23 |
colin- | will take a look at these strigazi thanks | 21:24 |
flwang | ttsiouts: it would be nice if you can add api ref for node groups api | 21:24 |
strigazi | colin-: the actual changes for custom drives shouldn't be a lot | 21:24 |
flwang | and user guide about how to use it | 21:24 |
ttsiouts | flwang: sure, I am on it | 21:24 |
flwang | ttsiouts: great | 21:25 |
ttsiouts | strigazi: should I update the spec to reflect the new names in the fields? e.g s/max_nodes/max_node_count? | 21:25 |
strigazi | yeap | 21:25 |
ttsiouts | cool | 21:25 |
flwang | strigazi: ttsiouts: are you happy with the new name? | 21:26 |
strigazi | flwang: works for me | 21:26 |
ttsiouts | flwang: I think it's better | 21:26 |
ttsiouts | what you proposed | 21:27 |
flwang | cool | 21:28 |
ttsiouts | strigazi, flwang: would an "autoscaled" flag make sense? | 21:28 |
ttsiouts | or should we treat it as a label in each NG? | 21:28 |
flwang | i'm going to use 'auto_scaling_enabled' | 21:28 |
flwang | to be consistent with the other services enabled labels | 21:28 |
flwang | ah, sorry | 21:29 |
flwang | you mean a label/flag against a NG? | 21:29 |
strigazi | flwang: I'm ok with field or label | 21:29 |
strigazi | ttsiouts: ^^ | 21:29 |
ttsiouts | flwang: yes, either a field or a label | 21:29 |
flwang | label is better for some reasons, though it's a bit out of control | 21:30 |
ttsiouts | flwang: in general the nodegroup will inherit labels from the cluster. | 21:30 |
ttsiouts | flwang: overriding them has some problems.. | 21:31 |
flwang | i'm using 'auto_scaling_enabled' https://review.openstack.org/#/c/631378/16/magnum/drivers/common/templates/kubernetes/fragments/enable-auto-healing.sh@209 | 21:31 |
flwang | if so, will it cause problems if we have another field for autoscaling | 21:31 |
ttsiouts | flwang: it should be fine I think | 21:32 |
flwang | ttsiouts: so you prefer to have it as a field? | 21:32 |
ttsiouts | flwang: the only thing about labels is that it would be better if we had an operator like "append" to the cluster's labels of sort | 21:33 |
strigazi | I think it would be better but I don't have a strong opinion | 21:33 |
strigazi | (swarm doesn't have it, but probably will never have it) | 21:34 |
ttsiouts | strigazi: yeah.. | 21:34 |
strigazi | it's up to us :) | 21:34 |
strigazi | it doesn't matter for swarm, it can be always false | 21:34 |
ttsiouts | flwang: I don't have strong feelings either | 21:35 |
flwang | ttsiouts: if you do think it's better using 'field', then i'm ok with that | 21:35 |
flwang | ttsiouts: the only thing i'm concerning is the conflicts between auto scaling/healing labels and the field of the NG | 21:35 |
flwang | if you're sure there is no problem, i'm happy | 21:36 |
ttsiouts | flwang: I'll try to check more offline and I'll get back to you on that | 21:36 |
strigazi | with labels the validation is done in the driver, it doesn't make a difference field/label | 21:36 |
flwang | ttsiouts: cool | 21:37 |
strigazi | anything else on this? | 21:38 |
flwang | i'm good, i will do more review, thanks for the great work | 21:39 |
ttsiouts | strigazi: I'm not sure about the update nodegroup api | 21:39 |
ttsiouts | resize makes more sense and it already includes nodegroups... | 21:39 |
*** itlinux has quit IRC | 21:40 | |
strigazi | flwang: ttsiouts I think if the update of NGs doesn't only resize, we can keep resize | 21:40 |
ttsiouts | strigazi: makes sense | 21:40 |
flwang | strigazi: yep, agree, for update, it definitely does more | 21:40 |
strigazi | you mean, makes more sense? | 21:41 |
ttsiouts | strigazi: I meant I agree with you | 21:41 |
ttsiouts | :) | 21:42 |
strigazi | flwang: Do you agree too? | 21:42 |
flwang | keep both update and resize for NG? | 21:43 |
strigazi | no | 21:43 |
strigazi | keep resize, if update doesn't do anything else | 21:43 |
flwang | just like what we have now for cluster update? | 21:44 |
strigazi | yes | 21:44 |
flwang | sure, i agree with that | 21:44 |
strigazi | cool | 21:44 |
ttsiouts | flwang: strigazicool | 21:44 |
strigazi | ttsiouts: anything else for NGs? | 21:44 |
ttsiouts | strigazi: I'll update the PS asap | 21:45 |
strigazi | cool | 21:45 |
strigazi | flwang: ngs (not the new driver necessarily, DB and API) and stein, thoughts? | 21:46 |
flwang | you mean get NG api and db change in stein? | 21:47 |
strigazi | yes | 21:47 |
flwang | i'm ok with that, if the api can throw a nice error | 21:48 |
strigazi | when trying to add a NG? | 21:48 |
flwang | say something like "please go to push strigazi to get it done' | 21:48 |
flwang | personally, i'd like to get NG in stein if we can | 21:49 |
flwang | ttsiouts: ^ are you confident that? | 21:49 |
strigazi | I'm ok with that :) | 21:49 |
colin- | when is our deadline for review in that case? | 21:49 |
colin- | (remind me, plz) | 21:49 |
strigazi | whithin 10 days | 21:49 |
colin- | wow ok | 21:49 |
strigazi | within 10 days | 21:49 |
flwang | https://releases.openstack.org/stein/schedule.html | 21:49 |
ttsiouts | flwang: we need to review the changes | 21:50 |
colin- | assuming that is well underway already/ | 21:50 |
flwang | ttsiouts: yep, sure | 21:50 |
colin- | NG peer review | 21:50 |
strigazi | API and DB are implemented | 21:50 |
flwang | ttsiouts: but we also want to understand if the owner is confidient the work is ready ;) | 21:51 |
strigazi | we can create a set of test tmr to validate | 21:51 |
strigazi | we can create a set of tests tmr to validate | 21:51 |
flwang | the db change looks good to me as long as the name being changed | 21:51 |
flwang | i can approve the db change | 21:51 |
ttsiouts | flwang: cool | 21:51 |
flwang | i will start to review the api change today | 21:52 |
ttsiouts | flwang: thanks! | 21:52 |
flwang | ttsiouts: thank you for your great work | 21:52 |
strigazi | flwang: ttsiouts I think if we prove that, creating a cluster in rocky, do the migration, scale the cluster in stein is pretty good | 21:52 |
strigazi | I have tried this two weeks ago | 21:53 |
flwang | strigazi: we're running out of time | 21:53 |
strigazi | correct | 21:53 |
flwang | for release and this meeting ;) | 21:53 |
flwang | rolling upgrade pls | 21:53 |
strigazi | let's wrap then | 21:53 |
strigazi | I'm staying late offline though | 21:54 |
strigazi | I'll ping you | 21:54 |
flwang | cool, i really really appreciate that | 21:54 |
colin- | ttyl, is the link earlier the best view of outstanding ng reviews? | 21:54 |
colin- | gerrit still confuses me | 21:54 |
strigazi | colin-: thanks for talking a look to ngs | 21:54 |
strigazi | yes | 21:54 |
strigazi | this branch https://review.openstack.org/#/q/topic:magnum_nodegroups+(status:open+OR+status:merged) | 21:55 |
flwang | colin-: you guys comments are more than welcome, pls review it | 21: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 |
flwang | i think now only CC, CERN and Blizzard are around | 21:56 |
strigazi | and brtknr stackHPC :) | 21:56 |
flwang | ah, yes | 21:56 |
flwang | brtknr: apologize | 21:57 |
strigazi | see you around all | 21:58 |
flwang | strigazi: thank you | 21:58 |
strigazi | #endmeeting | 21:58 |
*** openstack changes topic to "OpenStack Containers Team" | 21:58 | |
openstack | Meeting ended Tue Mar 19 21:58:27 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 21:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/containers/2019/containers.2019-03-19-21.00.html | 21:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/containers/2019/containers.2019-03-19-21.00.txt | 21:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/containers/2019/containers.2019-03-19-21.00.log.html | 21:58 |
strigazi | flwang: I'm diving to my devstack, see you later | 21:58 |
*** pcaruana has quit IRC | 22:08 | |
eandersson | o/ | 22:08 |
eandersson | I keep forgetting about the time change -_- | 22:08 |
flwang | strigazi: ping me if you need any help | 22:10 |
*** itlinux has joined #openstack-containers | 22:16 | |
openstackgerrit | Merged openstack/magnum master: Support <ClusterID>/actions/resize API https://review.openstack.org/638572 | 22:16 |
*** rcernin has joined #openstack-containers | 22:16 | |
openstackgerrit | Spyros Trigazis proposed openstack/magnum master: ng-1: Add nodegroup representation https://review.openstack.org/604823 | 22:17 |
openstackgerrit | Spyros Trigazis proposed openstack/magnum master: ng-2: Preparation for nodegroups https://review.openstack.org/642007 | 22:17 |
openstackgerrit | Spyros Trigazis proposed openstack/magnum master: ng-3: Adapt conductor cluster handler https://review.openstack.org/642008 | 22:17 |
openstackgerrit | Spyros Trigazis proposed openstack/magnum master: ng-4: Adapt existing drivers https://review.openstack.org/642009 | 22:17 |
openstackgerrit | Spyros Trigazis proposed openstack/magnum master: ng-5: Adapt cluster object https://review.openstack.org/642010 | 22:17 |
*** itlinux has quit IRC | 22:27 | |
flwang | ttsiouts: still around? | 22:30 |
ttsiouts | flwang: yeap | 22:30 |
flwang | why do we have to have 'docker_volume_size' for NG> | 22:30 |
ttsiouts | flwang: it was designed this way so that we can either inherit from the cluster or be able to override in case it is needed | 22:31 |
flwang | ttsiouts: ah, i can see the point now, thanks | 22:33 |
ttsiouts | flwang: cool | 22:34 |
flwang | ttsiouts: and the role is just a flexible string for user to tag the NG? | 22:34 |
flwang | i mean the 'role' field | 22:34 |
ttsiouts | flwang: yes | 22:34 |
ttsiouts | flwang: actually only the master role will be reserved | 22:35 |
flwang | what do you mean ' the master role'? | 22:35 |
ttsiouts | flwang: master role means that the nodegroup conatains master nodes | 22:36 |
ttsiouts | s/conatains/contains | 22:36 |
flwang | ttsiouts: interesting, why the NG could include master nodes? | 22:37 |
flwang | in other words, when we say NG, the N means node and in k8s world, it should be the worker nodes, no? | 22:38 |
ttsiouts | flwang: a use case would be to have master nodes spread across availability zones | 22:38 |
brtknr | O/ | 22:39 |
flwang | ttsiouts: that's a good reason, what happened if we containerized the master nodes in the future? anything we should keep in mind? | 22:40 |
openstackgerrit | Feilong Wang proposed openstack/magnum master: New config option for default Keystone auth policy https://review.openstack.org/643225 | 22:40 |
ttsiouts | flwang: hmmm | 22:41 |
ttsiouts | flwang: I have to think about this one | 22:41 |
flwang | ttsiouts: 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 Train | 22:42 |
ttsiouts | flwang: yes sounds really interesting | 22:43 |
openstackgerrit | Feilong Wang proposed openstack/magnum master: New config option for default Keystone auth policy https://review.openstack.org/643225 | 22:48 |
*** ttsiouts has quit IRC | 22:51 | |
brtknr | Sorry 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 |
flwang | brtknr: no problem, my friend | 23:01 |
flwang | and i'm really happy to see you and stackHPC are around with us for the k8s journey, looking forward more contribution/input from your side | 23:01 |
*** hongbin has quit IRC | 23:25 | |
*** henriqueof has joined #openstack-containers | 23:36 | |
*** mrodriguez has quit IRC | 23:53 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!