Tuesday, 2019-09-24

*** Liang__ has joined #openstack-meeting-401:05
*** hongbin has joined #openstack-meeting-401:39
*** diablo_rojo has quit IRC01:43
*** hongbin_ has joined #openstack-meeting-401:44
*** hongbin has quit IRC01:46
*** yamamoto has joined #openstack-meeting-402:16
*** yamamoto has quit IRC02:21
*** roman_g has quit IRC02:34
*** yamamoto has joined #openstack-meeting-403:27
*** hongbin has joined #openstack-meeting-403:28
*** hongbin_ has quit IRC03:30
*** links has joined #openstack-meeting-403:33
*** hongbin has quit IRC03:38
*** hongbin has joined #openstack-meeting-403:39
*** hongbin has quit IRC03:48
*** hongbin_ has joined #openstack-meeting-403:49
*** hongbin_ has quit IRC03:49
*** bnemec has quit IRC05:09
*** igordc has quit IRC05:12
*** Luzi has joined #openstack-meeting-405:13
*** bnemec has joined #openstack-meeting-405:15
*** yamamoto has quit IRC05:48
*** slaweq has joined #openstack-meeting-406:09
*** Liang__ is now known as LiangFang06:26
*** lpetrut has joined #openstack-meeting-406:47
*** gcheresh has joined #openstack-meeting-406:52
*** pcaruana has joined #openstack-meeting-406:56
*** e0ne has joined #openstack-meeting-407:04
*** e0ne has quit IRC07:09
*** Luzi has quit IRC07:18
*** ralonsoh has joined #openstack-meeting-407:34
*** roman_g has joined #openstack-meeting-407:56
*** psachin has joined #openstack-meeting-407:59
*** jraju__ has joined #openstack-meeting-408:03
*** links has quit IRC08:04
*** liuyulong_ has joined #openstack-meeting-408:33
*** k_mouza has joined #openstack-meeting-408:37
*** k_mouza has quit IRC08:39
*** k_mouza has joined #openstack-meeting-408:39
*** mtreinish has quit IRC08:43
*** freerunner has quit IRC08:43
*** mtreinish has joined #openstack-meeting-408:44
*** stephenfin has quit IRC08:44
*** dosaboy has quit IRC08:45
*** freerunner has joined #openstack-meeting-408:45
*** stephenfin has joined #openstack-meeting-408:45
*** dosaboy has joined #openstack-meeting-408:45
*** LiangFang has quit IRC09:09
*** salmankhan has joined #openstack-meeting-409:31
*** salmankhan has quit IRC09:31
*** salmankhan has joined #openstack-meeting-409:31
*** e0ne has joined #openstack-meeting-409:54
*** e0ne has quit IRC09:55
*** e0ne has joined #openstack-meeting-409:55
*** k_mouza has quit IRC09:58
*** k_mouza has joined #openstack-meeting-409:58
*** macz has quit IRC10:10
*** openstack has joined #openstack-meeting-410:15
*** ChanServ sets mode: +o openstack10:15
*** pcaruana has quit IRC10:24
*** bobmel has joined #openstack-meeting-410:27
*** bobmel has quit IRC10:30
*** jraju__ has quit IRC10:38
*** pcaruana has joined #openstack-meeting-410:48
*** liuyulong_ has quit IRC11:06
*** rihabb has quit IRC11:57
*** fdegir has quit IRC11:57
*** fdegir has joined #openstack-meeting-411:58
*** rihabb has joined #openstack-meeting-411:58
*** roman_g has quit IRC11:59
*** roman_g has joined #openstack-meeting-411:59
*** belmoreira has joined #openstack-meeting-412:27
*** psachin has quit IRC12:49
*** bh526r has joined #openstack-meeting-412:53
*** liuyulong has joined #openstack-meeting-413:17
*** psachin has joined #openstack-meeting-413:19
*** belmoreira has quit IRC13:30
*** belmoreira has joined #openstack-meeting-413:31
*** belmoreira has quit IRC13:32
*** lkoranda has joined #openstack-meeting-413:35
*** lpetrut has quit IRC13:41
*** belmoreira has joined #openstack-meeting-414:08
*** gagehugo has joined #openstack-meeting-414:15
*** liuyulong has quit IRC14:22
*** k_mouza has quit IRC14:49
*** k_mouza_ has joined #openstack-meeting-414:49
*** belmoreira has quit IRC14:50
*** belmoreira has joined #openstack-meeting-414:51
*** jsuchome has joined #openstack-meeting-414:51
*** lkoranda has quit IRC14:53
portdirect#startmeeting openstack-helm15:00
openstackMeeting started Tue Sep 24 15:00:34 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:00
openstackThe meeting name has been set to 'openstack_helm'15:00
portdirecthey folks, lets give it a few mins for people to arrive15:00
itxaka\o15:00
itxakao/15:00
portdirectthe agenda is here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-09-2415:00
lamto/15:00
itxaka\o/15:01
*** stevthedev has joined #openstack-meeting-415:01
portdirectitxaka: good to have you back :D15:01
*** sgrasley has joined #openstack-meeting-415:01
stevthedevo/15:01
jsuchomeo/15:01
*** pcaruana has quit IRC15:01
srwilkerso/15:02
megheisler\o15:03
*** gcheresh has quit IRC15:03
howello/15:04
portdirectok - lets get going15:04
roman_go/15:04
portdirect#topic Make probe configs its own key in values?15:05
*** openstack changes topic to "Make probe configs its own key in values? (Meeting topic: openstack-helm)"15:05
portdirectitxaka: floor is yours15:05
itxakayay!15:05
itxakamainly what it says, currently the config for the probe options is mixed together with the pod policies, which in some cases makes it difficult to find them and to see what the values are15:05
itxakanot only that but we use an ugly way of printing them to the values which if I could I would burn because they are totally unreadable15:06
itxakaI value readability over commodity and tbh, htk is full of terrible unreadable things15:06
itxakaso seeing that the probe function was recently introduced, I would propose a different approach to the probes that you can see on https://review.opendev.org/#/c/683220/15:07
itxakajust a simple key for them and a toyaml in the templates15:07
itxakano more 300 chars functions that you need to look up and decipher from htk to understand what they do15:08
portdirecttheres a lot to unpack here15:08
portdirectand i certainly am no fan of the sprawl of gotpl we have in htk15:08
portdirectbut we also need to consider some of the other aspects as to why we got here15:09
portdirectwe maintain a huge number of charts in this project15:09
portdirectand key to our success is constency in configuration input to them15:10
portdirectand also the ability to make improvements across the project simply15:10
portdirectthe htk funcations as they are today enable this, and also allow us to improve uniformly as well15:10
itxakammmh...15:11
itxakaI do agree that for some parts of common functions htk is a godsend, because we can fix or improve something i one place and it gets propagated15:11
itxakabut for probes?15:11
*** k_mouza_ has quit IRC15:11
jsuchomeis there a compromise possible? function in htk but not the crazy one as it is currently but something more like itxaka's proposal?15:12
itxakais there something expected to change in the probe configuration that would warrant having a function (which actually just does toYaml) for this?15:12
portdirectitxaka: that case is accommodated for: https://github.com/openstack/openstack-helm-infra/blob/master/helm-toolkit/templates/snippets/_kubernetes_probes.tpl#L5515:13
itxakaI do understand this on endpoints or dns or something that its complex15:13
itxakabut this is pretty straigthforward and it hurts my heart to see that complexity for no good reason15:14
portdirecta good example is neutron and nova, where in production environments we many need to change the probe to refelct operating condidtions15:14
portdirectalso with a simple toyaml - how would you disable the probe if desired?15:14
itxakaif you disable the probe then you have bigger problems than complexity :p15:15
portdirectwelcome to the real world :D15:16
itxakathats actually a good point, I did not think of probe disabling as I would not expect anyone to actually disable a probe lmao15:16
itxakaok, point taken, that kind of makes sense if you are crazy and disable probes15:17
portdirectitxaka: sometimes you need to as the world is full of crazy things15:17
portdirecteg recently we had a case where a site was using the fluent logger, which is blocking15:18
itxakaok then its settled and I would die a little bit everytime that I use that function15:18
portdirectfluentd was down15:18
jsuchomethat change (introducing this _kubernetes_probes.tpl) is quite new, if it is that needed, how did people disable probes before?15:18
portdirectwe needed to disable the probes to stop the rot spreading15:18
portdirectnow this is a bad edge case15:18
itxakaso the probe helper came from there? lmao15:19
portdirectbut the sort of stuff that we can cope with through having a common well developed function15:19
itxakastill a good thing to have stuff that comes from real issues15:19
portdirectno - just an example of why having every chart differnt means we loose the benefit of having a common function15:19
itxaka+1 for me to move on from this issue as I consider it settled15:19
itxakaunless jsuchome has something to say about it?15:19
portdirectjsuchome: re your q - kubectl edit :screams:15:20
jsuchomeI had hopes to see a code that even I can understand15:20
jsuchomeah15:20
portdirecti think this convo raises a really good point though15:21
itxakaI thought you could not disable probes via kubectl edit :o15:21
portdirectitxaka: you can do anything with a big enough hammer15:21
portdirectyou can though for all but statefulsets15:22
portdirect`no more 300 chars functions that you need to look up and decipher from htk to understand what they do`15:22
portdirect^ this is so true15:22
itxakayeah tpl is terribleeeee15:22
portdirectand somthing we need to solve for15:22
portdirectI'll put it on the agenda for next week - and lets see if we can think of better ways in the mean time?15:22
itxaka+115:23
jsuchomeI would just think that if disabling is the main issue, there might be a chance to make it possible with simpler method ... but I do not have specific idea now, so let's move on15:23
portdirect#topic Time to make zuul RELEASE-OS jobs voting?15:24
*** openstack changes topic to "Time to make zuul RELEASE-OS jobs voting? (Meeting topic: openstack-helm)"15:24
portdirectitxaka: your up :D15:24
itxakame again?15:24
itxakayeah what it says, not much to expand15:24
portdirecti think its time15:25
itxakashould we already move those into voting? Its been a long time with no progress there15:25
itxakasome may be broken and we are just ignoring them15:25
itxakaand we are already running them, what a waste of good resources!15:25
portdirectyeah - i think we should get a ps in today to flip them, unless anyone objects15:25
itxakayay |o/15:26
portdirectok - lets do it itxaka and jsuchome :D15:26
itxakayay yay \o/15:26
itxakawhos sending the ps?15:26
portdirectim excited - finally get suse voting, and a less historic openstack release15:26
portdirectitxaka: you ok with pusing it?15:27
itxakayup!15:27
portdirector jsuchome - then we can both get it in15:27
itxakasuse, ubuntu or all of them? Or several separated patches?15:27
jsuchomesorry I wasn't following, I could (so itxaka can use his +2), but I'll leave the honors of creating PS to him15:28
*** k_mouza has joined #openstack-meeting-415:28
portdirectroger - thanks15:28
portdirectok - lets move on15:28
portdirect#topic Was there a plan to unite various (bash) deployment scripts?15:28
*** openstack changes topic to "Was there a plan to unite various (bash) deployment scripts? (Meeting topic: openstack-helm)"15:28
jsuchome(I think if they are stable anough, let's do them all in one patch)15:28
portdirectjsuchome: agreed15:29
portdirectalso i think this is you?15:29
jsuchomeyes: so, I remember that some time ago we voluntered to work on those deployment scripts15:29
* itxaka runs15:29
jsuchomebut then I think someone had an AI to lay out some plans first15:29
jsuchomeso I was wondering, if there's a specific plan, or if I could just start digging and propose something...15:30
portdirectjsuchome: i put a few thoughts in the etherpad15:30
jsuchomeyeah, and also evrardjp said he used to have some ideas about this some time ago, I'm not sure if it went in the same direction15:30
portdirectbut i think its high time we pruned a lot of the old scripts that are gathering dust15:31
evrardjpyeah let's clean everything !15:31
itxaka+115:31
portdirectjsuchome: it went in a very similar direction to what evrardjp was proposing, just in bash rather than ansible15:31
jsuchomeso basically the plan is to take developer + multinode scripts and combine them with component ones?15:31
portdirectthough he can keep me honest there15:31
jsuchomeand he's alive! (evrardjp)15:31
evrardjp(in another meeting)15:32
*** belmoreira has quit IRC15:32
evrardjp(sorry)15:32
portdirectjsuchome: that would seem like the best place to start15:32
jsuchomeok then, I'll try to start there15:32
itxakaeverything merged *and* in ansible? Is this a dream?15:32
portdirectw00t - that would be great jsuchome15:32
portdirectitxaka: steady now15:33
jsuchomeI did not promise ansible itxaka!15:33
itxaka:(15:33
*** diablo_rojo has joined #openstack-meeting-415:33
itxakaI read ansible somewhere and got excited15:33
* jsuchome whispers there's not enough chef in this ecosystem...15:33
portdirecti think we should be looking to add over-rides to allow the `component` scripts to forfil the same functions as the developer and multinode ones do today15:33
* portdirect would like some puppet15:34
itxakaomg stop it15:34
itxakaportdirect: like with the features I guess?15:35
itxakaso multinode would be a feature?15:35
itxaka"feature" in the sense of feature gates and overrides of course15:35
portdirectitxaka: i think so15:36
itxaka+115:36
portdirectunless we want multinode to be the default, and 'singlenode' to be the (anti) feature?15:36
itxakado we expect other that POCs and Developers to deploy single node deployments?15:37
itxakaIMO should test the most common scenario15:37
portdirecti think to be honest - single node is the most common senario15:37
itxakathen single node as the default should be15:37
portdirectso perhaps leave it that way to simplify people starting out?15:38
jsuchomehm, most common senario for playing around, but production?15:38
portdirectoh my - so production is hard - in that we (putting work hat on) typically run >20 replicas of apis etc15:39
portdirectand other config params that would rule out anything other than large(ish) deployments15:39
jsuchomeyou mean you don't even use those scripts?15:39
itxakawell mostly the difference between 2 and 20 replicas is not much rigth?15:40
portdirectnot for production no15:40
itxakais most about the single pod vs multipod (no matter the number) deployments15:40
portdirectfor that id reccomend a datacenter lifecycle tool like (wait for it)15:40
portdirect...15:40
portdirectairship15:40
itxakanooooo15:40
jsuchomeand here we are15:40
jsuchomeok, so it's settled, multinode is the feature that needs to be turned on15:41
portdirectsounds good15:41
portdirect#topic Release notes? Abandoned? Enforced? Ignored?15:42
*** openstack changes topic to "Release notes? Abandoned? Enforced? Ignored? (Meeting topic: openstack-helm)"15:42
itxakaah I just moved that below because I dont want us to run out of time for roman_g topic15:42
portdirectah - ok, lets come back to this15:42
portdirect2 sec15:42
portdirect#topic Zuul Promote jobs are failed, logs are hidden15:43
*** openstack changes topic to "Zuul Promote jobs are failed, logs are hidden (Meeting topic: openstack-helm)"15:43
portdirectroman_g: floor is yours15:43
roman_gJust wanted to say that jobs failed15:44
roman_gAFAIK we don't have notification for post merge jobs15:44
roman_gI'm guessing if this is normal, or is it being taken care of already, or I can request logs and investigate15:45
roman_g?15:45
roman_gPromote jobs15:45
roman_ghttps://review.opendev.org/#/c/672678/15:45
portdirectevrardjp: is our resident sme in this area15:46
itxakayou it would be nice to be able to see those logs while filtering any secrets in there otherwise its a black box15:46
roman_gThat's hist patch, btw :)15:46
roman_g*his15:46
itxakaevrardjp is currently on a meeting so he wont be available unfortunately :/15:47
portdirectwhen hes escaped, you we ok to discuss this in #openstack-helm?15:47
itxaka+115:48
portdirectok - thanks for bringing this up roman_g and also digging into it15:49
portdirectlets take it to the channel when evrardjp is around15:49
portdirect#topic Release notes? Abandoned? Enforced? Ignored?15:49
*** openstack changes topic to "Release notes? Abandoned? Enforced? Ignored? (Meeting topic: openstack-helm)"15:49
roman_gitxaka: I would be gone home in 20 min. or so. Couldn't participate, but highlight me if needed, I will read tomorrow.15:49
itxakaAs it says, we dont have much movement in release notes so I wonder what should we do. Do we want to start -1 ps with no release notes for important stuff or we just go ahead and fully ignore them?15:50
itxakaroman_g will do, thanks!15:50
*** bobmel has joined #openstack-meeting-415:51
lamtI was thinking about reno the other day as there is a lot of network policies work inflight - but since we don't have any "releases" per se, it feels like additional administrative work.15:51
jsuchomethat seems like a good idea, but what is "important stuff" ?15:51
roman_gwhat product manager decides to be important15:52
portdirecti'm inclined to agree with lamt15:52
portdirectin that at the moment it generates admin overhead, that im not sure pays off15:52
portdirectuntill we can at least solve the problem of `what is "important stuff"`15:52
itxakaagreed15:53
portdirectso im inclined to say ignore for now?15:53
lamt++15:53
itxaka+115:54
portdirect#topic the long lost, and partly forgotten openstack-objects chart15:55
*** openstack changes topic to "the long lost, and partly forgotten openstack-objects chart (Meeting topic: openstack-helm)"15:55
itxakayay15:55
itxakaso there may be some work coming for that15:55
itxakaas there has been some recent interest on it15:55
portdirectawesome!15:55
itxakaso its not fully forgotten but pretty down in the backlog15:55
portdirectyes - it would tie in nicely to the gate pruning as well15:55
itxakathat point was just a informative note15:55
portdirectok - thanks dude15:56
portdirect#topic Helm3 plans15:56
*** openstack changes topic to "Helm3 plans (Meeting topic: openstack-helm)"15:56
itxakame again15:56
portdirectwe wont have time for all of this today15:56
portdirectbut in summary - we dont have any direct plans at this time15:56
portdirectas the charts will all work with helm315:56
jsuchomehave you seen that video? Is it worth watching?15:56
itxakaindeed we dont, some guy just filled up the topic etherpad15:57
portdirectitxaka: and thats why we love you15:57
itxakawhat about the library charts? any plan to move htk into that?15:57
itxakamostly interested in that15:57
portdirectitxaka: we should, as htk was very much one of the drivers behind that feature ;D15:57
itxakaoooh15:58
evrardjplibrary charts I guess15:58
portdirectit would also be a good time to address if possible some of the concerns raised at the start of the meeting15:58
evrardjp(catching up)15:58
portdirectin that when we move to a library chart, we should also clean up htk15:58
itxakamoving to lua?15:59
portdirectrather than take it all with us15:59
portdirectthats a possible outcome15:59
portdirecti think it would be good to have howell involved in these convos to15:59
evrardjpportdirect: that sounds fair, but how will you make sure you don't break customers, as you don't have stable versioning yet ?15:59
itxaka٩( ๑╹ ꇴ╹)۶15:59
portdirectevrardjp: with great care ;D15:59
evrardjpand a lot of shas!15:59
evrardjp:)16:00
portdirectlol16:00
portdirectwe should def start next week on this topic16:00
portdirectthats all the time we have today folks - thanks so much for coming16:00
portdirect#endmeeting16:00
itxaka(ʘ‿ʘ)╯16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Sep 24 16:00:33 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-09-24-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-09-24-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-09-24-15.00.log.html16:00
stevthedevHave a good week everybody16:01
evrardjpI read week-end16:01
stevthedevAgh16:01
stevthedevIf only16:01
evrardjpexactly16:01
evrardjp:)16:01
*** bh526r has quit IRC16:03
*** macz has joined #openstack-meeting-416:04
*** bobmel has quit IRC16:10
*** salmankhan has quit IRC16:40
*** k_mouza has quit IRC16:46
*** e0ne has quit IRC16:57
*** macz has quit IRC17:04
*** ralonsoh has quit IRC17:42
*** e0ne has joined #openstack-meeting-417:47
*** igordc has joined #openstack-meeting-417:48
*** psachin has quit IRC17:59
*** e0ne has quit IRC18:09
*** belmoreira has joined #openstack-meeting-418:17
*** e0ne has joined #openstack-meeting-418:32
*** e0ne has quit IRC18:33
*** e0ne has joined #openstack-meeting-418:54
*** jsuchome has quit IRC18:59
*** sgrasley has quit IRC19:15
*** gagehugo has left #openstack-meeting-419:44
*** e0ne has quit IRC19:59
*** belmoreira has quit IRC20:27
*** e0ne has joined #openstack-meeting-420:38
*** pmatulis1 is now known as pmatulis21:47
*** slaweq has quit IRC22:00
*** e0ne has quit IRC22:04
*** dulek has quit IRC22:04
*** k_mouza has joined #openstack-meeting-423:45
*** diablo_rojo has quit IRC23:47

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