Tuesday, 2018-07-17

openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: sql: add default_url column  https://review.openstack.org/58306600:16
mordredtristanC: I think the tenantname singleton service is the way ... and yes, please work on it if you have a chance00:24
mordredtristanC: I was also looking at https://angular.io/guide/router#lazy-loading-route-configuration - which isn't really quite right but has some ideas00:24
mordredtristanC: also https://angular.io/guide/router#child-routing-component00:24
mordredtristanC: which talks about how to have components that have their own roting00:25
mordredit still seems liek they take static input though00:25
tristanCmordred: yeah, i think we need to start having a context object to store a global state. singleton service seems like it would do the trick00:26
tristanCalright, then i'll work on that now00:27
mordredtristanC: I *think* if we can figure out the route stuff - we can put some context into the ActivatedRoute object (I saw something about that in the child-routing section)00:29
mordredtristanC: but yes- also - singleton service that handles this is ++00:29
tristanCi'll try to implement an ApiInfoService00:30
mordredtobiash: https://review.openstack.org/#/c/583062/ <-- you should be able to install a few less apk packages00:34
*** jiapei has joined #zuul02:10
*** rlandy has quit IRC02:28
*** _ari_ has quit IRC02:30
*** weshay has quit IRC02:30
*** _ari_ has joined #zuul02:31
*** pabelanger has quit IRC02:31
*** _ari_ has quit IRC02:31
*** _ari_ has joined #zuul02:31
*** pabelanger has joined #zuul02:32
*** weshay has joined #zuul02:32
*** sshnaidm|bbl has quit IRC03:49
*** sshnaidm|bbl has joined #zuul03:50
*** sshnaidm|bbl has quit IRC03:56
*** sshnaidm|bbl has joined #zuul03:57
jheskethianw: are you going to the openinfra day in sydney next month?05:13
*** nchakrab has joined #zuul05:27
*** nchakrab has quit IRC05:38
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: dashboard: make ZuulService load info api to manage paths  https://review.openstack.org/57941805:44
tristanCmordred: angular is very frustrating... 579418 took way longer than expected, i don't understand how component init works and had to use await to wait for the zuul service to get the info object05:45
*** quiquell|off is now known as quiquell05:45
tristanCit's surely not ideal, but it fixed the multi-tenant view bug and it should work as expected (e.g. white label shows status page, multi-tenant shows tenant-list if no tenant name is in the path)05:46
*** nchakrab has joined #zuul06:06
*** nchakrab has quit IRC06:31
tristanCcorvus: Shrews: it seems like we are hitting quota mis-calculation fixed by https://review.openstack.org/536930, any chance to get a nodepool release soon?06:35
*** nchakrab has joined #zuul06:37
tristanCis there a release frequency or schedule already discussed?06:37
*** chkumar|ruck has joined #zuul06:44
*** nchakrab has quit IRC07:09
ianwjhesketh: i was thinking of, are you?07:29
*** hashar has joined #zuul07:38
*** jluk has joined #zuul07:39
jlukHi there. Is there any way to manually enqueue a zuul buildset with a custom variable/param? I know there's nothing like this in the CLI client enqueue[-ref] command, but maybe in the protocol?07:47
*** sshnaidm|bbl is now known as sshnaidm|rover07:56
openstackgerritFabien Boucher proposed openstack-infra/zuul master: Add tenant yaml validation option to zuul client  https://review.openstack.org/57426508:00
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: dashboard: make ZuulService load info api to manage paths  https://review.openstack.org/57941808:02
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add selenium tests for the status page  https://review.openstack.org/57903908:02
*** electrofelix has joined #zuul08:10
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: sql: add default_url column  https://review.openstack.org/58306608:20
tobiashjluk: no, all variables parameters are defined in the job descriptions09:06
*** nchakrab has joined #zuul10:00
*** nchakrab_ has joined #zuul10:01
*** nchakrab has quit IRC10:04
jluktobiash: ok, expected that. So, let the hacking begin :)10:21
odyssey4meHi folks - is it possible for nodepool to make use of different private keys for authentication between providers? ie use private_key1 for provider 1, and private_key2 for provider 210:28
odyssey4meThere is 'key-pair' which is per label, but that only defines the name for the openstack driver when creating an instance... so it defines the target public key.10:30
odyssey4meI guess it'd be possible to split launcher configs so that the launcher for that region has a different default id_rsa.pub, but that's not so ideal.10:31
tobiashodyssey4me: nodepool only does a ssh-keyscan10:31
tobiashodyssey4me: it doesn't do logins10:32
odyssey4meah, ok - so it doesn't matter10:32
odyssey4meheh, makes sense10:32
tobiashodyssey4me: the zuul-executor knows the private key (and I think it's just one you can use atm)10:33
odyssey4metobiash: yeah, makes more sense thanks - we're only using nodepool, not zuul (we use jenkins instead)10:38
*** sambetts|afk is now known as sambetts10:59
*** rcarrill1 is now known as rcarrillocruz11:02
*** lennyb has quit IRC11:23
*** nchakrab_ has quit IRC12:07
*** rlandy has joined #zuul12:28
ShrewstristanC: there is no set release frequency, just whenever we need to release, we'll release12:31
*** elyezer has quit IRC12:46
*** dkranz has quit IRC12:50
*** samccann has joined #zuul13:04
tobiashShrews: is there a current release blocker for nodepool?13:04
Shrewstobiash: i don't think so13:05
tobiashShrews: was there a nodepool restart in openstack after the last fixes?13:05
*** elyezer has joined #zuul13:07
Shrewstobiash: we restarted before tagging the last release. we haven't restarted with any fixes after that (that i'm aware of)13:07
mordredShrews: we should probably restart with the sdk patch applied13:08
mordredtristanC: great job on that patch - and sorry it was frustrating!13:09
tristanCShrews: then perhaps the quota fix from tobiash call for a release?13:13
ShrewstristanC: maybe? i don't control the release13:14
Shrewsi'm not opposed to one13:14
tristanCmordred: oh well, javascript... if you don't mind the await usage then it's good, i couldn't make observer or eventemitter work similarly13:15
Shrewsbut i think openstack infra will want to restart nodepool again with the latest changes before a release13:15
mordredtristanC: it doesn't bother me - I think in this case we have to await because the routing information is the one thing we can't just fill in later13:16
tristanCmordred: otherwise i think we need to make each component subscribe to the zuul service and proceed to futher api call in a callback13:16
jheskethianw: sorry I missed your reply. Not sure yet, but was thinking about maybe submitting a zuulv3 talk if you were interested in co-presenting?13:17
mordredjhesketh, ianw: speaking of talks ... what are people submitting for LCA if anything?13:17
tristanCmordred: which could be implemented like that in a follow-up too13:18
mordredtristanC: nod. well, I think this at least un-breaks us13:18
mordredtristanC: and lets us step back and consider the overall structure13:18
Shrewsmordred: i don't think anyone else is interested in reviewing your shade-to-sdk patch, so maybe we should just land it by EOD today?13:19
mordredShrews: yah'13:21
mordredShrews: I mean- I don't blame them :)13:21
mordredShrews: oh - the recheck experimental did not work13:22
Shrewsmordred: b/c of dib issues. ianw put a fix up for dib pylint13:22
Shrewsmordred: we could either wait for that to land, or make a dependency13:22
mordredah - ok13:23
Shrewsmordred: https://review.openstack.org/58306813:23
mordredShrews: nod. I think we've banged on it pretty decently - if we restart it and things fall apart, we can revert13:25
jheskethmordred: great question.. I didn't have anything in mind yet. You should totally submit and come though ;-)13:27
openstackgerritMerged openstack-infra/nodepool master: Replace shade and os-client-config with openstacksdk.  https://review.openstack.org/57282913:38
mordredShrews: ^^ there we go13:39
*** dkranz has joined #zuul13:54
*** sshnaidm|rover is now known as sshnaidm|afk14:06
*** nchakrab has joined #zuul14:11
*** nchakrab_ has joined #zuul14:14
*** nchakrab has quit IRC14:17
Shrewsmordred: we'll need changes to the nodepool logging configs for sdk (so we don't forget)14:22
fungiwhat sort of deprecation/announcement period do we need for https://review.openstack.org/579434 (if any?)14:23
mordredfungi: I'm not sure - but I'm also not sure this will work as intended14:25
mordredbecause you can't pass a secret defined in one repo to a job defined in another repo14:26
mordredso people wanting to do this would need to make their own job that uses that role14:27
fungimordred: ahh, right can't make a variant of the job from zuul-jobs with the secret as an additional parameter14:27
mordredI think it might be worth pondering this use case and this specific job though and seeing what we think about it14:27
mordredfungi: yah - but I think this shows a clear usecase where such a behavior would be desirable from a user14:27
fungiwell, the alternative you had suggested was creating an account on rtd for the zuul server itself and then letting projects use the job with the embedded credential (and they'd have to grant the corresponding account access to their rtd project, similar to how our upload to pypi job works)14:28
*** gtema has joined #zuul14:34
*** quiquell is now known as quiquell|off14:35
tristanCmordred: same for upload-pypi jobs, i asked on http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-January/000212.html14:36
mordredfungi: yes - I think we could do that - but it seems like a legit case of desired reuse - and of course corvus has already laid out the implications we'd need to satisfy in order to make such a thing14:40
*** acozine1 has joined #zuul14:44
*** nchakrab has joined #zuul14:49
*** gtema has quit IRC14:50
*** nchakra__ has joined #zuul14:50
*** nchakrab_ has quit IRC14:53
*** nchakrab has quit IRC14:53
*** sshnaidm|afk is now known as sshnaidm|rover14:54
*** nchakrab has joined #zuul15:06
*** nchakrab_ has joined #zuul15:07
*** nchakrab_ has quit IRC15:08
*** nchakrab_ has joined #zuul15:08
*** nchakra__ has quit IRC15:09
*** nchakrab has quit IRC15:10
*** myoung is now known as myoung|biaf15:27
*** GonZo2000 has joined #zuul15:35
*** GonZo2000 has joined #zuul15:35
*** jiapei has quit IRC15:49
*** harlowja has joined #zuul16:18
corvusmordred: something like "allow a secret to be used by parent-job playbooks, but not children" ?16:18
*** myoung|biaf is now known as myoung16:19
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Docs: add a cross-ref in secrets  https://review.openstack.org/58330116:21
mordredcorvus: yeah. or maybe *hand wavey* only if the secret is attached to the job in a variant?16:21
corvusmordred: or project-pipeline variant?16:22
mordredyeah16:22
mordredI don't know how possible it is to distinguish - but "passing a secret as an 'argument' to a job" feels more like "I added a secret in a variant" than "I added a secret in a child job"16:23
mordredcorvus: I'm wildly gesticulating though16:23
corvusmordred: i agree this is worth thingking about and there may be opportunities for improvement.  i have many things rattling around in my head right now, so i may let the subconcious work on this one for a few days if further discussion isn't urgent.16:23
mordredcorvus: I do not think it is urgent16:23
corvusmordred: yeah, i grok the feeling you are trying to convey.16:23
corvusmordred: can you look at https://review.openstack.org/581888 and https://review.openstack.org/581909 when you have a sec?16:41
mordredcorvus: for you, I've got 516:42
corvusmordred: are the pbrx changes ready for final review?16:43
mordredcorvus: yes.16:44
mordredcorvus: I hit recheck on https://review.openstack.org/#/c/582396/ because I added a print to the end of hte pbrx job that will output the images built16:44
mordredbut that's cosmetic16:44
*** hashar is now known as hasharAway16:45
corvusmordred: thanks; i'll try to review them today16:45
mordredwoot!16:45
mordredcorvus: it should also be pretty easy to build locally if you want to poke at the results - 'pbrx --debug build-images' in your zuul directory should Just Work16:46
*** nchakrab has joined #zuul16:48
*** nchakrab_ has quit IRC16:50
*** tobasco is now known as tobasco_away16:54
mordredcorvus: you may want to add https://review.openstack.org/#/c/582732 to your list (it had a bad topic earlier)16:56
corvusmordred, tobiash: i have left some general ruminating comments on https://review.openstack.org/582794   i'm interested in your thoughts on that.16:57
corvusmordred: ack, thx16:57
openstackgerritMerged openstack-infra/zuul master: zk: retry initial zookeeper connection attempts  https://review.openstack.org/57604816:57
openstackgerritMerged openstack-infra/zuul master: dashboard: make ZuulService load info api to manage paths  https://review.openstack.org/57941816:57
openstackgerritMerged openstack-infra/zuul master: scheduler: fix enqueue event to use canonical project name  https://review.openstack.org/58004016:57
*** nchakrab has quit IRC17:02
*** nchakrab has joined #zuul17:02
*** acozine1 has quit IRC17:02
openstackgerritMerged openstack-infra/zuul master: Stop publishing docs to docs.openstack.org  https://review.openstack.org/58232317:04
openstackgerritMerged openstack-infra/zuul master: Fix line numbers in job repr  https://review.openstack.org/58190917:04
openstackgerritMerged openstack-infra/zuul master: Log cpu times of ansible executions  https://review.openstack.org/58271317:14
*** jluk has quit IRC17:19
openstackgerritMerged openstack-infra/zuul-sphinx master: Stop publishing to docs.openstack.org  https://review.openstack.org/58232617:20
openstackgerritMerged openstack-infra/nodepool master: Stop publishing docs to docs.openstack.org  https://review.openstack.org/58232517:28
*** goern has joined #zuul17:31
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: DNM Set pypi mirror to use 8080 instead of 80  https://review.openstack.org/58331717:39
*** sambetts is now known as sambetts|afk17:41
*** myoung is now known as myoung|lunch17:50
*** harlowja has quit IRC17:54
*** GonZo2000 has quit IRC17:59
*** ianychoi has quit IRC18:14
clarkblooking at slowness of zuul to enqueue changes from github, I'm beginning to wonder if part of it is a depends on to Gerrit18:15
clarkbspecifically https://github.com/kata-containers/proxy/pull/74 seems to be recheckable quickly if its depends on is merged but if it isn't merged then it takes forever (up to several hours) to show up in the zuul status at all18:15
clarkbbut I've had a hard tiem digging through logs to see where it is blocking so unsure if that is just coincidence or related18:16
*** electrofelix has quit IRC18:16
*** harlowja has joined #zuul18:32
*** sshnaidm|rover has quit IRC18:37
*** sshnaidm has joined #zuul18:39
*** samccann has quit IRC18:39
*** sshnaidm is now known as sshnaidm|rover18:44
*** myoung|lunch is now known as myoung18:47
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Fix devstack plugin for using openstacksdk  https://review.openstack.org/58333818:51
Shrewsmordred: that ^^ bit was missed in the sdk stuff. Not entirely sure if the whole LIBS_FROM_GIT stuff still applies in zuulv3 world?18:53
mordredShrews: we can probalby just delete that function - since sdk is already a part of base devstack installs18:55
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Fix devstack plugin for using openstacksdk  https://review.openstack.org/58333818:55
Shrewsmordred: k18:55
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Fix devstack plugin for using openstacksdk  https://review.openstack.org/58333818:56
*** eventingmonkey has quit IRC18:57
*** eventingmonkey has joined #zuul18:58
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Fix plugin and examples for using openstacksdk  https://review.openstack.org/58333819:03
corvusShrews: libs_from_git is set automatically for required-projects by the devstack job19:14
corvusShrews: so since openstackdsk is in required-projects in func-src-base, i think it should work as we expect (it will install openstacksdk from source always)19:15
Shrewscorvus: i figured as much, but i wasn't sure how to verify if we still needed that sh func19:16
clarkbdevstack or your devstack plugin must know to install it from source though19:16
clarkb(after checking libs from git, not sure if done for sdk)19:16
corvustrue -- so yeah, devstack would have to support installing openstackdk from git19:16
corvus    _install_lib_from_source "openstacksdk"19:17
corvusthat looks promising :)19:17
corvusso i think we're good19:18
corvusif you really wanted to be sure, you could push up a change to break openstacksdk and then depends-on it from a change to nodepool19:18
*** samccann has joined #zuul19:26
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Add role to ensure per-node output dirs exist  https://review.openstack.org/51182319:41
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Add role to fetch zuul logs from nodes  https://review.openstack.org/58334619:41
SpamapSHey has anybody worked on a manual-triggering via web interface thus far?19:50
SpamapSI'm going through the things Jenkins does for us to try and migrate as much off Jenkins and that's one thing Zuul isn't so great at.19:50
SpamapS(we have jobs where we plug in things like downtime windows and it goes off and runs automation to notify users and modify configs appropriately)19:51
mordredSpamapS: yeah - I'd be kind of concerned about adding support for the full jenkins parameterized build concept - because it's kind of a thing that stems from a very different worldview jenkins has19:56
mordredSpamapS: that said, I think tristanC and/or mhu have wanted some web-based triggering and/or worked towards such a thing19:56
mhumordred, SpamapS indeed we did! https://review.openstack.org/#/c/576907/19:57
SpamapSThe closest I have to it is adding a branch to an existing repo and merging empty commits. :-P19:57
SpamapSohh yeah that's nice19:58
SpamapSand autohold interface too19:58
SpamapSyay19:58
mordredSpamapS: have you considered putting downtime windows into a yaml file or somethign similar so that you can propose a change to announce a downtime and then land it when people agree abotsuch a thing?19:58
SpamapSI have all of that yes.19:58
mordredkk19:59
SpamapSBut these are ephemeral things.19:59
mordredsure19:59
SpamapSWe'd have a repo full of thousands of pointless yaml files if we did it for everything.19:59
mordredjust saying - if I have to click in a web browser and type text I always consider that a more systemic failure myself19:59
mordredbut if it works for you, then it works for you :)19:59
SpamapSSo we have a bot that does most of it without anyone thinking, in dev20:00
SpamapSbut even after that is done, there will be times where we need to override what it does.20:00
SpamapSlike not everything gets done with a perfect automation, sometimes you do need people to plug in overrides and teaching them yaml syntax vs. handing them a web form is not a great trade off.20:01
mordredheh20:01
SpamapSWe actually have moved a lot to our slack bot too20:02
SpamapSso you just @Bot do this thing with this data20:02
SpamapSand that's easier than yaml syntaxing :)20:02
SpamapSso another option is just being able to feed job parameters in via *anything* that isn't git20:02
SpamapSbut we could just make the bot make yaml and land it in git.20:02
mordredI guess I just don't understand what 'job parameters' are20:02
SpamapSThe most common case I have, it's a particular change order ID and an override scheduled time.20:03
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Add role to fetch zuul logs from nodes  https://review.openstack.org/58334620:04
mordredand then what happens when you trigger a job with a change order id and a time?20:04
SpamapSthe automation interrogates the change order system to find the server, asks openstack what resources are on the server, then notifies the owners of those resources of the scheduled downtime and modifies the change order appropriately.20:04
mordredgotcha. so sort of like passing two -e values to an ansible playbook20:04
SpamapSalso it disables the HV in openstack20:04
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: web: add tenant-scoped autohold, enqueue (change, ref)  https://review.openstack.org/57690720:04
mhuSpamapS, ^ needed a small rebase20:05
SpamapSmordred: yeah, it's just two inputs to a script20:05
SpamapSmhu: cool, I'll keep track. :)20:05
pabelangerianw: updated commit message20:05
SpamapSmordred: and that really is the base level thing I want. Arbitrary inputs to script. I *could* totally make a post job in a zuul.yaml and just have people land changes that set those values.20:06
corvusand to clarify, i think some version of mhu's approach is likely to land.  but it does not include 'parameters' -- that is something that we've restisted pretty strongly as it goes pretty hard against the grain of zuul, where all of the state is in git and things are repeatable.20:06
SpamapSBut that's just not a great experience.20:06
mordredSpamapS: so - I'll have to defer to corvus on his thoughts - but to me that sounds dangerously like turning zuul in to a competitor in the space of "arbitrary automation engine" ... yeah, what corvus said20:06
*** nchakrab has quit IRC20:07
SpamapSWell I mean I can wrap a zuul.yaml editor around github. Just wondering if it's something others have run into.20:07
SpamapSThe problem with *not* making zuul an arbitrary automation engine is that now I have two ways I have to run automation.20:07
SpamapSOne in test, and another in live. And that is sometimes very frustrating because the subtle differences bite us.20:08
SpamapSWhether it's a different version of ansible, or git repos in slightly different states.. We're in that situation now, and we are fine, but occasionally we find ourselves in a corner crying.20:08
mordredSpamapS: I'm not saying the use-case isn't valid - just that being complimentary to other things in a similar space lke AWX or Spinnaker is our current position in the ecosystem - and I'd rather stay friendly with those projects than competitive with them20:09
SpamapSYeah, we've got something AWX-like20:09
mordredSpamapS: so the thing you're talking about is one where the ramifications may be fairly broad and it would need some careful thought as to what it means for what we're doing20:09
SpamapSwhich is, a slack bot / eventing engine + ARA20:09
corvusapparently awx is now called 'tower'20:09
mordredoh? the split didn't take?20:10
mhucorvus, mordred I get your reasons against parameterized jobs but from users feedback, we're seeing the same requests as SpamapS20:10
corvushttps://docs.ansible.com/ansible/latest/reference_appendices/tower.html20:10
SpamapSAnd running the same playbook that ran in zuul, through that, has some serious problems.. not the least of which being that watching Ansible run in realtime in ARA *sucks*20:10
SpamapSah tower again, ok20:11
SpamapS:)20:11
mordredcorvus: oh - it was originally called awx - then it turned in to tower - then when they open sourced tower they called that awx20:11
dmsimardyeah, AWX is the proper name of the upstream of Tower20:11
SpamapSwell either way.. I'd much rather just run every *ansible* piece that runs in gate, the same way in post/prod/etc., if possible.20:11
SpamapSLike if Spinnaker or Tower are going to come into play, I'd want to use them in gate too. :-P20:12
SpamapSBut anyway, for parameterization, I think I understand where Zuul's at.20:12
mordredyah - same way in post/prod makes total sense - it's just that in check/gate there isn't really a place to provide parameters - so if the prod version si parameterized it's still different than check/gate20:12
SpamapSI don't mind at all having a repo that is like 'change-order-overrides' and has a post job that runs every time we land a change to the vars.20:12
SpamapSWould be nice to have a git log of all the change order overrides. ;)20:13
mordred++20:13
mordredgit log turns out to be quite nice!20:13
* corvus <3 git logs20:13
SpamapSAlso I do have post jobs that deploy to prod, and it works great, but they spin up a VM to run ansible, because I don't know how to do static nodesets, so, there's a lot to think about there.20:14
SpamapSWhat does work nicely is that I have a deploy-to-stage and deploy-to-prod that depends on it20:14
SpamapSso if the stage deploy 'splodes, prod is protected.20:14
mordredSpamapS: we've got some stuff coming that should help that ... and also we're about to start doing it in infra too20:16
mordredSpamapS: so over the next couple of months we should be able to have better conversations about post jobs deploying to prod20:17
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Add role to fetch zuul docs from nodes  https://review.openstack.org/58335020:18
*** hasharAway is now known as hashar20:24
*** dkranz has quit IRC20:37
pabelangerjust sent a ML post to zuul-discuss around base jobs, if people are interested.20:52
mordredpabelanger: I'm always interested20:55
pabelangernothing major, just something I'm considering in doing for rdoproject20:57
corvusi read that message as "i volunteer to write the documentation for how to build and use base jobs"20:58
pabelangeryah, i guess I walked into that :)21:00
*** samccann has quit IRC21:01
openstackgerritMerged openstack-infra/zuul master: Build container images using pbrx  https://review.openstack.org/58016021:01
openstackgerritMerged openstack-infra/zuul master: Specify a prefix for building the images  https://review.openstack.org/58239621:08
openstackgerritMerged openstack-infra/zuul master: Install less than alpine-sdk  https://review.openstack.org/58306221:08
corvuspabelanger: replied.  also, fwiw, there's nothing magic about the name 'base'.  you can set the default parent job for a tenant (it just defaults to 'base'.  that's the default default.)21:09
corvuspabelanger: might be worth suggesting that approach in the openstack-infra context too?21:09
pabelangercorvus: yah, I wanted to first float the idea here. So far the largest issue we've had around base jobs, is less experienced people in rdoproject merging changes to base and hoping they work. I'll bring up the topic with openstack-infra shortly21:24
clarkbpabelanger: base jobs must be in trusted repos though right?21:25
corvuspabelanger: regardless of this, it's pretty important that anyone who has permissions to merge changes to a config repo agrees on the parameters for merging those changes.  it's called "trusted" for a reason.21:25
corvuslike, by all means, let's make things better and more convenient.  but there's also an underlying issue if you can't trust the trusted repo reviewers, and that issue won't go away even if we improve the ux.  it's better to fix this from a POV of "the trusted repo reviewers are inconvenienced by this" rather than "the trusted repo reviewers don't understand what they're being asked to do".21:27
corvusclarkb: *base* jobs must be in trusted repos.  iirc, default-parent jobs can be anywhere.21:27
corvus(a base job is a job with no parent.  the default parent for jobs which don't specify a parent is (by default) named "base".  that job can be defined anywhere though)21:29
corvusso pabelanger's suggestion of "base-minimal" (actual base job) as the parent of "base" (counterintuitively not a base job) and using "base" as the default-parent should work.21:30
clarkbgotcha21:30
corvusas would having "base" be an actual base job and "pabelanger-base" as a child of base, and setting "default-parent: pabelanger-base" in the tenant21:30
*** hashar has quit IRC21:36
openstackgerritMerged openstack-infra/zuul master: Fix broken templates for projects in dependent pipelines  https://review.openstack.org/58188822:01
* mordred wants to adopt a system where one of our base jobs is called "pabelanger-base"22:22
*** sambetts|afk has quit IRC22:26
ianwjhesketh: i did offer a infra/zuul-ish talk for the sydney infra day thing ... i framed it more as an overview of openstack's change process.  i don't think they're that interested in openstack talks22:27
*** sambetts_ has joined #zuul22:28
*** myoung is now known as myoung|off22:31
pabelangercorvus: re: 'trusted for reason' Yup, just some growing pain on new zuulv3 users not understanding the power22:56
*** rlandy has quit IRC23:24
fungiianw: jhesketh: i learned a few years ago to stop mentioning "openstack" in my abstacts23:46
fungior i should have. i think a passing mention in my ato proposal is likely what got my open community vulnerability management talk nixed from this year's lineup23:46
fungiat this point conferences are afraid an "openstack" talk makes them look old and dusty23:47
fungioh, openstack... that thing kubernetes replaced?23:47
ianwfungi: yes, this one even has the subtitle "Previously known as OpenStack Australia Day,"23:54

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