Tuesday, 2018-07-24

*** livelace2 has quit IRC00:10
*** livelace2 has joined #openstack-containers00:10
*** shu-mutow has joined #openstack-containers00:12
*** itlinux has quit IRC00:13
*** threestrands has quit IRC00:38
*** hongbin has joined #openstack-containers00:39
openstackgerritFeilong Wang proposed openstack/magnum master: Add README.rst and Makefile for heat-container-agent  https://review.openstack.org/58506100:44
*** rcernin_ has joined #openstack-containers00:56
*** rcernin has quit IRC00:58
*** yamamoto has joined #openstack-containers01:20
*** yamamoto has quit IRC01:24
*** Bhujay has joined #openstack-containers01:24
*** ricolin has joined #openstack-containers01:43
*** armaan has quit IRC02:19
*** armaan has joined #openstack-containers02:20
*** jmlowe has joined #openstack-containers02:23
*** dave-mccowan has quit IRC02:31
*** ramishra has joined #openstack-containers03:01
*** vijaykc4 has joined #openstack-containers03:04
*** Bhujay has quit IRC03:17
*** pengdake has joined #openstack-containers03:26
*** adrianreza has quit IRC03:34
*** vijaykc4 has quit IRC03:38
*** jmlowe has quit IRC03:43
*** lpetrut has joined #openstack-containers03:53
*** mdnadeem has joined #openstack-containers03:58
*** ykarel has joined #openstack-containers04:03
*** armaan has quit IRC04:15
*** hongbin has quit IRC04:16
*** armaan has joined #openstack-containers04:18
*** pengdake has quit IRC04:27
*** lpetrut has quit IRC04:42
*** vijaykc4 has joined #openstack-containers05:00
*** yasemin has quit IRC05:02
*** armaan has quit IRC05:05
*** armaan has joined #openstack-containers05:06
*** armaan has quit IRC05:09
*** pc_m has quit IRC05:09
*** armaan has joined #openstack-containers05:10
*** pc_m has joined #openstack-containers05:13
*** vijaykc4 has quit IRC05:39
*** armaan has quit IRC05:43
*** armaan has joined #openstack-containers05:44
*** mjura has joined #openstack-containers05:44
*** yamamoto has joined #openstack-containers05:46
*** yamamoto has quit IRC05:48
*** yamamoto has joined #openstack-containers05:56
*** yamamoto has quit IRC06:00
*** adrianc_ has joined #openstack-containers06:00
*** adrianc__ has joined #openstack-containers06:01
*** adrianc_ has quit IRC06:05
*** janki has joined #openstack-containers06:06
*** yasemin has joined #openstack-containers06:08
*** adrianc__ has quit IRC06:20
*** gsimondon has joined #openstack-containers06:24
*** armaan_ has joined #openstack-containers06:26
*** armaan has quit IRC06:29
*** lpetrut has joined #openstack-containers06:33
*** pcaruana has joined #openstack-containers06:34
*** ispp has joined #openstack-containers07:05
*** udesale has joined #openstack-containers07:06
*** ykarel is now known as ykarel|lunch07:33
*** lpetrut has quit IRC07:48
*** AlexeyAbashkin has joined #openstack-containers07:50
*** mjura has quit IRC07:53
*** lpetrut has joined #openstack-containers07:55
*** Bhujay has joined #openstack-containers07:55
*** rcernin_ has quit IRC07:56
*** janki has quit IRC07:58
*** janki has joined #openstack-containers07:58
*** Bhujay has quit IRC08:07
openstackgerritMerged openstack/magnum master: Switch to stestr  https://review.openstack.org/58210008:09
*** yamamoto has joined #openstack-containers08:09
*** rcernin_ has joined #openstack-containers08:10
*** shu-mutow has quit IRC08:18
openstackgerritVu Cong Tuan proposed openstack/python-magnumclient master: Switch to stestr  https://review.openstack.org/58516808:19
*** ykarel|lunch is now known as ykarel08:21
openstackgerritVu Cong Tuan proposed openstack/magnum-tempest-plugin master: Switch to stestr  https://review.openstack.org/58517208:24
*** yamamoto has quit IRC08:26
*** ispp has quit IRC08:30
*** armaan_ has quit IRC08:34
*** parasitid has quit IRC08:34
*** armaan has joined #openstack-containers08:34
*** ispp has joined #openstack-containers08:38
flwang1strigazi: do we have meeting today?08:40
strigaziyes08:41
flwang1strigazi: ok, cool08:41
openstackgerritVu Cong Tuan proposed openstack/python-magnumclient master: Switch to stestr  https://review.openstack.org/58516808:42
*** ricolin has quit IRC08:42
strigaziflwang1: I faced a new first in openstack08:49
strigaziflwang1: works in production, doesn't work in devstack!08:49
flwang1strigazi: what's the problem?08:51
*** parasitid has joined #openstack-containers08:52
strigaziflwang1: kubernetes v1.11.1 works in production but it doesn't in devstack, I get E0724 08:52:02.604927       1 authentication.go:62] Unable to authenticate the request due to an error: x509: certificate specifies an incompatible key usage on the api.08:52
*** mjura has joined #openstack-containers08:56
*** vijaykc4 has joined #openstack-containers09:01
*** janki has quit IRC09:01
*** vijaykc4 has quit IRC09:05
*** vijaykc4 has joined #openstack-containers09:05
*** udesale has quit IRC09:06
*** vijaykc4 has quit IRC09:06
*** armaan has quit IRC09:07
*** armaan has joined #openstack-containers09:08
*** skyscraper has quit IRC09:09
*** skyscraper has joined #openstack-containers09:13
flwang1strigazi: any difference between your prod and devstack?09:16
strigaziflwang1: DNS09:16
strigaziflwang1: in prod we have dns09:17
flwang1strigazi: ok, i will try the 1.11.1 image09:17
flwang1does it work for 1.11.0?09:18
strigaziflwang1: I will try09:20
strigaziflwang1: it is the same image the 1.11.1 in prod and devstack09:21
*** udesale has joined #openstack-containers09:28
*** vijaykc4 has joined #openstack-containers09:37
*** gsimondo1 has joined #openstack-containers09:42
*** gsimondon has quit IRC09:45
*** vijaykc4 has quit IRC09:49
*** vijaykc4 has joined #openstack-containers09:50
flwang1strigazi: ok, btw, should we followup the functional testing on openlab?09:51
flwang1currently, without functional testing making things tricky09:52
strigaziflwang1 openlab testing would be a good idea, but I don't know what they want from us or how to communicate things09:54
strigaziflwang1: in this case it wouldn't help whatsoever09:54
flwang1strigazi: what i'm thinking is, because we can't do it with current openstack infra, so we HAVE TO look after any other way to do that09:55
strigaziflwang1 I know, I spend months on this and I gave up09:55
flwang1otherwise, we will be fxxked in the future09:55
flwang1strigazi: ok, i will try and see what can i do09:56
strigazino we won't, it just more difficult to accept changes09:56
flwang1strigazi: ok, for example, if we have a working function test, shit like this https://review.openstack.org/#/c/584215/ won't happen09:57
flwang1ok, i know it's not a good sample09:58
flwang1but you got my point, we have too many corners need to be covered09:58
strigaziI have pinged hogepodge dims and mnaser about openlab testing. My feeling is and I'm extremely confident about that there is not space for magnum in openlab testing.09:59
strigaziI'm mentioning this ^^ because it is not overlooked by me.10:01
strigaziflwang1: 1.11.0 works :(10:01
flwang1strigazi: ok, got it10:01
strigazi#startmeeting containers10:02
openstackMeeting started Tue Jul 24 10:02:01 2018 UTC and is due to finish in 60 minutes.  The chair is strigazi. Information about MeetBot at http://wiki.debian.org/MeetBot.10:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.10:02
*** openstack changes topic to " (Meeting topic: containers)"10:02
strigazi#topic Roll Call10:02
openstackThe meeting name has been set to 'containers'10:02
*** openstack changes topic to "Roll Call (Meeting topic: containers)"10:02
flwang1strigazi: if so, there are probably some regression issues10:02
flwang1we may need review the changes between 1.11.1 and 1.11.010:02
flwang1o/10:02
strigazio/10:02
strigazi#topic Blueprints/Bugs/Ideas10:03
*** openstack changes topic to "Blueprints/Bugs/Ideas (Meeting topic: containers)"10:03
flwang1strigazi: seems there are always only you and me in this meeting10:03
strigazi#topic meeting time10:04
flwang1maybe we can merge the two meetings10:04
*** openstack changes topic to "meeting time (Meeting topic: containers)"10:04
slunkadhi10:04
strigaziI could late night for me, early for you and normal for blizzard?10:05
strigazislunkad: hello10:05
*** sfilatov has joined #openstack-containers10:05
strigaziflwang1: 2100 UTC ?10:06
flwang1strigazi: 2100UTC means 10AM, IIRC10:07
flwang1for NZ time10:07
strigazi1400 for west coast10:07
strigazi0900 for NZ10:08
strigazi2300 Europe10:08
strigaziflwang1: thoughts?10:09
flwang1works for me10:10
strigazifor europe I'm present in working hours10:10
strigaziI can setup something like office hours10:10
strigaziTuesday mornings10:10
flwang1strigazi: that would be nice10:10
strigaziSo if someone wants something can find me for sure.10:10
strigaziIMO, for our case we should push things in th ML10:11
strigazislunkad: what do you think about office hours?10:11
flwang1totally agree, we can put more our discussion in the ML10:11
strigaziit is like a meeting but without minutes. it is still logged.10:12
slunkadstrigazi: what do you mean like setting it up as your status on irc?10:12
strigazino, in the wiki page I'll post that this time and day someone will be on the channel10:13
strigaziwell for europe me10:14
slunkadok ya that sounds good10:14
flwang1strigazi: i can cover the NZ/AP time if it's helpful10:15
strigaziok then, Tuesdays at 1300 UTC europe maybe east coast for me10:15
strigaziflwang1: for you?10:16
strigaziyou can pick a time that you are online and it is day :)10:16
strigaziyou can pick a time that you are online and it is daytime :)10:16
flwang1strigazi: yep10:16
slunkaddoes that mean the thursday meeting will not happen?10:16
flwang1probably My Thursday morning10:16
strigaziwe can move the meeting on Tuesdays 2100 or 2200 UTC10:17
strigazi2100 UTC is a go?10:18
strigaziflwang1: ^^10:19
flwang1strigazi: works for me10:19
strigazi#agreed meeting moves to Tuesdays 2100 UTC10:20
strigaziWe can do it today10:20
strigazitmr for you flwang110:20
flwang1strigazi: sure10:21
strigaziNext week I'll be on holidays. We can still have a meeting and flwang1 chairs it?10:22
flwang1strigazi: no problem10:22
flwang1i will call you if there is question i can't answer10:22
strigazi:)10:22
strigazioffice hours Tuesdays at 1300 UTC for me10:23
*** vijaykc4 has quit IRC10:24
strigaziflwang1: do you want to set office hours?10:24
*** vijaykc4 has joined #openstack-containers10:24
flwang1strigazi: let me check the UTC time of mine10:24
*** vijaykc4 has quit IRC10:25
*** vijaykc4 has joined #openstack-containers10:26
flwang1Wed UTC 10:00PM - 11:00PM10:26
strigazipm?10:26
flwang1PM means my AM, and it may work for others, like afternoon10:27
flwang1i don't know10:27
flwang1or i can put mine later10:28
strigazioh, so 2200 UTc ok10:28
strigazisounds good10:28
strigazi#agreed office hours for strigazi  Tuesdays at 1300 UTC and Wednesdays 2200 UTC for flwang110:29
flwang1cool10:30
strigazi#topic Blueprints/Bugs/Ideas10:30
*** openstack changes topic to "Blueprints/Bugs/Ideas (Meeting topic: containers)"10:30
strigaziFor me, I'll push to finish the upgrade API to have it in rocky, server and client by Friday. flwang1 I'll need you help for reviews.10:31
flwang1strigazi: no problem, i'm keen to review it10:31
strigaziThe implementation will do inplace upgrades I haven't managed to do the replace with draining.10:33
strigaziAnd secondly, I'll investigate the issue with kube v1.11.110:34
strigaziv1.11.0 and v1.11.1 work at the CERN cloud and they pass the conformance tests.10:34
strigaziv1.11.0 works on devstack, but v1.11.1 doesn't10:35
strigaziThere is an issue with RBAC or certs10:35
strigaziI might try a devstack with designate enabled.10:35
*** vijaykc4 has quit IRC10:36
strigaziThe only big difference is that in t production we have DNS and authentication is done with the node names.10:36
strigazinode name == hostname10:36
strigazikube node name == hostname == nova vm name10:37
flwang1that's possible10:37
strigaziwhat is possible?10:37
flwang1i mean maybe related to DNS10:38
strigazithat it is for th millionth time DNS? :)10:38
*** vijaykc4 has joined #openstack-containers10:38
strigazithat it is for the millionth time DNS? :)10:38
flwang1no, maybe related the hostname something10:38
strigazihttp://i.imgur.com/eAwdKEC.png10:38
strigaziI couldn't resist10:39
strigaziI'm investigating, it is good dive in how auth works in k8s10:39
flwang1i like the paint, typical chinese paint10:39
flwang1strigazi: yep, as for auth, did you ever put some effort on the best practice of k8s security?10:40
flwang1since I didn't see there is a sig-security in k8s community10:40
flwang1so i'm wondering if there is team caring about it10:40
strigaziAFAIK we are doing the best possible. apart from selinux...10:41
strigaziafter adding calico we covered the policy part too.10:41
flwang1selinux is another topic, i don't think we still need to disable it, right?10:41
strigaziwe could have a label10:42
strigaziif selinux is on10:42
strigaziuser will need to modify their temlates with the appropriate labeling10:42
strigazithe security-context in the pod spec10:43
strigazihttps://kubernetes.io/docs/setup/independent/install-kubeadm/10:44
strigaziDisabling SELinux by running setenforce 0 is required to allow containers to access the host filesystem, which is required by pod networks for example. You have to do this until SELinux support is improved in the kubelet.10:44
strigaziI have by passed all the issues with selinux on but I'm not very confident on having it on10:45
flwang1strigazi: ok, is kubeadm doing the same?10:46
strigaziyeap10:46
strigazibut it works with selinux on10:46
*** sfilatov_ has joined #openstack-containers10:47
strigaziwe can follow this offline with help from #fedora10:47
flwang1strigazi: ok, cool10:48
strigaziTo conclude, the cluster in queens and master are secure. After that, it is on the cluster admin to deploy apps securely.10:48
strigazithat is it from me.10:49
flwang1cool10:49
sfilatov_I have a question: how do we cope with upgrades in case of one of the k8s manifests needs to be changed?10:49
*** sfilatov has quit IRC10:50
sfilatov_For example when I upgraded k8s from 1.9.8 to 1.10 I faced an issue with grafana manifest10:50
sfilatov_image version for grafana needs to be bumped10:50
sfilatov_Will the new upgrade logic allow us to upgrade this version?10:51
strigaziversions are easy to bump10:51
strigaziwhereever we have a label with the tag10:51
flwang1strigazi: as long as we pass it as a label i think10:51
strigazithe agent will run apply and bump it.10:52
flwang1but for grafana, IIRC, we're hardcode the version10:52
*** rcernin_ has quit IRC10:52
strigazifor grafana yes10:52
sfilatov_So upgrade should support versions?10:52
sfilatov_i mean labels*10:52
strigaziyes10:52
strigazisince kube_tag is a label10:53
strigazithe same applies for all10:53
sfilatov_So the idea is to pass all the needed labels10:54
sfilatov_openstack coe cluster upgrade <cluster name or id> \10:54
sfilatov_   --masters \10:54
sfilatov_   --rollback \10:54
sfilatov_   --batch-size <size> \10:54
sfilatov_   --parameters key1=val1,...,keyN=valN10:54
sfilatov_like in this spec?10:54
strigazisfilatov_: can you push a patch for the missing ones?10:54
sfilatov_yes, I can do that10:55
strigazicoredns and the monitoing ones10:55
sfilatov_OK10:55
sfilatov_Also could you tell the status for cluster_healing and nodepools?10:56
sfilatov_Looks like they are on hold10:56
sfilatov_Are there any plans on getting back to them?10:57
strigaziwe can have the moniting in (which is required for healing)10:57
strigazinodegroups won't make it in Rocky10:57
strigazifor autohealing we can have it10:58
sfilatov_didn't quite get it10:58
sfilatov_we are talking about heat autohealing, right?10:58
strigazino10:58
strigazimagnum will monitor the cluster nodes10:59
sfilatov_is there a patch for this?10:59
strigazithis the 1st part, it will basically ask the api if the nodes are ok.10:59
sfilatov_I haven't seen it10:59
strigaziflwang1: has one10:59
sfilatov_Kubernetes API?10:59
strigaziyes10:59
flwang1sfilatov_: wait a sec11:00
flwang1https://review.openstack.org/57081811:00
flwang1https://review.openstack.org/57289711:00
sfilatov_I guess it's okay for the first part, but generally would be better to get notifications from it11:00
sfilatov_flwang1: thx!11:00
sfilatov_strigazi: >nodegroups won't make it in Rocky11:00
flwang1sfilatov_: no problem11:00
strigazisfilatov_: openstack notifications?11:00
strigazisfilatov_: user notifications?11:01
strigazithese are veeery different things.11:01
flwang1sfilatov_: i think magnum can send openstack notifications out for the status change11:01
strigaziflwang1: ^^ this easy and very doable11:01
flwang1strigazi: yep11:02
sfilatov_we have a lot of issues11:02
strigazisfilatov_: we have someone that just started working again in nodegroups but there is space for more people. In any case nodegroups will be in the next release (Rocky)11:02
strigazisfilatov_: what issues?11:03
sfilatov_when K8s api is not available11:03
sfilatov_for some reason11:03
sfilatov_that's why I like it better when nodes send notifications11:03
sfilatov_but I guess we can talk about it in patch set11:03
strigaziwe can ask kubelet\11:04
strigazicurl https://$KUBELET_IP:10250/healthz == 'ok'11:04
sfilatov_yeah11:04
strigazipolling11:04
sfilatov_I'll check the patches then11:04
strigazinot pushing11:04
sfilatov_and will comment it offline11:04
strigaziok11:05
sfilatov_strigazi: And if you plan on adding push-upgrades11:05
sfilatov_how do you implement master/minions?11:05
sfilatov_I mean I thought you need some kind of nodepools for that11:05
strigaziI'll ping you in the review.11:05
sfilatov_thx11:05
strigaziwe have two now, master and minion11:05
strigaziLet's wrap them. I'll send a summary in the ML and cc you11:06
flwang1strigazi: thanks11:06
strigaziWe need to use the ML11:06
sfilatov_thx11:06
strigazibefore closing11:06
flwang1currently, i just finished the multi region issue and mainly focus on our magnum deployment11:06
strigazisfilatov_: flwang1 slunkad if tou have time, test v1.11.0 seems to work well11:07
*** sfilatov_ has quit IRC11:07
strigaziI'll continue on v1.11.111:07
flwang1strigazi: it's on my list now11:07
strigaziflwang1: great news \o/11:07
flwang1strigazi: yep, i'm so excited about that11:07
*** sfilatov has joined #openstack-containers11:07
strigaziwe are going multiregion here too, we'll need to talk11:08
strigazilet's wrap, we are 9 mins late11:08
strigaziok?11:08
strigazisaid once11:09
*** sfilatov has quit IRC11:09
*** sfilatov has joined #openstack-containers11:09
strigazisaid twice11:09
strigaziThanks for joining folks!11:09
strigazi#endmeeting11:10
*** openstack changes topic to "OpenStack Containers Team"11:10
openstackMeeting ended Tue Jul 24 11:10:03 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)11:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/containers/2018/containers.2018-07-24-10.02.html11:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/containers/2018/containers.2018-07-24-10.02.txt11:10
openstackLog:            http://eavesdrop.openstack.org/meetings/containers/2018/containers.2018-07-24-10.02.log.html11:10
*** sfilatov has quit IRC11:10
*** sfilatov has joined #openstack-containers11:10
*** yamamoto_ has joined #openstack-containers11:14
*** sfilatov has quit IRC11:14
*** sfilatov has joined #openstack-containers11:14
*** sfilatov has quit IRC11:14
*** sfilatov has joined #openstack-containers11:16
*** sfilatov has quit IRC11:16
*** yamamoto_ has quit IRC11:27
*** udesale has quit IRC11:28
*** sfilatov has joined #openstack-containers11:33
*** yasufum has joined #openstack-containers11:41
*** yasufum_ has joined #openstack-containers11:43
*** yasufum has quit IRC11:45
*** yasufum has joined #openstack-containers11:46
*** vijaykc4 has quit IRC11:47
*** yasufum_ has quit IRC11:48
*** serlex has joined #openstack-containers11:49
*** linkmark has joined #openstack-containers11:54
*** yasufum_ has joined #openstack-containers11:54
*** yasufum has quit IRC11:56
*** yasufum_ is now known as yasufum11:56
*** sfilatov_ has joined #openstack-containers11:58
*** sfilatov has quit IRC11:58
*** vijaykc4 has joined #openstack-containers12:00
*** sfilatov has joined #openstack-containers12:00
*** sfilatov_ has quit IRC12:03
*** yasufum has quit IRC12:04
*** strigazi has quit IRC12:13
*** strigazi has joined #openstack-containers12:14
*** armaan has quit IRC12:26
*** armaan has joined #openstack-containers12:26
*** ispp has quit IRC12:39
*** ispp has joined #openstack-containers12:59
*** flwang1 has quit IRC13:05
*** flwang1 has joined #openstack-containers13:06
*** ianychoi has quit IRC13:08
*** ianychoi has joined #openstack-containers13:08
*** dave-mccowan has joined #openstack-containers13:11
*** dave-mcc_ has joined #openstack-containers13:20
*** dave-mccowan has quit IRC13:22
*** ricolin has joined #openstack-containers13:30
*** gsimondo1 has quit IRC13:59
*** ykarel is now known as ykarel|away14:04
*** mjura has quit IRC14:05
*** jmlowe has joined #openstack-containers14:12
*** ykarel|away has quit IRC14:12
*** mdnadeem has quit IRC14:15
*** sfilatov_ has joined #openstack-containers14:21
*** sfilatov has quit IRC14:21
*** armaan has quit IRC14:37
*** armaan has joined #openstack-containers14:38
*** jmlowe has quit IRC14:41
*** markguz has joined #openstack-containers14:43
*** janki has joined #openstack-containers14:45
*** markguz_ has joined #openstack-containers14:49
*** markguz has quit IRC14:52
*** vijaykc4 has quit IRC14:54
*** udesale has joined #openstack-containers14:56
*** hongbin has joined #openstack-containers15:00
*** rcernin_ has joined #openstack-containers15:05
*** hongbin has quit IRC15:08
*** hongbin has joined #openstack-containers15:08
*** udesale has quit IRC15:18
*** lpetrut has quit IRC15:19
*** ispp has quit IRC15:26
*** rcernin_ has quit IRC15:30
*** pcaruana has quit IRC15:32
*** lpetrut has joined #openstack-containers15:39
*** ispp has joined #openstack-containers15:41
*** itlinux has joined #openstack-containers15:49
*** lpetrut has quit IRC15:52
*** lpetrut has joined #openstack-containers16:03
*** ispp has quit IRC16:04
openstackgerritSpyros Trigazis proposed openstack/magnum master: WIP: build images in the ci  https://review.openstack.org/58542016:09
*** serlex has quit IRC16:10
openstackgerritAndrei Ozerov proposed openstack/magnum master: Trustee: provide region_name to auth_url searching  https://review.openstack.org/58294716:22
*** ricolin has quit IRC16:39
*** mjura has joined #openstack-containers16:39
*** markguz has joined #openstack-containers16:40
*** markguz_ has quit IRC16:43
*** vijaykc4 has joined #openstack-containers16:44
*** mgoddard has joined #openstack-containers17:06
*** itlinux_ has joined #openstack-containers17:07
*** itlinux has quit IRC17:09
*** AlexeyAbashkin has quit IRC17:11
*** lpetrut has quit IRC17:16
*** ramishra has quit IRC17:17
*** armaan has quit IRC17:25
canori01Just to clarify, so Tuesday meetings will move to 2200 UTC and no Thursday meetings?17:39
*** itlinux_ has quit IRC17:42
*** itlinux has joined #openstack-containers17:42
*** vijaykc4 has quit IRC17:56
*** ykarel has joined #openstack-containers18:02
*** sfilatov_ has quit IRC18:02
*** zerick has quit IRC18:16
*** zerick_ has joined #openstack-containers18:16
*** ykarel is now known as ykarel|away18:33
*** zerick_ has quit IRC18:40
*** zerick has joined #openstack-containers18:41
*** itlinux has quit IRC18:54
*** mgoddard has quit IRC18:56
*** armaan has joined #openstack-containers18:57
*** itlinux has joined #openstack-containers19:02
*** itlinux has quit IRC19:03
*** ykarel|away is now known as mdnadeem19:03
*** mdnadeem has quit IRC19:03
*** mdnadeem has joined #openstack-containers19:03
*** mdnadeem has quit IRC19:08
*** canori01 has quit IRC19:15
*** armaan has quit IRC19:24
*** armaan has joined #openstack-containers19:25
*** armaan has quit IRC19:29
*** spiette has quit IRC19:40
*** spiette has joined #openstack-containers19:44
*** flwang1 has quit IRC19:55
*** rtjure has quit IRC19:57
*** itlinux has joined #openstack-containers19:59
*** canori01 has joined #openstack-containers20:06
imdigitaljimstigazi: flwang1: will be at the #meetings tuesday :)20:14
*** rcernin_ has joined #openstack-containers20:19
*** janki has quit IRC20:31
openstackgerritSpyros Trigazis proposed openstack/magnum master: WIP: build images in the ci  https://review.openstack.org/58542020:53
strigaziimdigitaljim flwang canori01 meeting?20:57
*** flwang1 has joined #openstack-containers20:57
*** rtjure has joined #openstack-containers20:58
strigaziteam?21:01
flwangyes21:02
flwangi'm here21:02
strigaziimdigitaljim canori01 ?21:02
strigaziflwang:  it doesn't make a lot of sense to make a meeting the two of us right? :)21:03
strigaziflwang: Was the email unclear?21:03
flwangyes, let's skip it then21:03
flwangprobably because of the title of the mail21:04
flwangso not much people follow it?21:04
strigazibtw this seems to be working: https://review.openstack.org/58542021:04
*** jmlowe has joined #openstack-containers21:05
flwangfantastic21:05
flwangbut why the heat-container-agent image is being removed?21:06
strigaziit is not removed21:06
strigaziit is moved to /dockerfiles21:06
strigazito have all containers under one dir21:07
strigaziIt doesn't make sense to you?21:07
strigaziit was a shameless porting from openstack/loci21:08
flwangstrigazi: ok, i'm reviewing it again21:08
flwangmy fault, it's rename, not remove, my eyes !21:09
strigazithe last patchset was to copy the logs21:09
flwangcan we do the name convention then?21:10
imdigitaljimhere21:10
imdigitaljimsorry21:10
imdigitaljimive been working on a kubernetes cloud controller cleanup process using software deployment lifecycle hook21:11
imdigitaljimflwang1: great work with the heat-container-agent btw, i had been watching that and I appreciate the recent changes21:11
flwangimdigitaljim: thank you, that's a tricky because it needs a lot of collaboration from Heat and other teams21:12
imdigitaljimalso we thought the first meeting was next week21:12
imdigitaljimour misunderstanding21:12
imdigitaljimstrigazi: ^21:13
imdigitaljimsorry i havent caught up some of my PR's, we've been pushing forward to get some operational and are going to upstream the changes after we can confirm much of it is indeed working21:14
strigaziimdigitaljim: no worries21:14
imdigitaljimin addition to some new features21:14
strigaziimdigitaljim: you have multiple regions too?21:14
imdigitaljimyeah21:14
imdigitaljimmany regions21:15
strigazione magnum to rule them all?21:15
imdigitaljimno a magnum in each region21:15
imdigitaljimalthough some components such as keystone cross multiple regions21:16
flwangimdigitaljim: same architecture at here21:16
imdigitaljimflwang1: good to know21:16
strigaziflwang: you will have many magnum deployments?21:17
flwangstrigazi: yes21:17
imdigitaljimwell for us technically HA magnum in each region21:18
flwangone for each region21:18
strigaziand many heats?21:18
flwangstrigazi: yes21:18
flwangpls don't tell me bas story21:18
flwangbad21:18
strigaziflwang: no, I don't have any story21:19
strigazi:)21:19
strigazibtw I have a magnificent story21:19
colin-also here, sorry to be late21:19
strigaziabout the issue with v1.11.x21:19
strigaziSo 1.11.x was working perfectly in our production cloud but it wasn't working on devstack21:20
imdigitaljimi noticed 1.11.1 had some minor config changes needed to work21:21
strigazithe reason is that in 1.11 kubelet is proxing connections from the apiserver to the pods21:21
imdigitaljimwere running on 1.11.0 right now though21:21
flwangstrigazi: any reason we have to bump the rocky release to 1.11.1?21:22
imdigitaljimoh the error i had was related to invalid certificate key usages21:22
strigaziand kubelet was trying to server the container stream to localhost21:22
strigazibut the hyperkube container has the /etc/hosts file empty and clouldn't resolve localhost to 127.0.0.121:23
flwangstrigazi: so you have figured out the root cause?21:23
strigaziwell, at CERN we have out DNS and guess what, the dns resolves localhost.cern.ch to 127.0.0.1!!!21:24
strigazihence it was working inprod21:24
imdigitaljimoh interesting21:24
imdigitaljimill keep an eye out for that as well21:24
strigazithe solution was simple, mount /etc/hosts to the kubelet system container21:24
imdigitaljimwe also didnt notice that DNS issue21:24
flwangimdigitaljim: that's only for 1.11.1 as you mentioned you're using 1.11.021:25
strigaziafter that it worked21:25
strigaziflwang: in the end it was both21:25
flwangstrigazi: will you propose a patch?21:25
strigaziyes21:25
flwangnice21:25
imdigitaljimflwang: no i mean i tried 1.11.1 briefly to see if we could just move to that without issue21:26
strigazias soon as I fixed I cooked the builder to propose this patch in our repo21:26
imdigitaljimand it was failing based on some invalid keyusage21:26
flwangok21:26
imdigitaljimi didnt spend much time on it after that but ill keep @strigazi:21:26
imdigitaljimin mind21:27
strigaziimdigitaljim  the key usage comes from the above, double checking now.21:28
strigaziimdigitaljim: you can notice that the apiserver runs correctly but as soon as the kubelet tries to join the errors start to occur21:29
imdigitaljimstrigazi: yeah i figured, i just didnt correlate that to /etc/hosts at the time, ill check it out as well21:29
imdigitaljimthe info is much appreciated21:29
*** rcernin_ has quit IRC21:30
strigaziI need to check if we need /etc/hosts in all containers21:30
imdigitaljimdid you say you were just adding them as a mount to config.json.template21:31
strigaziyes21:31
imdigitaljimperfect21:31
imdigitaljimill validate my issue and give that a shot in a bit21:32
flwanggreat21:32
flwangbtw, imdigitaljim as for the k8s cluster deployed by magnum, have you done any security audit?21:32
imdigitaljimwe have no yet, we're waiting to have the resource cleanup fixed before we say we have an "MVP"21:33
flwangfair enough21:33
flwanglet's share what we find then in that domain21:33
imdigitaljimabsolutely21:34
imdigitaljimalso strigazi:21:34
flwangit's very critical for prod using21:34
imdigitaljimminor thing that might help you out21:34
imdigitaljimin your Dockerfiles you could use21:34
imdigitaljimARG KUBE_VERSION21:34
imdigitaljimFROM gcr.io/google-containers/kube-apiserver-amd64:$KUBE_VERSION21:34
imdigitaljimas the first 2 lines21:34
imdigitaljimand use --build-arg KUBE_VERSION={some param}21:35
imdigitaljimin the build to make updating a little easier21:35
imdigitaljimhttps://gitlab.cern.ch/cloud/atomic-system-containers/blob/cern-qa/kubernetes-apiserver/Dockerfile#L121:35
imdigitaljimso you might be able to do updates easier21:35
imdigitaljimif that works for your CI21:36
*** itlinux has quit IRC21:38
strigazisounds good21:38
strigaziimdigitaljim: in the apiserver the error didn't went away yet21:39
imdigitaljimoh that invalid error i was talking about?21:39
strigaziimdigitaljim: flwang the kubelet error was fixed though21:39
strigaziimdigitaljim: yes21:39
flwangcool\21:42
strigaziSo, 1.11.0 is fixed. 1.11.1 needs some more work with rbac21:43
imdigitaljimyeah, thats where were at as well21:43
imdigitaljim1.11.0 is good as is 1.11.1 needs some work21:44
imdigitaljimis it rbac or how we have our certs signed21:44
flwang1.11.0 is good means no any work?21:44
strigaziin the CERN work though :(21:44
strigaziin the CERN cloud work though :(21:44
flwang1.11.1 nees works, but have we figured out what we need to do?21:44
strigaziflwang: no, in 1.11.1 we miss something21:45
strigaziwe don't know why21:45
imdigitaljimwell if it works in the cern cloud still perhaps we can use it as a model for what is different =)21:45
strigaziin 1.11.0 we found the solution, we just need to push the images21:45
strigaziimdigitaljim: put localhost in the DNS server21:46
imdigitaljimyeah21:46
strigazifolks, I need to go, see you tmr21:47
imdigitaljimthanks for the discussion21:47
imdigitaljimtake care21:47
imdigitaljimo/21:47
colin-have a good one21:47
strigazihave a nice day all21:47
strigaziflwang: I might catch you later for you, tmr for me :)21:47
strigazibye21:47
cbrummstrigazi: thanks for the meeting time change21:47
strigazicbrumm: you are welcome21:48
flwangcy21:51
openstackgerritSpyros Trigazis proposed openstack/magnum master: WIP: build images in the ci  https://review.openstack.org/58542021:58
openstackgerritSpyros Trigazis proposed openstack/magnum master: WIP: build images in the ci  https://review.openstack.org/58542022:01
*** jmlowe has quit IRC22:14
*** rcernin has joined #openstack-containers22:30
*** hongbin has quit IRC22:30
*** markguz has quit IRC23:10
*** yolanda_ has joined #openstack-containers23:56
*** linkmark has quit IRC23:57
*** yolanda has quit IRC23:58

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