Tuesday, 2019-06-04

*** yamamoto has joined #openstack-meeting-400:02
*** markvoelker has quit IRC00:24
*** Liang__ has joined #openstack-meeting-400:27
*** Liang__ is now known as LiangFang00:30
*** Adri2000 has quit IRC00:40
*** Adri2000 has joined #openstack-meeting-400:45
*** bobh has joined #openstack-meeting-400:58
*** yamamoto has quit IRC01:03
*** bobmel has joined #openstack-meeting-401:05
*** bobmel has quit IRC01:09
*** bobh has quit IRC01:54
*** hyunsikyang has quit IRC02:16
*** hongbin has joined #openstack-meeting-402:17
*** yamahata has quit IRC02:24
*** yamamoto has joined #openstack-meeting-402:51
*** happyhemant has quit IRC03:20
*** igordc has quit IRC03:39
*** LiangFang has quit IRC03:59
*** Liang__ has joined #openstack-meeting-404:01
*** yamahata has joined #openstack-meeting-404:02
*** gcheresh has joined #openstack-meeting-404:03
*** igordc has joined #openstack-meeting-404:06
*** bobmel has joined #openstack-meeting-404:06
*** bobmel has quit IRC04:11
*** hongbin has quit IRC04:17
*** gcheresh has quit IRC04:28
*** bobmel has joined #openstack-meeting-404:47
*** bobmel has quit IRC04:51
*** pcaruana has joined #openstack-meeting-405:12
*** radeks has joined #openstack-meeting-405:18
*** pcaruana has quit IRC05:23
*** bobmel has joined #openstack-meeting-405:27
*** pcaruana has joined #openstack-meeting-405:28
*** bobmel has quit IRC05:31
*** e0ne has joined #openstack-meeting-405:43
*** igordc has quit IRC05:51
*** Liang__ has quit IRC05:53
*** Liang__ has joined #openstack-meeting-405:54
*** bobmel has joined #openstack-meeting-405:58
*** bobmel has quit IRC06:02
*** lpetrut has joined #openstack-meeting-406:10
*** slaweq has joined #openstack-meeting-406:13
*** bobmel has joined #openstack-meeting-406:30
*** yamamoto has quit IRC06:41
*** evrardjp_ is now known as evrardjp06:43
*** gcheresh has joined #openstack-meeting-406:44
*** yamamoto has joined #openstack-meeting-406:59
*** e0ne has quit IRC07:09
*** slaweq has quit IRC07:16
*** yamamoto has quit IRC07:20
*** yamamoto has joined #openstack-meeting-407:21
*** yamamoto has quit IRC07:30
*** markvoelker has joined #openstack-meeting-407:32
*** yamamoto has joined #openstack-meeting-407:33
*** bobmel has quit IRC07:34
*** yamamoto has quit IRC07:39
*** slaweq has joined #openstack-meeting-407:40
*** bobmel has joined #openstack-meeting-407:42
*** yamamoto has joined #openstack-meeting-407:42
*** markvoelker has quit IRC08:05
*** k_mouza has joined #openstack-meeting-408:13
*** e0ne has joined #openstack-meeting-408:32
*** k_mouza has quit IRC08:36
*** k_mouza has joined #openstack-meeting-408:37
*** janki has joined #openstack-meeting-408:39
*** spsurya has joined #openstack-meeting-408:51
*** Liang__ has quit IRC09:03
*** Liang__ has joined #openstack-meeting-409:05
*** mugsie_ is now known as mugsie09:52
*** k_mouza has quit IRC09:53
*** markvoelker has joined #openstack-meeting-410:02
*** Liang__ has quit IRC10:03
*** k_mouza has joined #openstack-meeting-410:05
*** happyhemant has joined #openstack-meeting-410:13
*** slaweq has quit IRC10:30
*** markvoelker has quit IRC10:36
*** yamamoto has quit IRC10:36
*** yamamoto has joined #openstack-meeting-410:37
*** yamamoto has quit IRC10:38
*** slaweq has joined #openstack-meeting-411:01
*** yamamoto has joined #openstack-meeting-411:21
*** janki has quit IRC11:30
*** markvoelker has joined #openstack-meeting-411:33
*** yamahata has quit IRC11:56
*** yamamoto has quit IRC11:58
*** yamamoto has joined #openstack-meeting-412:00
*** markvoelker has quit IRC12:05
*** seajay has joined #openstack-meeting-412:08
*** yamamoto has quit IRC12:13
*** mugsie is now known as mugsie_12:18
*** mugsie_ is now known as mugsie12:18
*** spsurya has quit IRC12:40
*** yamamoto has joined #openstack-meeting-412:51
*** bh526r has joined #openstack-meeting-412:55
*** yamamoto has quit IRC12:59
*** yamamoto has joined #openstack-meeting-412:59
*** Luzi has joined #openstack-meeting-413:00
*** howell has joined #openstack-meeting-413:07
*** rihbb has joined #openstack-meeting-413:08
*** Luzi has quit IRC13:13
*** rihbb has quit IRC13:17
*** diablo_rojo has joined #openstack-meeting-413:18
*** diablo_rojo has quit IRC13:22
*** Liang__ has joined #openstack-meeting-413:23
*** diablo_rojo has joined #openstack-meeting-413:23
*** lpetrut has quit IRC13:43
*** liuyulong has joined #openstack-meeting-413:53
*** gagehugo has joined #openstack-meeting-414:32
*** yamamoto has quit IRC14:48
*** yamamoto has joined #openstack-meeting-414:53
*** yamamoto has quit IRC14:53
*** yamamoto has joined #openstack-meeting-414:54
*** yamamoto has quit IRC14:55
*** yamamoto has joined #openstack-meeting-414:55
*** yamamoto has quit IRC14:55
*** jsuchome has joined #openstack-meeting-414:56
*** lpetrut has joined #openstack-meeting-414:57
*** mattmceuen has joined #openstack-meeting-414:57
*** Liang__ has quit IRC14:58
*** cheng1__ has joined #openstack-meeting-415:00
mattmceuen#startmeeting openstack-helm15:00
openstackMeeting started Tue Jun  4 15:00:30 2019 UTC and is due to finish in 60 minutes.  The chair is mattmceuen. 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
mattmceuen#topic Rollcall15:00
*** openstack changes topic to "Rollcall (Meeting topic: openstack-helm)"15:00
mattmceuenGM / GE all!15:00
mattmceuenLet's give it a few minutes for folks to join15:01
srwilkerso/15:01
* srwilkers scurries off for caffeine15:01
jsuchomeo/15:01
gagehugoo/15:01
*** mbuil has joined #openstack-meeting-415:01
* mattmceuen virtual coffee for jayahn and srwilkers15:01
itxaka\o15:01
georgkhello15:01
itxakaon extra over here pls mattmceuen15:02
mattmceuenThanks for joining all15:02
itxakas/on/one/15:02
howello/15:02
* mattmceuen coffee -> itxaka posthaste15:02
evrardjpo/15:02
*** gcheresh has quit IRC15:02
mattmceuenOur fearless leader is tied up, so I'll try to cover!15:02
mattmceuenHowever, I don't have an agenda prepped, so we'll be doing this a bit ad hoc15:03
mattmceuenhttps://etherpad.openstack.org/p/openstack-helm-meeting-2019-06-0415:03
mattmceuenplease add any topics you'd like to discuss into there15:03
*** rihbb has joined #openstack-meeting-415:04
*** rihbb has left #openstack-meeting-415:04
jayahno/15:05
* jayahn is half sleeping 15:05
mattmceuen#topic Feedback on hugepage support in HTK resource handling15:05
*** openstack changes topic to "Feedback on hugepage support in HTK resource handling (Meeting topic: openstack-helm)"15:05
mattmceuenhttps://review.opendev.org/#/c/662603/15:06
mattmceuenFeedback welcome ^15:06
mattmceuengeorgk anything else to discuss here or just offline in the patchset?15:06
georgkboth is fine15:06
mattmceuencool - to parrot you :) in the agenda notes:      Question: adding checks for hugepage resources or removing checks, as in https://review.opendev.org/#/c/662603/115:07
mattmceuencan you give us a quick overview georgk15:07
georgkI'd like to add hugepage resoruce handling to HTK15:07
georgkand there is a debate if the corresponding resource snippet should check input or not15:08
itxakawhat are the cons of extra checking?15:08
itxakacomplexity in the snippet?15:08
georgkthe check sanitize the input. in case of a type, for instance hugepages-2M instead of hugepages-2Mi, this would be removed15:09
georgkfrom the resource definition.15:10
georgkas a result, the pod gets spawned without hugepage config, resulting in an application error15:10
georgkif the check was not there, K8s would have not spawned the pod due to the typo15:10
georgkcatching the problem earlier15:10
georgkfunny, thing, in this case fewer checks chatch the problem earlier.15:11
evrardjpfor me this raises a bigger concern in my head15:11
evrardjpwhere is the limitation of what we implement in HTK15:11
evrardjpfor me the goal of HTK is to provide convenience, and for example, in this case, I would not use htk, but pass the data verbatim to k8s15:12
evrardjphtk can provide validation15:12
evrardjpso where is the boundary?15:12
evrardjpI like the fact we provide validation in htk, I find it less useful if we just retemplate yaml15:12
evrardjpdid I generalize the concern correctly georgk?15:13
mbuilactually, when using hugepages-2M, k8s does not complain saying "I don't understand this resource". I don't remember the exact error but it was something like "I can't get hugepages-2M" which made things very confusing because there were enough free hugepages-2M15:13
srwilkershelm-toolkits meant to give us a consistence interface with interacting with charts -- in this case specifically, it gives us a clean interface to inject the yaml instead of having to modify the chart templates directly each time we want to modify these things15:13
georgkevrardjp: yes, thanks15:13
evrardjpsrwilkers: oh so in this case it's not about validation but DRY approach15:14
georgksrwilkers: I do this benefit15:14
mattmceuenFor cases where we render an override chunk directly into a k8s manifest 1:1, I would lean toward not getting in the business of validating k8s schema for k8s15:14
evrardjpdid I get that correctly?15:14
evrardjpmattmceuen: in that case the function doesn't need to exist in htk15:15
evrardjpat all15:15
*** yamamoto has joined #openstack-meeting-415:15
*** yamamoto has quit IRC15:15
*** yamamoto has joined #openstack-meeting-415:15
georgkevrardjp: the function does a bit more as it also checks if resource handling is enabled or not15:16
evrardjpbecause consistency is naturally implied by convention (we respect k8s data structure)15:16
evrardjpgeorgk: so I guess there are multiple problems at hand here.15:16
evrardjplet's not go into the generalization to make the problem simpler to apprehend. Sorry if I went for a different path :)15:16
*** sgrasley has joined #openstack-meeting-415:17
georgkso, I wanted to tap into the experience of the folks here to decide which way to go best.15:18
georgkfeel free to take some more time to look at the patchset15:18
mattmceuenFor the updated version of of _kubernetes_resources, I think I agree evrardjp -- it's mostly one like of "toYaml" and 50 lines of boilerplate.  Maybe better to put "toYaml" directly in the calling manifest in that case.  However, if we do want to enforce a schema (as opposed to toYaml) then I see the value of retaining the snippet for the sake of driving consistency across charts.15:18
mattmceuenpros/cons both ways15:19
evrardjpmattmceuen: agreed there15:19
mattmceuenSounds good georgk -- I think we all understand the problemspace well enough to mull over it now :)15:19
mattmceuenthanks for bringing it up15:19
evrardjpthen we "just" have to decide which function deserves validation15:19
evrardjpwhich input*15:20
mattmceuenyeah15:20
cheng1__if we enhance the htk function, which case do we handle15:20
*** yamamoto has quit IRC15:20
evrardjpif you want validation (so deep knowledge of the app) and what you are doing is across multiple charts, then htk need to be adapted for enforcing convenience15:21
cheng1__limit user input?15:21
evrardjpmattmceuen: did I summarize this well?15:21
mattmceuentake a look at the final comment in that patchset as well cheng1__ -- it has a pretty good example15:21
evrardjpenforcing conformity*15:21
mattmceuenthe good thing about a "toYaml" approach is that it's very flexible, so you can add in new inputs as the native k8s api object is enhanced over time for example.  The bad thing is that is's very flexible, so you can get your input wrong, and sometimes k8s can give you cryptic error messages back :)15:22
mattmceuenthere's a place for both15:23
georgkso, given that there will likely be nasty cornercases which cannot be handled well, I lean towards the toYaml approach15:23
srwilkersin this case specifically15:23
srwilkersactually, nevermind me15:24
mattmceuenSo then the question is15:24
itxakadamn you had me hanging there for one full minute srwilkers15:25
itxakanow I want to know what you were gonna said :/15:25
srwilkersitxaka: :)15:25
evrardjpit's not the first time he does that in a meeting :p15:25
mattmceuenIf we just want toYaml, and we think "direct toyaml is better than wrapped toyaml" --  is it still a good idea to make the htk function a pass-through for the sake of consumers of the function15:25
mattmceuenthat would give some time to update osh proper, airship, anything else before yanking the function out15:26
evrardjpI believe if the function is just reoutputting same yaml, then the function needs to be deprecated15:26
mattmceuendeprecated:  agree.  time-delayed removal15:26
evrardjp(same or similar, with indention)15:26
evrardjpindentation*15:27
mattmceuenAny objections?15:27
evrardjpindentation shouldn't be a valid reason to keep tech debt15:27
itxakaagreed ^^15:27
jayahnagreed..15:27
mattmceuenboom.  look at us, we decided something, portdirect will be so happy15:27
mattmceuenunless he disagrees, in which case too bad :p15:27
georgk:-)15:27
mattmceuenOk, moving on:15:28
georgkawesome15:28
georgkthanks15:28
mattmceuen#topic Technical debt15:28
*** openstack changes topic to "Technical debt (Meeting topic: openstack-helm)"15:28
itxakathats me!15:28
mattmceuentake it away!15:28
evrardjpwe just talked about one, more tech debt reduction?15:28
evrardjpawesome!15:28
itxakaso it was mentioned last week on the channel that some of the comments and views on some patches were ignored and there was a feeling that there is not enough done to reduce tech debt15:28
*** qwebirc65085 has joined #openstack-meeting-415:28
itxakaso Im wondering, how can we tackle that? how can we start reducing tech debt for a nicer maintenance of osh?15:29
evrardjpbest code to maintain is no code :)15:29
jayahni am not following15:29
evrardjpI was told rm -rf is not a solution though15:29
*** lpetrut has quit IRC15:29
evrardjpdo you have an example itxaka?15:29
mattmceuenthat's a broad topic itxaka!  Can you point us to an example or an embryonic thought or something15:29
itxakano ideas here other than having "reduce tech debt" day once per month/15 days15:29
jsuchome(how is rm -rf not the solution?)15:30
mattmceuenrm -rf everything except the tests, and work your way back from there jsuchome15:30
evrardjpitxaka: how you want to have a periodic checking of what we all achieved to reduce tech debt?15:30
itxakaevrardjp: it was you the one to mention it, so hopefully you will have an example ;)15:30
evrardjpdamn I can't remember now15:30
itxakaIm just a vessel of thougths and feeelings15:30
mattmceuenlol15:30
evrardjpoh yes!15:30
evrardjpI remember15:30
mattmceuenmy feelings agree with your feelings15:30
evrardjpcool ... so!15:30
evrardjpyes we are adding new images in osh-images, with no explanation whatsoever how they gonna fit in the OSH vision (for example, how they will be used in helm charts)15:31
evrardjpif future me wants to rm -rf all the things, he will check for the reason why image x exists in the first place15:31
jsuchomeyep, let's test drive it all, if only someone would give us few years of uninterrupted development...15:31
jsuchome(sorry JP I did not want to interrupt your thoughts)15:32
*** e0ne has quit IRC15:32
evrardjphaha15:32
evrardjpmy point is that we all need to be aware that the code we are adding has downsides, and we should drive to periodically reduce old remnants15:33
srwilkerswith regards to images, i can speak to a few that i've added/proposed15:33
itxakahence "reduce tech debt" day :P15:34
evrardjpfor example, we discussed at the PTG to remove the newton building of images. This was a good idea.15:34
evrardjpI just want to make sure we are not forgetting things15:34
evrardjpall together15:34
evrardjpsrwilkers: it's not targetted against a single individual15:34
evrardjpit's we need to take ownership _together_ ;)15:34
srwilkerswell right, but i feel the context helps that collective ownership15:34
georgkevrardjp: you have a good point here and I see this specifically be true in case of the dpdk images15:35
georgkblaming myself here15:35
evrardjpawesome, I am all ears srwilkers :D I love a good narrative15:35
mattmceuenIs you guys' feeling that we're adding things we shouldn't (unneeded tech debt) or that we're not sufficiently explaining/documenting/discussing the widgets that are added15:35
evrardjpmattmceuen: I guess without the latter we can't evaluate the former15:36
jayahnlatter15:36
evrardjpwe can only trust your insights in that case.15:36
mattmceuenone easy thing that we've done inconsistently / ad-hoc -- maybe every time we add an X we then do a quick show-and-tell in this team meeting; where X is something we can define that is bigger than a line of code15:37
evrardjpthe former might have happened too, but let's not go into the specifics right now I would say15:37
evrardjpmattmceuen: alternatively, provide a release note ?15:37
itxakarelease notes +115:37
itxakaI would forget stuff otherwise for sure15:37
evrardjplet's have a "what's in it for the community"15:37
mattmceuenagree 100%, only caveat is that we currently have a team meeting and we currently don't have a release notes :)15:38
evrardjprelease notes would be the target reading for all deployers15:38
evrardjpdon't we?15:38
evrardjpI think I wrote things for that?15:38
jayahnwe have15:38
mattmceuenoh I may have missed it15:38
itxakaI guess we can agree that for any change that is relatively "costly" a release note should be provided so everyone is awere of how, why, when15:38
mattmceuenmy bad15:38
jayahnnot forced or recommend in the process yet15:38
evrardjpproves I need to communicate better :D15:38
* mattmceuen is the worst at communicating :D15:38
itxakashould have provided a release note for that evrardjp ;)15:39
evrardjpI think it's two things itxaka: commit messages for the WHY is good, renos are a plus for deployers15:39
mattmceuenevrardjp you probably just need to add a release note letting folks know there are release notes15:39
evrardjpI probably did, but we don't release yet, so we don't publish them yet :p15:39
*** yamahata has joined #openstack-meeting-415:39
evrardjpdifferent topic there15:39
mattmceuenso should we gently start encouraging folks to add release notes, via patchset feedback, in preparation for it becoming part of the formal process?15:39
*** spsurya has joined #openstack-meeting-415:40
itxaka+115:40
jayahnbut, then where we can check all the release notes? we don't have releases yet.15:40
evrardjpmattmceuen: I think that would be one good action item... If commit messages explain well the WHY things are done, and release notes are provided when a user facing feature appears, then we are good15:40
jayahnah.. evrardjp, mentioned15:40
mattmceuen++ evrardjp15:40
evrardjpjayahn: in the meantime that would be in-tree15:41
*** arunkant has joined #openstack-meeting-415:41
evrardjpbut all the deployer facing features would be there, so you know you have to read them :)15:41
mattmceuensounds like a plan to me.  Let's all please keep an eye out for good use cases for release notes and steer the broader team toward creating them in PS, as well as explanatory commit messages15:42
mattmceuenGood to move on itxaka & all?15:43
evrardjplgtm15:43
itxakayup yup!15:43
mattmceuencool15:43
jayahn+115:43
mattmceuen#topic When meeting time poll will happen?15:43
*** openstack changes topic to "When meeting time poll will happen? (Meeting topic: openstack-helm)"15:43
mattmceuenI'm going to go out on a limb and guess this is yours jayahn?15:43
jayahni wrote in etherpad15:43
mattmceuenThe easy thing for me would be to punt this one to portdirect :p15:43
mattmceuenhowever I made the same commitment on the airship side15:44
jayahni have been talking about this since ptg. but, honestly, i feel like i am the only one who cares about this15:44
mattmceuen#action mattmceuen to sit down with portdirect to do polls this week15:44
mattmceuensorry for the delay jayahn, been real busy but that's not a good excuse15:44
*** bnemec has quit IRC15:44
itxakadidnt we brougth it up on the last meeting and ti was agreed that a mail was gonna be sent?15:45
* itxaka searches for last etherpad agenda...15:45
jayahnyeap.15:45
srwilkersi raised it to portdirect after last meeting, but it's not happened yet15:45
evrardjpjayahn: you are not the only one15:45
evrardjpsorry if you feel that way15:45
*** bnemec has joined #openstack-meeting-415:46
mattmceuenwell the other thing is... many folks who would care probably aren't here15:46
jayahnmy additional comment on etherpad is just asking if simple poll is right way. but it is just flow of my thought15:46
*** iyamahat has joined #openstack-meeting-415:46
itxakaindeed, that sucks, sorry for the delay jayahn15:46
mattmceuenIt'll happen by next week15:46
mattmceuenOk - if there isn't anything else on this one we'll move on15:47
evrardjpmattmceuen is rolling for initiative.... !15:47
itxakawell, I guess the poll can also help in gauging the interest from other parties in participating and if that interest is big enough something should be discussed on how to approach that15:47
mattmceuen#topic I have an entire hour with portdirect on Friday on our outlook calendars for this >:-)15:47
itxakathis is in regards of your comments in the etherpad jayahn ^^15:47
*** openstack changes topic to "I have an entire hour with portdirect on Friday on our outlook calendars for this >:-) (Meeting topic: openstack-helm)"15:47
mattmceuenlol I didn't mean to make that a topic15:47
itxakaI like this topic15:48
jayahnitxaka: yeap. thanks15:48
mattmceuenthis will make for the best meeting notes15:48
mattmceuenportdirect will never let me lead this meeting again15:48
itxakawhats the outcome of this topic :P15:48
* mattmceuen mission accomplished15:48
mattmceuen#topic Review Requests15:48
*** openstack changes topic to "Review Requests (Meeting topic: openstack-helm)"15:48
mattmceuen    https://review.opendev.org/#/c/653428/ -> Add tempest job and gate to zuul as voting15:48
mattmceuen    https://review.opendev.org/#/c/662992/ -> htk: provide default domain env and secrets15:48
mattmceuen    Follow up: https://review.opendev.org/#/c/662993/ -> keystone: default domain fix15:48
mattmceuen    https://review.opendev.org/#/c/662988/ -> tempest: several fixes to tempest config15:48
mattmceuen    https://review.opendev.org/#/c/662775/ -> Update apparmor job after fluent-logging split (Fixes apparmor job!)15:48
mattmceuen    https://review.opendev.org/#/c/622573/7 -> TF plugin review15:48
*** hamzy_ has quit IRC15:48
qwebirc65085Hi all15:49
evrardjpI have an extra topic15:49
mattmceuenGood mix of interesting patchsets being asked for review - thanks for adding them, and let's please put them on our to do lists15:49
qwebirc65085This is prabhu15:49
mattmceuenhey prabhu15:49
jayahnhi prabhu15:49
qwebirc65085Just reminder to review TF plugin changes15:49
* mattmceuen evrardjp - noted15:49
qwebirc65085I have added 2 links on story board, one for plugin changes and the other one for TF bringup with openstack15:50
evrardjpprabhu you are at the right time :)15:50
mattmceuenThanks for the reminder prabhu15:50
qwebirc65085any questions on the writeup, please let me know15:50
mattmceuenis the patchset you linked for the plugin change, and bringing it up with openstack is still TODO?15:51
qwebirc65085no.  latest patchset is working fine with TF15:51
mattmceuenok great15:51
mattmceuenvery cool15:52
qwebirc65085i have fixed some stuff seen during my unit testing.15:52
itxakaqwebirc65085: regarding the doc you sent, maybe you should host it somewhere and link it from the story? (Maybe its already linked, havent had time to look at the stories)15:52
srwilkerswe still need to see it exercised as a job that runs in openstack-infra to be able to properly validate it and provide valuable review15:52
qwebirc65085i didn't find a place to upload complete doc15:52
qwebirc65085that's why i put it as story15:52
mattmceuenfor the story, you can link back to them via the `Story:` and `Task:` tags in the commit message IIRC15:53
itxakaummm, no attachments in storyboard, that sucks :(15:53
qwebirc65085@srwilkers: ok15:53
mattmceuenYeah, I see a lot of scripts in your PS to run TF -- hopefully it'll be a straightforward thing to just add (one or more) gates to run the scripts, similar to what we have now15:54
mattmceuenok -- evrardjp you had an additional topic!15:54
evrardjpyes15:54
evrardjpso...15:54
evrardjpopenstack-helm-images promote pipeline is broken15:55
qwebirc65085@mattmceune: ok15:55
*** cheng1__ has quit IRC15:55
mattmceuen#topic openstack-helm-images promote pipeline is broken15:55
*** openstack changes topic to "openstack-helm-images promote pipeline is broken (Meeting topic: openstack-helm)"15:55
mattmceuenWhat do we need to do to fix it evrardjp?15:55
evrardjplet me rephrase that15:55
evrardjpthat sounds like a big deal, but it's not :)15:55
evrardjpso15:55
evrardjpin a recent patch, I added the fact to build/publish images with -date15:56
evrardjpthat doesn't work in promote pipeline right now.15:56
evrardjpI am working with infra to fix that15:56
evrardjpin the meantime we can:15:56
evrardjpremove the publication with dates, and do it again when infra is ready15:56
evrardjpI just wanted to raise awareness of the problem15:57
mattmceuengotcha - what is the issue w.r.t infra support for the dates?15:57
itxakado we have an estimation on when would infra be ready?15:57
evrardjpand I will submit a review to revert what I added, to make sure we can still publish images.15:57
itxakaif its too long then +1 to revert + postpone15:57
evrardjpso expect later a revert of the revert15:57
mattmceuensounds like a plan15:57
evrardjpmattmceuen: for technicalities, ansible_date_time is not part of the facts available on the pipeline15:58
mattmceuenahh15:58
evrardjpit involves zuul executors if you are interested.15:58
itxakaoooh15:58
mattmceueninteresting - I would like to dig more, my zuul integration knowledge is not strong15:59
evrardjptime is of the essence15:59
evrardjpon the channel maybe?15:59
mattmceuen+115:59
evrardjpthanks mattmceuen for the meeting!15:59
mattmceuenand with that we are out of time!15:59
itxakao/15:59
mattmceuenThanks for joining everyone16:00
evrardjpthanks everyone!16:00
mattmceuensee y'all in the channel16:00
itxakathanks y'all16:00
mattmceuen#endmeeting16:00
jayahnthanks16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
evrardjpincluding those who stay up late for us!16:00
openstackMeeting ended Tue Jun  4 16:00:08 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-06-04-15.00.html16:00
*** jsuchome has quit IRC16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-06-04-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-06-04-15.00.log.html16:00
*** gagehugo has left #openstack-meeting-416:03
*** qwebirc65085 has quit IRC16:08
*** lpetrut has joined #openstack-meeting-416:27
*** k_mouza_ has joined #openstack-meeting-416:52
*** lpetrut has quit IRC16:55
*** k_mouza has quit IRC16:56
*** k_mouza_ has quit IRC16:56
*** bh526r has quit IRC17:04
*** hamzy has joined #openstack-meeting-417:10
*** yamahata has quit IRC17:27
*** iyamahat has quit IRC17:27
*** k_mouza has joined #openstack-meeting-417:32
*** k_mouza has quit IRC17:36
*** iyamahat has joined #openstack-meeting-417:38
*** iyamahat_ has joined #openstack-meeting-417:45
*** yamamoto has joined #openstack-meeting-417:47
*** iyamahat has quit IRC17:49
*** gcheresh has joined #openstack-meeting-417:51
*** yamamoto has quit IRC17:52
*** yamahata has joined #openstack-meeting-417:58
*** diablo_rojo has quit IRC18:12
*** spsurya has quit IRC18:24
*** gcheresh has quit IRC18:30
*** diablo_rojo has joined #openstack-meeting-418:31
*** e0ne has joined #openstack-meeting-418:54
*** e0ne has quit IRC18:55
*** e0ne has joined #openstack-meeting-419:29
*** e0ne has quit IRC19:30
*** k_mouza has joined #openstack-meeting-419:33
*** k_mouza has quit IRC19:37
*** altlogbot_0 has joined #openstack-meeting-419:39
*** slaweq has quit IRC19:43
*** slaweq has joined #openstack-meeting-419:45
*** gcheresh has joined #openstack-meeting-419:59
*** dave-mccowan has joined #openstack-meeting-420:01
*** radeks_ has joined #openstack-meeting-420:06
*** radeks has quit IRC20:09
*** e0ne has joined #openstack-meeting-420:23
*** gcheresh has quit IRC20:25
*** dave-mccowan has quit IRC20:27
*** hamzy has quit IRC20:31
*** e0ne has quit IRC20:41
*** e0ne has joined #openstack-meeting-420:42
*** e0ne has quit IRC20:43
*** dklyle has quit IRC20:49
*** dklyle has joined #openstack-meeting-420:49
*** pcaruana has quit IRC21:07
*** howell has quit IRC21:41
*** yamamoto has joined #openstack-meeting-421:50
*** yamamoto has quit IRC21:55
*** slaweq has quit IRC22:07
*** slaweq has joined #openstack-meeting-422:11
*** seajay has quit IRC22:24
*** slaweq has quit IRC22:24
*** slaweq has joined #openstack-meeting-422:34
*** slaweq has quit IRC22:47
*** dave-mccowan has joined #openstack-meeting-422:57
*** radeks_ has quit IRC22:58
*** slaweq has joined #openstack-meeting-423:04
*** slaweq has quit IRC23:17
*** yamamoto has joined #openstack-meeting-423:41
*** slaweq has joined #openstack-meeting-423:50

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