Wednesday, 2018-08-15

clarkbSpamapS: my hunch is that the vast amount of io that ansible and git do is improved when jumping between page tables00:00
clarkbbut I haven't really dug in because I'm happy to take the performance bump as is :)00:00
fungia gift from the kernel gods00:00
clarkbinterestingly this improvment appears to come without pcid flag on our VM cpus00:02
openstackgerritJeremy Stanley proposed openstack-infra/zuul-website master: Add a temporary summit promotional message  https://review.openstack.org/59187000:05
fungithat's very much wip00:05
*** rlandy has quit IRC00:43
openstackgerritJeremy Stanley proposed openstack-infra/zuul-website master: Add a temporary summit promotional message  https://review.openstack.org/59187001:27
fungii added a block to the css to override styling of p in a banner, but kept consistent with the existing color scheme01:30
corvusfungi: cool, that generally looks good....  but now that i see that, perhaps we should also post an ansiblefest thing -- after all, we'll have a booth there01:59
fungiindeed!01:59
corvusfungi: you might consider a little more horizontal space between the text and the button, and a slightly larger font on the button02:00
fungiheh, jimmy just suggested that in another conversation (the extra space). i had it in locally and removed it because i wasn't sure it was warranted, but easy to add02:00
corvusgood typography is universal! :)02:01
fungiand if i just switch to the normal button class instead of the small button, that probably addresses the size concern02:01
openstackgerritJeremy Stanley proposed openstack-infra/zuul-website master: Add a temporary summit promotional message  https://review.openstack.org/59187002:13
fungisee if that's ^ any better02:13
*** openstack has joined #zuul02:36
*** ChanServ sets mode: +o openstack02:36
*** pcaruana has joined #zuul05:12
openstackgerritneilsun proposed openstack-infra/zuul master: Using zuul string format for zuul web static_cache_expiry option  https://review.openstack.org/59191706:31
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: [wip] web: rewrite interface in react  https://review.openstack.org/59160407:21
tristanCmordred: corvus: ^ rewrote the status page in react and added stream navigation. though the ws code remains to be written.07:25
*** lennyb has joined #zuul07:27
*** lennyb has quit IRC07:28
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: [wip] web: rewrite interface in react  https://review.openstack.org/59160407:28
*** lennyb_ has joined #zuul07:34
*** lennyb_ is now known as lennyb07:35
*** lennyb has quit IRC07:35
*** electrofelix has joined #zuul07:40
*** lennyb_ has joined #zuul07:40
*** lennyb_ is now known as lennyb07:41
*** lennyb has quit IRC07:41
*** lennyb has joined #zuul07:44
*** lennyb has quit IRC08:28
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: npm: add CI=true environment  https://review.openstack.org/59196408:37
*** andreaf has quit IRC09:16
*** mattclay_ has joined #zuul09:17
*** andreaf has joined #zuul09:17
*** mattclay has quit IRC09:18
*** robled has quit IRC09:18
*** mattclay_ is now known as mattclay09:18
SpamapSman, it helps if you actually push your images into the registries you created, and not some random test string named one that you had hard coded10:18
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: [wip] web: rewrite interface in react  https://review.openstack.org/59160410:39
*** panda|ruck is now known as panda|ruck|lunch11:25
*** panda|ruck|lunch is now known as panda|ruck11:53
*** rlandy has joined #zuul12:31
*** samccann has joined #zuul12:50
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Add npm lint target back  https://review.openstack.org/59202213:01
mordredtristanC: cool! there ^^ is a followup patch adding a lint target back (thought it would be a good way to learn some things)13:01
mordredtristanC: there's still about 10 linter errors with that that don't make sense to me yet but might make sense to you13:02
mordredgit diff13:02
mordredgah13:02
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Add npm lint target back  https://review.openstack.org/59202213:13
SpamapSmordred: so.. now.. the container images..13:14
mordredSpamapS: talk to me13:14
SpamapSmordred: I am running into things like, there's no /var/run/nodepool13:14
SpamapSBefore I run off and paper over all of that.. do you have suggestions?13:14
mordredSpamapS: well - I think I'd been expecting that stuff like that would be attached as volumes?13:15
SpamapS/var/run should actually clear out when the container dies, so it should not be a volume.13:15
SpamapSNot even an emptyDir13:16
mordredwhat are we putting in /var/run ?13:16
SpamapSnodepool wants to put a pid file there13:16
SpamapSso I can probably find a place for it that exists13:16
mordredah - yes. that pid file doesn't seem useful in a container context does it?13:16
SpamapSand not care13:16
SpamapSbecause I don't actually need a pid file13:16
SpamapSbut.. papering.13:16
mordredSpamapS: that's part of the fork/daemonization right? would it be better to have k8s run it as a foreground process? (just thinking out loud, I don't know the answers)13:17
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Add npm lint target back  https://review.openstack.org/59202213:37
mordredtristanC: ok - a few more tweaks there ^^ I fixed some of the issues, but also properly enabled the standardjs rules, so it produced a few more errors :)13:37
openstackgerritMerged openstack-infra/zuul master: Remove non-working html code in div container  https://review.openstack.org/59145913:38
sshnaidmdoes anybody know when during the job job_timeout starts to count? http://logs.openstack.org/95/586595/1/check/tripleo-ci-centos-7-containers-multinode/b8a44d3/job-output.txt.gz13:40
sshnaidmif it from very start of zuul ececution or after some playbooks?13:40
SpamapSmordred: Yeah I'm wondering if we might want some standard interface for pbrx to run the entry points with some helpful hints that they should assume container.14:04
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Add npm lint target back  https://review.openstack.org/59202214:04
SpamapSmordred: or have some kind of way to express final steps to prep the container14:05
Shrewssshnaidm: i *think* zuul.timeout starts includes both pre and run playbooks. zuul.post_timeout is only the post playbook14:06
SpamapSFor this one, we could probably just add an os.makedirs before the pidfile?14:06
mordredSpamapS: I think I'd prefer the first one, cause the second one feels like it would start getting complex14:06
sshnaidmSpamapS, so it's from very beginning of the job, right? And is there way to find out when job started from within the job itself?14:07
mordredSpamapS: maybe so? could also be helpful on non-container deploys if someone has an ephemeral /var/run filesystem and the box reboots14:07
SpamapSsshnaidm: 301 Shrews14:07
SpamapSmordred: yeah, generally you aren't running nodepool-launcher as root, so that makedirs is going to fail14:08
sshnaidmSpamapS, oops, sorry :)14:08
sshnaidmShrews, ^^14:08
SpamapSsshnaidm: no worries. :)14:08
SpamapSit happens14:08
sshnaidmSpamapS, we are a lot in the "S-" club14:08
SpamapSmordred: this is a fairly common tactic btw..  https://github.com/kubernetes/contrib/blob/master/statefulsets/zookeeper/Dockerfile#L48-L5714:09
Shrewssshnaidm: should begin at the start of pre playbook run. i'm not sure if the start time is readily available. corvus would know for sure14:10
pabelangersshnaidm: Shrews: yah, job_timeout right now is shared for both pre-run / run phases. We've talked about creating a pre-run timeout before: https://git.zuul-ci.org/cgit/zuul/tree/zuul/executor/server.py#n99714:11
corvustristanC: is it not possible to use jquery with react?  we want to remove it anyway, so that's fine, but i thought if jquery could be used it would make the react patch simpler since we could change the status page later.14:14
tristanCcorvus: i think it is possible to mix both, but i would prefer we take this opportunity to clean-up the code too.14:15
tristanCcorvus: with the ChangeQueue component, it will be possible to create a status page for a single change too14:16
tristanCcorvus: i did keep the bootstrap classes and structure, rewritting the jquery bit in react is quite straighforward14:17
tristanCmordred: that's great, thanks. i'll add rebase follow-up on the linters then, and we should squash when we are satisfied14:18
mordredSpamapS: nod. worth pondering a bit14:18
mordredtristanC: yah - I think squashing is definitely easier/better than trying to keep it as a stack and rebasing14:19
corvustristanC: ok; because of all the details on the status page, it might take a little longer to get this through, but if you're willing, it'll be worth it.  :)14:19
mordred++14:19
tristanCcorvus: it's mostly done, see: http://logs.openstack.org/04/591604/7/check/zuul-build-dashboard/6247836/npm/html/14:20
corvustristanC: i know, that's what i was looking at :)14:20
corvustristanC: it looks good, just a few details which may or may not be easy to resolve :)14:20
corvustristanC: are those glyphicons or fontawesome?14:23
corvusor something else? :)14:23
pabelangertristanC: wow, that looks nice14:23
tristanCcorvus: they are provided by patternfly, it mixes bootstrap and fotawesome14:24
tristanCpabelanger: thanks :-)14:24
mordredalso - I'd like to note that the react patch adds javascript unittests14:25
mordredand a test job to run them14:25
mordredthere is only one test - but I like that it exists and that there is a place to add more14:26
corvussshnaidm, Shrews: i don't believe the start time is exposed as a var, but it would be easy to do so.14:26
sshnaidmcorvus, where is better to do it?14:26
mordredtristanC: if it's easier for you to squash the lint patch sooner rather than later, please feel free - I don't feel any ownership of it, it was more just an opportunity to poke a little bit14:26
SpamapSmordred: to be clear.. the zk approach isn't helping either... feels like the container world just isn't in to uniformity in this area.14:27
sshnaidmcorvus, maybe here? https://github.com/openstack-infra/zuul-jobs/blob/master/roles/emit-job-header/tasks/main.yaml#L714:27
corvussshnaidm: if you want to add it to zuul, here would be the place: http://git.zuul-ci.org/cgit/zuul/tree/zuul/executor/server.py#n142514:28
mordredSpamapS: yah. it's an area I'd like to think about a bit as we beat our heads around this - because if the idea behind these container images we're producing is that they should be single-process style containers (as opposed to light-weight vms) - it seems like we'll want some patterns - like signaling info re: daemonization, what things should write to local disk vs. volumes, etc14:29
fungianybody aware of any zuul-oriented talks which got accepted for ansiblefest?14:29
sshnaidmcorvus, sorry, I'm not familiar with this code. When is it executed?14:30
pabelangerfungi: I don't think anything has officially been announced?14:31
corvusfungi: i think rbergeron & co were finishing up selections recently14:31
fungipabelanger: yeah, i suppose at most people just know whether they've submitted any talks on the subject14:31
fungithanks corvus!14:31
corvussshnaidm: that's the code which creates the inventory file with the 'zuul' variables before zuul runs ansible14:31
corvusfungi: i know people have submitted talks on the subject!14:32
sshnaidmcorvus, I see.. so setting timestamp there will be actually before the job itself starts14:32
SpamapSmordred: yeah, I wonder if we should just have a set of standard envvars, like PBRX_CONTAINER=1, that we can set in the container image, and the python can inspect to make decisions.14:32
SpamapSthough I'm actually getting around it now with CLI args14:33
fungicorvus: awesome!14:33
SpamapSwhich is how zk gets around it14:33
SpamapSfungi: My talk was accepted!14:33
SpamapSI'll be sharing how we use Zuul at GoDaddy14:33
fungiSpamapS: at ansiblefest? neat!14:34
corvusmordred, SpamapS: i'm not super excited about having zuul look at PBRX env vars in the code, but it seems entirely appropriate to have a command-line or config option which causes it to run in the foreground, and perhaps some setup.cfg or whatever file that says to use that for pbrx...14:36
corvustristanC, mordred: what's with the "#" in the url?14:37
tristanCcorvus: right, so the implementation is using the HashRouter for route14:38
tristanCi picked this one as it will make static file simpler to use, all webclient request reach a single index.html file14:39
tristanCwe could use the BrowserRouter to make navigation use '/' instead of '#' in the url14:40
tristanCbut then, this need special server route to redirect the path to the root index.html14:40
corvusi'm a big fan of urls that are meaningful and look like urls, though the single file certainly has advantages.  i'd love it if we could have both (path routing is a thing!), but if not, we'll have to think about the trade-offs.14:44
mordredI feel the same way - I like the current non-hash urls - but they do come with a cost, including but not limited to making it extra hard to serve multi-tenant dashboard code from swift ...14:45
mordredsince this is using webpack under the coveres and we've solved the non-hash urls with that already I'm confident we can do it for this14:45
mordredbut it may be worth pondering tradeoffs for sure14:46
tristanCit's a simple change to restore the path routing using the BrowserRouter, just need to adapt the api module to discover the base path of the api when loaded from a sub-path14:47
tristanCbut can we at least drop the ".html" extensions and the make all the route reach a single index.html file?14:47
corvustristanC: yeah, let's give that a shot and see how it looks.14:48
corvus(i'd love to drop the html extensions)14:48
tristanCmordred: i'll squash the lint and fix the last issue now15:40
mordredtristanC: cool15:43
panda|ruckpabelanger: how much you think it's difficult to make job.extra_vars: able to include variables from a file ?15:56
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: [wip] web: rewrite interface in react  https://review.openstack.org/59160415:56
tristanCcorvus: mordred: last PS adds status page filters and default expand checkbox :)15:57
panda|ruckpabelanger: or any vars: invocation15:57
pabelangerpanda|ruck: don't think it would be too difficult, we'd likely want to have a discussion about how to implement it first15:57
panda|ruckpabelanger: thanks.15:58
corvustristanC, mordred: when i run 'npm run start' i get npm ERR! enoent ENOENT: no such file or directory, open '/home/corvus/git/openstack-infra/zuul/package.json'15:58
corvusknow what i have to do to run tristanC's change?15:58
mordredcorvus: you need to cd into the web subdir15:59
mordredin the patch all of the js related things are shifted into the web dir, including the package.json15:59
corvusmordred: oh, ok :)15:59
corvusthat also makes yarn install do something other than exit successfully quickly15:59
mordredyeah. yarn install in the web dir too16:00
tristanCcorvus: also, once you have yarn installed, you can "yarn build" or "yarn start"16:01
corvustristanC: it looks like that isn't set up to use the openstack api yet, just local?16:02
tristanCcorvus: yes, you have to use REACT_APP_ZUUL_API_ROOT="https://zuul.openstack.org/zuul/api/" environment variable16:02
tristanC( https://review.openstack.org/#/c/591604/8/doc/source/developer/javascript.rst )16:03
tristanCcorvus: or you can wget the endpoint in the "web/public" directory and it will query the local files16:03
mordredwe can likely add some of that back to package.json like we had before16:08
corvusmordred, tristanC: an interesting side effect of using glyphs instead of images for the circles is that the lines may not line up any more.  it's designed as a sort of grid with the circles and lines having the same width16:12
corvusmordred, tristanC: maybe we can set the glyph css to a pixel value16:13
mordredcorvus: yah - I never got the glyphs patch I tried originally to work16:13
mordredthat's probably a good idea16:13
corvustristanC: oh!  the fa and pf icons are different sizes; i don't think we can mix them16:16
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP fix status lines  https://review.openstack.org/59214516:20
corvustristanC: ^ that corrects the size and makes things line up, but we need to find 2 alternate icons16:20
corvustristanC: basically, they need to render as 16x1616:20
corvusthe pf icons do, but not fa16:21
corvusbut maybe there are other alternates, that's just a quick change to demonstrate it working16:21
*** panda|ruck is now known as panda|off16:22
mordredwoot16:23
mordredcorvus, tristanC: incidentally "yarn run build" or "yarn run lint" are slightly nicer output-wise than npm run build|lint ... basically because you don't get the npm exception traceback boilerplate at the end16:24
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: [wip] web: rewrite interface in react  https://review.openstack.org/59160416:25
tristanCmordred: and you can just run "yarn lint" too16:25
tristanClast PS adds "yarn start:openstack" and "yarn start:multi"16:26
*** openstackstatus has joined #zuul16:59
*** ChanServ sets mode: +v openstackstatus16:59
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP fix status lines  https://review.openstack.org/59214517:09
openstackgerritAndreas Jaeger proposed openstack-infra/zuul-website master: Link to Zuul Sphinx extension  https://review.openstack.org/59128217:09
corvustristanC: there we go, i found some icons ^ that at least should fix up all the lines and icons.  feel free to squash.17:09
SpamapScorvus: yeah I think now that I'm getting into the meat of the problem, CLI switches seem to be able to solve all my issues.17:10
SpamapS(regarding earlier envvar things)17:19
SpamapSa lot of what is getting me is that I am stealing tobiash's stuff and it has non-standard paths for stuff17:21
tristanCcorvus: nice! i'll squash tomorrow.17:22
SpamapShrm17:41
SpamapShaving trouble getting the pidfile name changed :-P17:41
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow run to be list of playbooks  https://review.openstack.org/59216017:43
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow run to be list of playbooks  https://review.openstack.org/59216017:44
pabelangermordred: corvus: tobiash: tristanC: ^propsed again for job.run to be a list of playbooks. I've included a few use cases in the commit message17:45
pabelangershould add reno note there too17:45
openstackgerritMonty Taylor proposed openstack-infra/zuul master: [WIP] Fix post pipeline change display  https://review.openstack.org/59216517:51
mordredtristanC: ^^ that should fix the uuid overflow in post pipeline (which makes me sad, I like the abbr idea - but it seems to be being stripped out)17:51
mordredpabelanger: could you say more words to me about "One example would be your job workflow would be to run multiple playbooks on the same host but use different groups in an inventory file." ?17:52
mordredpabelanger: (mostly my brain can't wrap itself around those specific words)17:53
pabelangermordred: let me remove that, as it is not valid for me any more17:53
mordredok.17:54
mordredI like the second one you wrote - that does seem to be in keeping with the concept "test using your production playbooks"17:54
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow run to be list of playbooks  https://review.openstack.org/59216017:55
pabelangermordred: refreshed the first17:55
pabelangerthat would be an example of tripleo does for their quickstart playbooks17:56
corvusmordred, pabelanger: is this better than having a job playbook which includes the setup / test playbooks?17:58
corvuswith the existence of import_playbook it feels like borderline implementing ansible in zuul17:59
pabelangercorvus: that's how I done things so far today, single playbook to setup / test. However, I'm currently exploring the idea of using an external library to test, in this case testinfra. eg: https://review.openstack.org/591888/ For that, its looking more like ansible to setup then tox to test18:02
*** sshnaidm is now known as sshnaidm|bbl18:05
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow run to be list of playbooks  https://review.openstack.org/59216018:10
mordredcorvus: for reasons I cannot explain, I find import_playbook makes me uncomfortable18:13
corvushrm.  given that ansible has a construct for "run these two playbooks in series and exit immediately with failure if one of them fails", i feel like we need a compelling case for why we should reimplement that in zuul18:14
corvusmy understanding is it would look something like this: https://etherpad.openstack.org/p/YBnjOEpHOD18:15
pabelangerthere is also variable scoping issue with ansible and import_playbook. But running ansible-playbook twice, you don't get variables from first run in 2nd, which is how tripleo works today too18:15
mordredyah - I believe import_playbook is processed at compile time18:16
corvusnow we're getting somewhere :)18:16
corvusso there is a substantive difference between a playbook with 2 import_playbook calls, and two separate ansible-playbook invocations?18:16
mordredhttps://twitter.com/thejimic/status/1026969663169863681 <-- jimi_c was saying that he's been resisting doing include_playbook, which would, I think, be the more similar construct18:16
pabelangercorvus: I believe yes, but would need to dive more into testing again.  IIRC, when I last looked variables did leak across import_playbook18:18
mordredcorvus, tristanC: hrm. I have no idea why https://review.openstack.org/#/c/592165 didn't work - I must be missing something obvious somewhere18:18
mordredpabelanger: like if you do a set_fact in playbook 1 I'd suppose18:19
pabelangeror register18:20
pabelangerbut ya18:20
corvusmordred: that looks like some kind of react compile error?18:20
corvusthat's impressive18:20
corvusmordred: i don't think abbr is getting eaten, it must be that changeText isn't getting set18:23
mordredyes. I have verified that a playbook with two import_playbooks leaks variables from the first to the second18:23
corvusmordred: maybe that regex test isn't working?18:23
mordredcorvus: well, when I opened it in inspector in firefox there was no abbr ?18:23
mordredoh - I see what you're saying18:24
*** electrofelix has quit IRC18:25
mordredcorvus: where did you see a compile error?18:25
corvusmordred: when i opened the test build for 59216518:26
corvusi see Invariant Violation: "Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7BchangeText%7D&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. "   in the console18:26
mordredcorvus: oh neat18:27
pabelangermordred: are you at a point where you can start publishing pbrx images for zuul? or is there something blocking18:31
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow run to be list of playbooks  https://review.openstack.org/59216018:32
corvuspabelanger, mordred: i think the standard here should be that zuul should not reipmlement things ansible already does, but allow ansible operators to do the sort of things they would do with ansible in production.  it sounds with the latest info, list-of-run-playbooks meets that threshold.  let's just make sure we write that up to justify it.18:37
pabelangersure, let me get some coffee and I'll update the commit message18:38
mordredpabelanger: yes - although we need to write a pbrx push command and then we need to make a push job with the infra account credentials18:59
mordredpabelanger: but other than that, we're totally ready :)18:59
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Allow run to be list of playbooks  https://review.openstack.org/59216019:01
pabelangermordred: ack! I'll look to see how loci and kolla are doing it19:03
mordredpabelanger: my thinking on the command, if that is a thing you want to push on - is that there is ProjectInfo class in pbrx.container_images19:03
mordredpabelanger: that does the work to figure out what the list of console scripts would be19:03
mordredpabelanger: (which in turn can provide the list of image names to push)19:03
pabelangerk19:03
mordredpabelanger: so I was thinking add a pbrx push-images command that also takes an optional --prefix argument19:04
mordredthat would do docker push on every image name that pbrx build-images would have built19:05
mordredpabelanger: probably if prefix is given, we want to skip pushing the unprefixed names19:05
mordredpabelanger: then lifting the code from loci to set up the docker config from a zuul secret is probably a great plan19:06
mordredpabelanger: (also, if ou don't have time for that, I'll get around to it one of these days I promise :) )19:07
pabelangermordred: have _some_ time, so I can poke into it and see how it works19:11
Shrewsi have some cycles (and a mostly working wrist now) I could spend on that, too if pabelanger would rather look at other things19:11
pabelangerShrews: np if you want to look too19:12
*** openstackgerrit has quit IRC19:19
*** sshnaidm|bbl is now known as sshnaidm19:22
Shrewsmordred: hrm, it's not pbrx's intent to build 2 images for each entrypoint when a prefix is supplied, is it?20:05
Shrewsmordred: e.g., for nodepool where we have pbrx_prefix=zuul    http://logs.openstack.org/12/590412/3/check/pbrx-build-container-images/12d8e91/job-output.txt.gz#_2018-08-14_15_56_03_36765220:05
mordredShrews: yah - it's probably better to only tag them with the prefix if prefix is given20:07
*** elyezer_ has joined #zuul20:25
*** elyezer has quit IRC20:29
*** openstackgerrit has joined #zuul20:53
openstackgerritMonty Taylor proposed openstack-infra/zuul master: [WIP] Fix post pipeline change display  https://review.openstack.org/59216520:53
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP fix post change id link  https://review.openstack.org/59219720:53
mordredcorvus, tristanC: ^^ ok there it is20:53
corvusmordred: omg lets see if we found the same thing :)20:53
mordredcorvus: hah. jinx20:53
corvuser, close, but different20:54
*** samccann has quit IRC20:56
corvusmordred: yours is a more faithful port of the jquery code, i'll abandon20:57
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Map file comment line numbers  https://review.openstack.org/59044221:38
openstackgerritMerged openstack-infra/zuul-jobs master: Add icons to index files  https://review.openstack.org/59153522:14
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: Add private key storage migration  https://review.openstack.org/59221323:01
* SpamapS fighting through making his base post job scp logs to a log storage server23:12
mordredSpamapS: you've seen the logs-in-swift stuff corvus has been working on yes?23:49
SpamapSI have23:49
SpamapSit makes me hahppy23:49
mordredkk. just making sure23:49
mordredit makes me happy too23:49
SpamapScause I have a big ceph cluster23:49
SpamapSwith swift API23:49
SpamapSso.. +123:49
mordredalthough - the zuul-inline-comments makes me a bit more giddy23:49
mordredSpamapS: we're very close to flipping the switch for ourselves23:50
SpamapSwhat I really need next btw, is fast-forward-gate23:50
mordredSpamapS: I know all of those words, but I don't know what they mean in that combination23:50
SpamapSwhich basically means, for a slower-moving repo where most changes happen one at a time.. but sometimes things explode with 10... I want check->gate to be instant if it can fast forward.23:50
mordredoh - right - the thing darragh tweeted about23:51
SpamapSso that when people submit a change, it passes checks.. any jobs that are the same in check/gate, just get auto-passes if the commit fast forwards.23:51
SpamapSI didn't know anybody else tweeted this.23:51
mordredyah. electrofelix did the other day23:51
SpamapSBut.. it just seems silly to re-run jobs on the same git state.23:51
corvusSpamapS: it's not silly23:51
mordreddependencies outside of the git code change23:51
mordredfrequently, it turns out23:51
SpamapSWhen the job takes 2 hours and it *just* ran, it's a huge waste of my team's time. They usually just end-around and force merge.23:52
corvuseither external dependencies, or internal (zuul-managed ones)23:52
*** rlandy is now known as rlandy|afk23:52
SpamapSWhich compromises the whole gating paradigm.23:52
corvusSpamapS: i hear what you're saying, and i'm not saying we can't do it, but i am saying it's not silly, and it's complicated, and if we're going to do it, it's going to take some thought.23:53
SpamapSTotally makes sense if the check is stale or something. But I have a ton of instances where somebody makes a fix, pushes itup, checksrun, approvals happen, and then .. 2 more hours while we wait.23:53
corvusSpamapS: may i suggest an alternative?  skip check?23:53
mordredyeah. on those repos skipping check and going straight to gate might be a better choice at the moment23:54
corvusi believe that gate requiring a check vote is an anti-pattern.  don't copy that from openstack.23:54
corvusthat's something openstack does because it operates in a specific environment where that's necessary23:54
SpamapSGitHub reinforces that.23:54
SpamapSbecause the thought is you need checks to be required.23:55
SpamapSBut your point makes sense.. we could not require the openstack check for gate.23:55
mordredsure. but the gate votes add the checks and then do the merge23:55
corvusSpamapS: happily, zuul can enforce that for you instead of github23:55
corvusas soon as zuul splits into its own tenant, i would like to remove the clean-check requirement from zuul's own gate23:55
clarkbcorvus: I'n not sure I would go so far as to say it is an anti pattern. Check provides extremely useful information to reviewers in many cases23:55
corvusthen we'll be a better exemplar of the process23:55
mordredin fact, github's behavior + zuul without check-vote-required will make the manual "just merge it" seem more extreme23:56
corvusclarkb: i'm not suggesting we remove check :)23:56
clarkbcorvus: and needing to swing back around and check if gate worked after you approve instead of just checking it upfront can be clunky23:56
corvusclarkb: i'm suggesting we remove the requirement.  if check provides something you need (eg, review of rendered docs) by all means wait for it23:56
clarkbah gotcha23:56
mordredlike the ansible-role-puppet patch we just +A'd23:56
SpamapSI tend to use check passes as a gate into my review queue..23:57
clarkbya I would agree that gate requires check is a bit :(23:57
mordredwe had to wait an extra test cycle for it even though you +A'd it 30 seconds after I pushed it up23:57
mordredSpamapS: me too - usually23:57
SpamapSBut I am happy to skip that in urgent situations23:57
mordredbut if you remove that requirement, then if a patch gets a +A before check is done, it'll go straight to gate23:57
SpamapSso yeah, I think not waiting for the status in gate makes sense.23:57
mordred++23:57
SpamapScorvus: I bow to your wisdom sir. :)23:57
corvusSpamapS: i accept your user requirements :)23:58
corvuswe'll talk about the ff thing more i'm sure, i just think to do it right in zuul is going to need a bit more... computation... than it seems at first glance.  and the skip-clean-check thing might be an immediate win (plus good on its own)23:59
mordredI had just written those words - but worse23:59
corvus(my guess is we'll need a real build database that we can depend on so we can query some things about history and git repo states)23:59

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