Friday, 2017-08-04

openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove state_dir requirement from merger  https://review.openstack.org/49068200:11
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat github driver docs  https://review.openstack.org/49068800:34
*** http_GK1wmSU has joined #zuul02:34
*** http_GK1wmSU has left #zuul02:35
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Prevent execution of locally overridden core modules  https://review.openstack.org/49021603:21
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add some ansible plugin tests  https://review.openstack.org/45439603:21
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Allow and document use of the uri module from localhost  https://review.openstack.org/49021503:21
mordredrebased to fix merge conflict caused by one of the docs patches03:22
mordredjeblair: it might be?03:22
mordredjeblair, SpamapS, pabelanger: https://review.openstack.org/454396 passes tests now if you have a chance to poke it in03:27
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat merger and executor config docs  https://review.openstack.org/49066503:31
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat web section  https://review.openstack.org/49066603:32
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: update format in connections.rst  https://review.openstack.org/49067203:32
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat gerrit driver docs  https://review.openstack.org/49068103:33
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Remove state_dir requirement from merger  https://review.openstack.org/49068203:34
*** bhavik1 has joined #zuul04:28
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Add some ansible plugin tests  https://review.openstack.org/45439605:12
*** bhavik1 has quit IRC07:01
*** amoralej|off is now known as amoralej07:23
openstackgerritJoshua Hesketh proposed openstack-infra/nodepool master: Clarify diskimage names in docs  https://review.openstack.org/49078107:42
*** http_GK1wmSU has joined #zuul08:03
*** http_GK1wmSU has left #zuul08:04
*** electrofelix has joined #zuul08:42
*** openstackgerrit has quit IRC10:18
*** jkilpatr has joined #zuul11:01
*** dkranz_ has joined #zuul12:22
electrofelixI've notice an odd behaviour when testing with the bonnyci fork of zuul for github support (as zuulv3 is not recommended for production usage) and it seems like it might be something unrelated to github and a limitation of zuulv212:35
electrofelixif you have two pipelines with the same trigger definition but different status reporting sections, and create two project definitions and assign each to one of the two pipelines12:36
electrofelixwhen an event occurs it appears that both pipelines receive the event and attempt to report the status instead of only the pipeline of the project the event should have been associated with12:36
*** amoralej is now known as amoralej|lunch12:43
electrofelixI recognize that having two pipelines receive the same event but for different projects is probably an edge case12:46
electrofelixbut it seems useful to be able to add a test pipeline with updated settings for a single project before updating all other projects with the same setting change12:46
*** jkilpatr has quit IRC12:49
tobiashelectrofelix: for the v2 branch I had a similar problem which is fixed by https://review.openstack.org/#/c/334378/13:00
tobiashelectrofelix: you coult try that patch in your environment and see if it helps (not sure if it's the same root cause)13:00
*** jkilpatr has joined #zuul13:05
electrofelixtobiash: thanks, it should clean up my unit test if it does13:15
electrofelixtobiash: confirmed that is the fix13:21
*** openstackgerrit has joined #zuul13:24
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat github driver docs  https://review.openstack.org/49068813:24
*** amoralej|lunch is now known as amoralej13:24
*** xinliang has quit IRC13:27
pabelangermorning13:29
*** xinliang has joined #zuul13:40
*** xinliang has quit IRC13:40
*** xinliang has joined #zuul13:40
*** jkilpatr_ has joined #zuul13:41
*** jkilpatr has quit IRC13:42
tobiashelectrofelix: yay13:52
mordredelectrofelix: heya - I'd use v3, not that branch14:41
mordredelectrofelix: we're rolling v3 out for openstack in roughly 4 weeks - while it's possible we might still break one or two small things between now and then, those breaks will be WAY less of a migration than migrating from fork-of-v2 -> v314:43
pabelanger++14:47
mordredelectrofelix: that fork of v2 is _definitely_ not recommeneded for production at all and we're close enough to prime time that bug reports on v3 or finding issues either in the code or the docs is massively helpful14:49
electrofelixmordred: unfortunately I expect we're committed to being stuck on it for a few more weeks at least, though it sounds like we might be ready to migrate to the v3 branch around the same time it goes live14:51
*** jasondotstar has quit IRC15:03
tobiashmordred: what are the plans for the master branch once zuulv3 is released?15:10
tobiashmordred: asking because I still have some patches for master around and thinking if I should abandon these or keep them for some eventually to be created v2-legacy branch15:11
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Support longer pkcs1-oaep secrets  https://review.openstack.org/49062015:12
jeblairtobiash: our plans are to merge v3 into master; we don't intend to maintain v2 after v3 is released15:14
jeblairtobiash: (i expect the actual v3 release will come from the master branch)15:14
tobiashjeblair: that's clear and I also don't expect to maintain v215:15
tobiashjeblair: so I'll just abandon these patches? (currently they're just visual noise on my dashboard)15:15
jeblairtobiash: unless they're critical bugfixes (especially ones that would still affect v3)15:16
tobiashjeblair: https://review.openstack.org/#/q/status:open+project:openstack-infra/zuul+branch:master+owner:%22Tobias+Henkel+%253Ctobias.henkel%2540bmw.de%253E%2215:17
tobiashnot really critical bugfixes15:17
tobiashI'll probably keep 482856 in case gerrit gets updated before zuul15:18
clarkbtobiash: I think we want to be able to point at that one and tell people to apply it locally if they need to talk to newer gerrit with old zuul (so keeping it open is good)15:20
jeblair++15:21
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Don't request empty nodesets  https://review.openstack.org/48724315:21
tobiashjeblair: what about 403559 (that is a bugfix for zuul-cloner)?15:22
tobiashthat's the last one missing in question15:22
jeblairtobiash: i'd personally rather focus on v3 and not take the (admittedly, very small) risk, but if anyone else wants to +3 it that's fine15:27
tobiashjeblair: ok, then I'll wait until monday and abandon it then if no one wants to +3 it :)15:28
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: DNM - testing base-test playbook  https://review.openstack.org/49094515:33
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat SMTP driver docs  https://review.openstack.org/49094715:37
pabelangerjeblair: mordred: going to restart zuul-executor to pickup new zuul.conf changes15:38
pabelangerI don't see a reload option ATM15:38
pabelangerYa, I am guessing we'll want a reconfigure_handler for zuul-executor too15:39
pabelangercan see about adding that today15:39
jeblairmordred: what do you want to do about the question in 488221?  I'd love to land that15:42
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat sql driver docs  https://review.openstack.org/49095015:44
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat timer driver docs  https://review.openstack.org/49095115:46
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat timer driver docs  https://review.openstack.org/49095115:47
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat zuul driver docs  https://review.openstack.org/49095315:49
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Fix job example and misspelling  https://review.openstack.org/49095515:56
Shrewsvery simple +3 for someone ^^^15:56
Shrewsthat 'image' to 'label' change had me scratching my head for a bit15:56
tobiashShrews: +3'd15:58
mordredjeblair: oh - sorry - I forgot about that ... one sec16:00
mordredjeblair: I think lets' just do 255 for now - it's a varchar field anyway so there's not a TON of importance in limiting it further16:00
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Update SQL reporter to store results  https://review.openstack.org/48822116:01
mordredjeblair: ^^16:01
jeblairmordred: cool16:03
jeblairtobiash: want to +3 that ^16:03
tobiashjeblair: nope16:05
Shrewsmordred: I'm experimenting with job configuration using shade (e.g., https://review.openstack.org/490948). Something weird happened with the log streaming. Here is what I captured from the websocket stream (http://paste.openstack.org/show/617553/), but what was reported to gerrit was "test-job finger://ze01.openstack.org/3e85265630c94203bb44829314950d45 : FAILURE in 32s" with no link to the log16:05
tobiashupgrade script seems not to fit to code now (16 bs 255 chars)16:05
jeblairtobiash: thanks :)16:06
jeblairmordred: ^16:06
* Shrews acting as the pre-PTG confused guinea pig16:06
tobiashjeblair: have a comment/question in 49095316:07
jeblairShrews: the issue is that job does not inherit from the base job, which is what is responsible for uploading logs16:07
Shrewsjeblair: ah! well that explains that16:07
jeblairShrews: next week i plan on working on story 200111016:07
jeblairShrews: which is to make base jobs both required and implicit16:08
jeblairShrews: so, if things go well with that, if you had written that job at the end of next week, it should have worked like you intended :)16:08
tobiashShrews: I encountered this error everytime I had an ansible error in a task such as undefined variable16:08
Shrewsjeblair: this is good info16:08
mordredtobiash: DOH16:08
jeblairShrews: (ie, if you omit 'parent', it will automatically default to 'parent: base' -- which is what you want to add to that to fix it today)16:08
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Update SQL reporter to store results  https://review.openstack.org/48822116:09
mordredtobiash: thank you for that catch16:09
Shrewsjeblair: that explains the log issue. still wondering why the command failed, but that helps. thx16:09
tobiashmordred: so now all 255 and +2 :)16:10
Shrewsi'm guessing 'tox' isn't installed since i bypass our std jobs16:10
mordredShrews: yes. tox isn't instlaled - and also the base job handles getting the source code over there16:11
jeblairShrews, mordred: yeah, that's a good reason for it not to work, but it's not a good reason for us not to see any output...16:11
mordredShrews: and also the cwd for the playbook is /home/zuul but the source code (once the base job copies it over) is in /home/zuul/src/git.openstack.org/openstack-infra/shade16:11
mordredShrews: aka "src/{{ zuul.project.canonical_name }}"16:12
mordredShrews: so for things you want to happen "in the source dir of the one project" - you need to add an args:\n  cwd: "src/{{ zuul.project.canonical_name }}" to the command16:13
Shrewsmordred: ah. i expect this to be a common issue16:13
mordredjeblair: ^^ I don't have an answer yet, but I feel like we may want to figure out a cantrip of some sort to make that easier for the simple case16:13
mordredShrews: yah.16:14
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Fix job example and misspelling  https://review.openstack.org/49095516:15
jeblairmordred: some ideas: a new variable so that's easier to type, or a new command module.16:15
Shrewsmordred: jeblair: ok, once i set parent, i get a better log: http://logs.openstack.org/48/490948/4/check/test-job/40d0d7e/job-output.txt.gz#_2017-08-04_16_12_21_81287316:15
jeblairmordred: are you troubled by the lack of output for the tox command error?16:15
pabelangerShrews: yay16:16
Shrewscurious that didn't show up in the previous run16:16
jeblairShrews: assuming you didn't change anything else, i note that the old run had "[Zuul] Log Stream did not terminate", but the new one had an actual error16:16
Shrewsjeblair: all i did was add the parent16:16
jeblairmordred, Shrews: could there be a race in the command output streaming?16:16
* Shrews apologizes if he's causing noise around this16:17
mordredjeblair: our base job starts the log streamer16:17
jeblairmordred: ah that would do it :)16:17
Shrewsah, yeah. requiring the base job seems even more important now  :)16:18
jeblairtest-job                                  ERROR No valid playbook found16:18
mordredI am still MILDLY concerned, as I thought our command module still put stdout/stderr into the stdout_lines in the result object16:18
jeblairneat ^ :)  had only seen that in tests up to this point.  :)16:19
mordredjeblair: neat!16:19
jeblairmordred: i thought you filtered that out for console display, and only included it in json now?16:19
jeblair(since it's presumably redundant when we actually have console streaming)16:19
pabelangermordred: jeblair: restarting ze01.o.o now that we have no running jobs16:19
pabelangerand started again16:21
Shrewsyay, it's working! thx all. sorry to distract16:24
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Use zuul.executor.work_root for add-build-sshkey  https://review.openstack.org/49096916:29
jeblairShrews: no problem!16:30
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat tenant config docs  https://review.openstack.org/49097016:30
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Update SQL reporter to store results  https://review.openstack.org/48822116:32
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove score attribute from sqlreporter config  https://review.openstack.org/49097216:39
jeblairmordred, tobiash: ^ oops we forgot something16:39
jeblairalso, that's our first reporter with no configuration whatsoever.  i think "foo: {}" is the best way to do that, but it's worth a second thought.16:39
tobiashjeblair: would just 'foo:' also work?16:44
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Remove configure-mirrors from unittests/pre  https://review.openstack.org/49097716:46
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat timer driver docs  https://review.openstack.org/49095116:46
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat sql driver docs  https://review.openstack.org/49095016:46
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat SMTP driver docs  https://review.openstack.org/49094716:46
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat tenant config docs  https://review.openstack.org/49097016:46
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat zuul driver docs  https://review.openstack.org/49095316:46
*** electrofelix has quit IRC16:47
jeblairtobiash: hrm i'll try16:47
tobiashjeblair: I think that should give you a dict key with none as value16:47
pabelangerjeblair: mordred: so, I think we might need to bikeshed over 490997 ^.  It raises another question, do we expect zuul operators to setup local site-variables to use playbooks / roles in zuul-jobs, and if so, we'll need to establish a namespace for such variables I believe16:48
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use null values instead of the empty dict for sql reporter  https://review.openstack.org/49097816:49
jeblairtobiash: yes i think you're correct ^ that's a followup change that does that16:49
jeblairtobiash: i guess that's a little more ansible like from what i've seen16:49
jeblairpabelanger: yes i think we do expect zuul ops to set up local site vars for zuul-jobs16:50
jeblairpabelanger: and i think you mean 49097716:50
tobiashjeblair: yay16:50
pabelanger490977 yes16:51
jeblairtobiash: (i think you could also write "foo: null" with that change if you were so inclined)16:51
tobiashyes that should be the smae16:51
tobiashs/smae/same16:51
pabelangerjeblair: mordred: tobiash: do you mind adding https://review.openstack.org/#/c/490643/ to your review queue. Creates fetch-tox-output role that we can use from project-config17:00
tobiashpabelanger: lgtm17:03
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: DNM: test task with undefined variable  https://review.openstack.org/49098717:07
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: DNM: test task with undefined variable  https://review.openstack.org/49098717:09
tobiashthere is a delay of 30s if a shell/command task fails with an ansible error like undefined variable: http://paste.openstack.org/show/617555/17:12
pabelangertobiash: not sure I understand17:18
pabelangerisn't that expected, since you added a sleep?17:18
tobiashpabelanger: not the sleep task (that was just to give me time to open the live log)17:18
tobiashpabelanger: when ansible bails out because of undefined variable the callback module waits on the streamer for 30s for a shell task that was never executed17:19
pabelanger[Zuul] Log Stream did not terminate17:19
pabelangerwonder if that is related some how17:20
tobiashjepp, that's related17:20
tobiashthat is emitted after waiting for 30s for the streamer to end17:20
pabelangerIIRC, we still need to properly debug that17:20
pabelangercool, didn't know that17:20
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: DNM: test task with exit 1  https://review.openstack.org/49098717:23
*** openstack has joined #zuul17:31
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat timer driver docs  https://review.openstack.org/49095117:31
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat sql driver docs  https://review.openstack.org/49095017:31
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat SMTP driver docs  https://review.openstack.org/49094717:31
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use null values instead of the empty dict for sql reporter  https://review.openstack.org/49097817:31
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat tenant config docs  https://review.openstack.org/49097017:31
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat zuul driver docs  https://review.openstack.org/49095317:31
jeblairtobiash, pabelanger: i think mordred mentioned that may be happening on shell tasks that don't emit any output17:32
tobiashthat's with a 'exit 1' task: http://paste.openstack.org/show/617557/17:33
tobiashthat returns immediatly17:33
tobiashso maybe this occurs if the shell was not started at all17:34
tobiashbut I don't understand zuul_console yet17:34
ShrewsAnyone know if it is possible to have sphinx docs link to a directory and list the files there?17:37
tobiashjeblair, pabelanger: I think I found the reason: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/ansible/library/zuul_console.py?h=feature/zuulv3#n18517:44
tobiashif it fails to open the console file (and it will never exist) it gets into an endless loop trying to open it17:44
tobiashso we should probably add some timeout here (or is the retry needed?)17:45
jeblairtobiash: i'm not sure, but it may be possible for us to start trying to stream the log before ansible actually runs a command which would create it (even under normal conditions)17:50
jeblairwhich i think is why that's written that way17:50
tobiashjeblair: so retry limit 10 (5s)?17:50
tobiashor more?17:50
jeblairtobiash: i'd prefer to think of a more reliable way to deal with it17:51
tobiashjeblair: ok, different idea, can we distinguish between ansible parse error and shell-script error in zuul_stream?17:52
tobiashhere: v2_runner_on_failed?17:52
jeblairtobiash: i don't know off the top of my head17:53
tobiashif yes, we could just kill the listener without timeout and leave the zuul_console as is17:53
tobiashjeblair: oh I think I was wrong, it seems to be on the reader side18:05
tobiashthere is data from the stream18:06
tobiashbut this is the only exit point of the reader: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/ansible/callback/zuul_stream.py?h=feature/zuulv3#n14318:06
tobiashwhich requires the command to be executed and returned some exit code18:07
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add project examples and doc references.  https://review.openstack.org/49100818:08
Shrewsjeblair: i'm prepared to bikeshed on the proposed change there ^^^ as a potential way forward for our docs18:08
Shrewsdoesn't add much yet18:09
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: reformat metrics docs  https://review.openstack.org/49101018:11
jeblairShrews: cool i'll take a look18:11
Shrewshttp://logs.openstack.org/08/491008/1/check/tox-docs/bc50199/html/user/config.html#job18:14
pabelangerShrews: we could totally run a gate job using the examples too, if we wanted18:16
pabelangerto make sure they are always up to date18:16
Shrewsthat'd be kinda cool18:16
Shrewsbut, they'd probably have to remain openstack specific in that case. was trying to avoid that18:17
jeblairi'm kind of leaning the other way.  there are certainly some nice things you get from having external examples, but i think it makes the documentation a little more difficult to write and maintain.  for example it would be very easy for the highlighted lines to get out of sync.18:18
jeblairShrews: would it be okay to just inline those examples?18:18
jeblairalso, sorry i have to run real quick.  biab.18:19
Shrewsjeblair: we could, but then we'd have to keep the doc and source files in sync. not sure what doing that buys us18:19
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: DNM: test task with exit 1  https://review.openstack.org/49098718:23
*** adam_g has quit IRC18:24
*** adam_g has joined #zuul18:25
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Add project examples and doc references.  https://review.openstack.org/49100818:26
*** openstack has joined #zuul18:30
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: DNM: test task with empty command  https://review.openstack.org/49098718:31
jeblairShrews: back.  what do you mean doc and source files in sync?  i just meant put the contents of those example files directly into code-blocks in the rst files18:42
Shrewsjeblair: My thought was that having a directory of different types of examples (I sort of inferred that you wanted something like this yesterday)? would be useful, even without the documentation.18:44
jeblairShrews: oh, hrm.  i only meant within the docs themselves.18:44
Shrewsjeblair: I sort of like when projects include full examples that I can browse, independently of the docs18:44
jeblairShrews: yes, that can be nice; though i'm not sure some of the same reasons apply here -- for instance, folks are very unlikely to be able to copy an example and start using it.18:46
jeblairwhereas i think it will be very difficult to write and maintain the docs with all of the examples being external.18:48
Shrewsjeblair: how so?18:50
jeblairShrews: if a line is every added to one of those example files, the docs would need to be updated to change the line emphasis.  but there's no indication that the examples directory is used by the docs.  it seems quite likely that a change like that could slip through.18:51
Shrewswe could mitigate some of that by moving the examples under the doc/ structure (i had it there originally, actually)18:52
Shrewsbut yeah, we'd have to be alert for highlight changes18:52
jeblairShrews: moreover, any text that you write that refers to the examples means that you need to go look at probably several example files in order to make references (as opposed to just being able to look up a couple of paragraphs in the same file)18:53
jeblairShrews: (put another way -- i *had* to render the docs in order to understand them, which is not something i'm used to.  that extra effort reviewing is also extra effort writing.)18:54
Shrewsok, sounds like you're a strong "no" on this approach. i can just inline it18:54
Shrewsno biggie  :)18:54
jeblairShrews: i wouldn't characterize it as a strong no, or at least not permanently so.  more that i'm concerned we don't have the discipline for it at the moment.  i think i'd like to revisit it later.18:57
jeblairShrews: (and yeah, if we do revisit this, i think having it under the doc tree helps with that, and also with grepping)18:59
jeblairShrews: regarding the content itself -- do you want to mention the project stanza under the job section? -- because we haven't gotten to 'project' yet in the narrative.  what about putting the complete example under 'configuration items' then excerpting parts of it under the relevant items (so maybe job+playbook under job, then job+project under project)?19:07
Shrewsjeblair: i'm not sure now. i want to rethink the approach, so just ignore what i have up right now.19:11
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Try to early terminate streaming on ansible errors  https://review.openstack.org/49102719:12
jeblairShrews: okiedokie19:12
tobiashjeblair, pabelanger: what do you think of ^^^ for fixing the 'stream did not terminate' problem?19:13
jeblairtobiash: i think that's a question for mordred too ^19:13
tobiashoh, sure, sorry mordred19:14
tobiashthat's the best I could come up after digging more than I wanted into the command ansible module19:14
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Support longer pkcs1-oaep secrets  https://review.openstack.org/49062020:05
pabelangeryay20:06
*** jkilpatr_ has quit IRC20:41
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: change default title for value xref  https://review.openstack.org/49109120:55
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: enable show_related  https://review.openstack.org/49109721:15
pabelangerjeblair: just walked the stack of doc changes, looking really good!21:26
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Remove score attribute from sqlreporter config  https://review.openstack.org/49097221:29
*** jkilpatr_ has joined #zuul21:29
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat SMTP driver docs  https://review.openstack.org/49094721:33
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: add very simple architecture diagram  https://review.openstack.org/49110021:46
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat sql driver docs  https://review.openstack.org/49095022:23
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: DNM - testing base-test  https://review.openstack.org/49111022:26
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: DNM - testing base-test  https://review.openstack.org/49111022:27
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Docs: add very simple architecture diagram  https://review.openstack.org/49110022:41
openstackgerritJames E. Blair proposed openstack-infra/zuul-sphinx master: Add setup to module import  https://review.openstack.org/49112823:02
mordredtobiash, jeblair: yes - that approach looks good to me23:05
mordredjeblair: also, I agree with pabelanger - the docs stack is amazing23:06
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add zuul-sphinx as a requirement  https://review.openstack.org/49112923:07
jeblairpabelanger, mordred: oh cool, thanks :)23:07
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat timer driver docs  https://review.openstack.org/49095123:13
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat zuul driver docs  https://review.openstack.org/49095323:14
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat tenant config docs  https://review.openstack.org/49097023:14
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Use null values instead of the empty dict for sql reporter  https://review.openstack.org/49097823:15
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: reformat metrics docs  https://review.openstack.org/49101023:15
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Docs: change default title for value xref  https://review.openstack.org/49109123:17
pabelangermordred: https://review.openstack.org/490643/ is ready for a review, created new fetch-tox-output role. We'll need that for our publish-openstack-python-tarball job23:21
openstackgerritJames E. Blair proposed openstack-infra/zuul-sphinx master: Change usage from zuul_sphinx.zuul to zuul_sphinx  https://review.openstack.org/49113123:22
openstackgerritMerged openstack-infra/zuul-sphinx master: Add setup to module import  https://review.openstack.org/49112823:22
jeblair491131 is trivial; i'm going to self-approve it and make a release23:29
mordredjeblair: ++23:30
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Set success-url for tox-docs job  https://review.openstack.org/49113223:34
openstackgerritMerged openstack-infra/zuul-sphinx master: Change usage from zuul_sphinx.zuul to zuul_sphinx  https://review.openstack.org/49113123:34
jeblairpushed zuul-sphinx 0.1.323:35
jeblairpabelanger: nit on that, but should work23:36
pabelangerjeblair: ya, thanks.23:36
pabelangerjeblair: I am trying to decided if we want it setup in zuul-jobs or openstack-zuul-jobs.  I'm leaning towards openstack-zuul-jobs, because we have openstack-docs-build running on zuul ATM23:37
pabelangerbut, maybe zuul-jobs is the right place23:37
pabelangersince tox-docs is the parent23:37
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Set success-url for tox-docs job  https://review.openstack.org/49113223:38
pabelangerokay, sold my self on zuul-jobs23:38
jeblairpabelanger: yeah, it's an open question in my mind.  :)  it will affect us either way because it will be inherited.23:39
pabelangerya, lets go with zuul-jobs for now.23:39
clarkbis the success url implicitly relative to the logs location?23:39
clarkbif so I think that is slight departure in behavior where we currently publish that stuff to docs-draft.openstack.org on a different "disk" than logs.openstack.org23:40
jeblairclarkb: i have good news for you!  it's both!  https://docs.openstack.org/infra/zuul/feature/zuulv3/user/config.html#attr-job.success-url23:40
pabelangerclarkb: ya, docs-draft.o.o is something we still need to do23:41
jeblairclarkb: it's relative if it's a relative url, or, make an absolute url and it takes over23:41
clarkbah ok23:41
clarkbthe biggest reason to have separate disks for that is variable retention policy though I think its 30 days for both right now :/23:41
jeblairclarkb, pabelanger: however, it's likely that we'll probably just do something parallel for docs draft -- since in that case we can let the ansible publisher tell us where it put things.  so i expect at least the base part of the docs-draft url to come from ansible just like the current stuff.23:42
pabelangerya23:42
jeblairclarkb: maybe we should consider folding it back in.  would get an extra TB of space.  :|23:43
jeblairi'm guessing docs builds aren't as big as they used to be23:44
clarkbjeblair: worth considering. We can also likely consider bumping logs retention back up again23:44
clarkbwe've got it under control now I think23:44
clarkbjeblair: because no more docbook?23:44
jeblairclarkb: that's my assumption, yes.23:45
pabelangerya, logs.o.o looks to be at 9TB ATM23:45
clarkbfungi: what was your process of determining largest jobs?23:45
clarkbfungi: du -s on a change number prefix then sorting by job name?23:46
jeblairnah, i'm wrong.  there hasn't really been a systemic change in doc-draft usage over the past year.23:46
fungiclarkb: great question! lemme see if i can dig up my notes but it was something along those lines23:46
jeblairjust normal looking cycles.23:46
clarkbfungi: we might want to rerun that and tackle the next things on the list23:46
clarkbjeblair: dedup would probably help significantly on that fs23:46
jeblairclarkb: indeed23:46
fungitook somewhere between 24-48 hours to complete across the entire corpus, if memory serves23:47
clarkbwe could live dangerously and use btrfs23:47
clarkbbut red hat just announced its too dangerous for them so maybe not23:47
clarkb(which is slightly funny bceause xfs)23:48
jeblairplease not the btrfs.  i did that once it was not fun.23:48
mordredif jeblair doesn't behave we will subject him to the btrfs23:48
pabelangermaybe discuss at PTG about hashing my date for logs now?23:48
pabelangerI mean, we could start testing with zuulv3.o.o now23:48
jeblairmordred: not the comfyfs!23:48
clarkbI've been using it because it is suse default and its been fine. But I expect on older kernels its much sadness23:49
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Update the zuul-sphinx extension config  https://review.openstack.org/49113423:50
clarkbone thing that would be neat is fs scrubbing on merge23:50
clarkbits late on friday so we can talk about neat features that will never happen right?23:50
clarkbchange merges, its doc drafts are all deleted23:50
jeblairclarkb: that's totally plausible in zuulv3 :)23:50
clarkbya, I worry more about iops overload23:51
jeblairzero-node job in a change-merged pipeline with like 1 line of ansible :)23:51
fungifor i in `seq 20`;do du -sk /srv/static/logs/`echo $RANDOM|cut -c-2`/??????/*/*/* >> du_sample.txt;done23:51
clarkb(delete cron is laready a 2 day process iirc)23:51
fungifor j in `cut -d/ -f9 du_sample.txt|sort -u`;do echo $[$(grep /$j$ du_sample.txt|cut -f1|sed s/^/+/)] $j;done|sort -n|tail -n100>summary.txt;echo $[$(cut -f1 du_sample.txt |sed s/^/+/)] total kilobytes>>summary.txt23:51
clarkbjeblair: but we can give it a go and stop if the filesystem falls over23:51
jeblairclarkb: should give the delete cron much less work to do, so may be a wash as far as io23:52
jeblairbasically, it's zero-sum io :)23:52
clarkbjeblair: ya distribute it over time too rather than all at once23:52
jeblairi feel like someone should give fungi some output.  even if it's just a spinning cursor.23:53
clarkbthats quite the script23:53
clarkbfungi: if you haven't already done it I'll start the first command in a screen23:53
fungiclarkb: go for it. that'll take overnight probably23:54
clarkbfungi: does it need to run as root?23:54
fungithen once it's done (or really at any point along the way for that matter) you can run the other in another session to get preliminary analysis fairly quickly23:54
fungiyeah, i ran it under the root account23:54
fungiin part because it's easier for others to attach to a screen session started as root23:55
clarkbwe serve logs under different account than we write them so they should be all readable but guessing there are corner cases where taht assumption is false23:55
fungiwell, also root gets some priority scheduling, if my arcane knowledge of niceness levels is still applicable in this day and age23:55
clarkbok thats running and I'm tailing the sample file in window 123:56
fungiattached23:57
clarkbfungi must hate attaching to screens I've started23:57
clarkbwith my full screen terminals23:57
fungiif we used tmux it would just instantly resize its geometry to accommodate me ;)23:58
fungithat's one of the things i find impressive about tmux is that it scales columns and rows to whatever the least common denominator of attached sessions is23:59

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