Thursday, 2018-02-08

mordredclarkb, corvus: 541939 is green on build-sphinx-docs - should we add a depends-on or rebase the corvus stack on that patch?00:04
*** elyezer has quit IRC00:17
*** elyezer has joined #zuul00:17
*** elyezer has quit IRC00:31
openstackgerritMerged openstack-infra/nodepool master: Update tox docs environment to match build-sphinx-docs  https://review.openstack.org/54193900:31
*** elyezer has joined #zuul00:35
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Infer python2 vs. python3 for sphinx jobs  https://review.openstack.org/54195200:39
jheskethcorvus: do you have a moment to chat about the update_queue (nothing urgent)00:45
corvusjhesketh: yep00:46
jheskethcancelling the queue on 'stop' (from my reading) shouldn't have any bad affects as the jobs are all being stopped (it might require a bit of extra error handling, but nothing difficult).00:47
jheskeththe challenge is with the updates requested as part of the merger that's included with the executor00:47
jheskethgiven that they only enqueue when there is no other work, it's a bit of an edge case00:48
jheskethbut if we do shutdown in the middle of an update that work we may give the scheduler/configure an error00:49
jheskethone way to handle it woudl be to just shut it down and have the merger client understand how to recognise a request has failed because of a disconnect rather than being something such as unable to merge00:49
jheskeththis could be helpful as what we're trying to smooth out is network errors. This would mean the merger client (and hence scheduler) can handle disconnects from any of the merger processes00:50
jheskethso should be need to restart a merger server we can as well00:50
corvusyeah, i think that would be ideal for general robustness anyway (and in the future, we may want to retry merge jobs in response to some errors, so that will give us a framework for that00:51
corvusthat's probably a bit more work though00:52
jheskethright, that was my thinking00:52
jheskethcorvus: so I'm not sure it is too bad. We can modify MergeGearmanClient.handleDisconnect to re-submit the job X times00:53
jheskethactually handleDisconnect is for when the gearman client can't talk to the gearman server, so that won't solve this issue, but will still help00:53
jheskethhandleWorkFail is probably what we need00:54
corvusjhesketh: yeah00:54
jheskethand maybe handleWorkException, but if a worker is causing exceptions because of a malformed job we don't really want to send that job elsewhere00:54
corvusjhesketh: if you want to start down that path and see if it heads down a rabbit hole, that seems like a good idea -- i think it's the ideal solution00:54
jheskethyep, will do :-)00:55
corvusjhesketh: and if it's too complicated, we can work out how to compromise in the executor for now00:55
corvusjhesketh: maybe handle exception the same way?  could be out of disk space or something...?00:55
jheskethcorvus: can you confirm for me (if you know) that on merge failure etc the gearman worker still sends a WorkComplete with the error described in the result?00:55
corvusjhesketh: i can't confirm off the top of my head, but if not, i think they should.  i think we've been moving things to that model (it makes a lot more sense because of things like this)00:56
jheskethcorvus: yeah, so long as we're limiting retries we should be okay... also want to avoid the case where a malformed job takes the worker offline completely (eg segfault) which will then slowly take out other workers00:56
corvusjhesketh: ++00:56
jheskethcorvus: yep, agreed. I think I made that mistake in early turbo-hipster versions where I thought WORK_FAIL was for failures in the job, but really it should be failures in the protocol00:57
jheskethso if I come across that we can look at fixing that too00:57
corvusjhesketh: a *really* quick look suggests that the merger behaves the way we want, but it's worth keeping an eye out00:57
jheskethyep, that was my observation too00:58
corvusjhesketh: (ie, a grep for workFail returns only one obvious result)00:58
jheskethcool, I'll get on with that then. Thanks for your time :-)00:58
corvusjhesketh: thank you!00:58
*** dkranz has quit IRC01:25
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Add /label-list to the webapp  https://review.openstack.org/53556301:43
*** elyezer has quit IRC02:57
*** elyezer has joined #zuul03:02
*** bhavik1 has joined #zuul04:12
*** bhavik1 has quit IRC04:39
*** elyezer has quit IRC05:22
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: zk: use kazoo retry facilities  https://review.openstack.org/53553705:24
*** elyezer has joined #zuul05:25
tristanCShrews: last PS of 535537 should correctly handle sequence creation error, and there is a test for it05:27
*** threestrands has quit IRC05:57
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Allow Ansible 2.4  https://review.openstack.org/53578106:28
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Disable action and lookup plugins from 2.4  https://review.openstack.org/53583906:28
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584006:28
*** elyezer has quit IRC06:29
*** elyezer has joined #zuul06:31
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584006:41
*** sshnaidm|afk has quit IRC07:00
*** sshnaidm|afk has joined #zuul07:04
*** xinliang has joined #zuul07:16
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584007:21
*** elyezer has quit IRC07:26
*** elyezer has joined #zuul07:28
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584007:36
*** elyezer has quit IRC07:37
*** elyezer has joined #zuul07:40
*** sshnaidm|afk has quit IRC08:03
*** jpena|off is now known as jpena08:11
*** maxamillion has quit IRC08:17
*** sshnaidm|afk has joined #zuul08:17
*** mnaser has quit IRC08:17
*** kmalloc has quit IRC08:17
*** maxamillion has joined #zuul08:17
*** mnaser has joined #zuul08:18
*** kmalloc has joined #zuul08:18
*** robcresswell has quit IRC08:18
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584008:18
*** sshnaidm|afk is now known as sshnaidm08:26
*** elyezer has quit IRC08:35
*** elyezer has joined #zuul08:41
*** robcresswell has joined #zuul08:49
*** elyezer has quit IRC08:58
*** elyezer has joined #zuul09:08
openstackgerritMatthieu Huin proposed openstack-infra/nodepool master: Clean held nodes automatically after configurable timeout  https://review.openstack.org/53629509:18
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584009:29
*** hashar has joined #zuul09:44
*** hashar has joined #zuul09:44
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584009:51
openstackgerritMatthieu Huin proposed openstack-infra/nodepool master: Clean held nodes automatically after configurable timeout  https://review.openstack.org/53629509:57
*** hashar has quit IRC09:57
*** hashar has joined #zuul09:59
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584010:19
*** jpena is now known as jpena|away10:59
openstackgerritAndrea Frittoli proposed openstack-infra/zuul-jobs master: Change the list of extensions to a dict  https://review.openstack.org/54048511:07
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584011:12
*** hashar has quit IRC11:17
openstackgerritMatthieu Huin proposed openstack-infra/nodepool master: Clean held nodes automatically after configurable timeout  https://review.openstack.org/53629511:17
*** hashar has joined #zuul11:22
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul autohold: allow operator to specify nodes TTL  https://review.openstack.org/53959611:22
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: test functional stream  https://review.openstack.org/54213811:23
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584011:29
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584011:39
*** elyezer has quit IRC11:45
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: test functional stream  https://review.openstack.org/54213811:49
*** elyezer has joined #zuul11:51
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584012:15
*** elyezer has quit IRC12:40
*** elyezer has joined #zuul12:49
*** jpena|away is now known as jpena|off12:52
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584012:57
openstackgerritMarkus Hosch proposed openstack-infra/zuul master: Extend stackdump to display the daemonize status  https://review.openstack.org/54215812:57
openstackgerritMarkus Hosch proposed openstack-infra/zuul master: Cleanly shutdown zuul scheduler if startup fails  https://review.openstack.org/54215912:58
openstackgerritMarkus Hosch proposed openstack-infra/zuul master: Add --check-config option to zuul scheduler  https://review.openstack.org/54216012:58
*** jpena|off is now known as jpena13:06
*** maho has joined #zuul13:09
*** Wei_Liu has quit IRC13:15
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584013:21
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54218213:41
*** Wei_Liu has joined #zuul13:47
tobiashsorry for spamming, trying to get that thing to run ^13:49
*** sshnaidm is now known as sshnaidm|rover13:50
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54218214:04
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Run zuul-stream-functional on every change to ansible  https://review.openstack.org/54220314:07
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Run zuul-stream-functional on every change to ansible  https://review.openstack.org/54220314:10
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Allow Ansible 2.4  https://review.openstack.org/53578114:18
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Disable action and lookup plugins from 2.4  https://review.openstack.org/53583914:18
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584014:18
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54218214:18
*** maxamillion has quit IRC14:21
*** maxamillion has joined #zuul14:21
kklimondaSpamapS: let me see if I can find some time today and tomorrow to fix those last comments - I've been running with this patch for some time and that obviously has made me less anxious to get it into mainline :/14:34
SpamapSkklimonda: yeah I am trying not to cherry-pick too much and run mostly off mainline (except the slack reporter which I made ;-)14:36
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Infer python2 vs. python3 for sphinx jobs  https://review.openstack.org/54195214:37
kklimondasigh, I'm 100 commits behind mainline I think14:37
SpamapSYeah I haven't rebased in a while.14:38
*** dkranz has joined #zuul14:38
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Fix builds queued forever after failure to get node request  https://review.openstack.org/53733514:44
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Port in changes from ansible 2.4 command module  https://review.openstack.org/53584014:53
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54218214:53
tobiashmordred: I think this works now except the log of a debug task with var ^14:55
tobiashcurrently a bit stuck there14:55
tobiashmordred: you handle the debug task there right?14:56
tobiashhttp://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/ansible/callback/zuul_stream.py#n37714:56
mordredtobiash: yes- and we use debug tasks in jobs so we know they work14:57
tobiashwith ansible 2.4 the debug task with var has no msg anymore (did it have one in the past?) in the result dict14:57
tobiashmordred: that's the result dict for debug with var and ansible 2.4: http://logs.openstack.org/82/542182/2/check/zuul-stream-functional/5c1325e/job-output.txt.gz#_2018-02-08_14_15_08_05117214:59
tobiashnot that nice to filter14:59
mordredtobiash: OH - I get what you're saying now15:00
tobiashhrm, that should take care of dumping everything rught?15:02
tobiashhttp://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/ansible/callback/zuul_stream.py#n38715:02
mordredtobiash: so - the logic for debug with a var is (or needs to be), I think - remove any keys that start with _ansible - remove 'changed' - anything left is a debug var to print - but I'm not sure how we detect that - so maybe it has to be a final condition?15:03
tobiashmordred: maybe with result._task.action not in ('debug') ?15:03
tobiashwill try that15:03
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54218215:07
tobiashyeah, I think just the detection if a debug task fails15:07
*** Wei_Liu has quit IRC15:08
dmsimardcorvus: I suppose the executors need to be restarted to pick up the new statsd counters ? Don't see them in graphite yet.15:21
corvusdmsimard: yep15:22
dmsimardokay, there's no rush so I'll just wait until we need to restart them for something. Thanks.15:23
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54218215:23
*** maho has quit IRC15:31
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Handle debug tasks more robust in zuul_stream  https://review.openstack.org/54218215:34
*** elyezer has quit IRC15:35
*** elyezer has joined #zuul15:36
*** hashar is now known as hasharAway15:38
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Exit launchers and builders immediately  https://review.openstack.org/54193016:02
*** xinliang has quit IRC16:29
corvusSpamapS, clarkb: can you give https://review.openstack.org/540489 a look?16:45
*** openstackgerrit has quit IRC16:48
*** jimi|ansible has quit IRC16:51
*** openstackgerrit has joined #zuul16:58
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Exercise pidfile before daemonizing  https://review.openstack.org/54231516:58
*** markush1 has joined #zuul17:08
*** markush1 has quit IRC17:10
*** myoung is now known as myoung|biaf17:22
SpamapScorvus: looking17:42
SpamapScorvus: +1. :)17:43
*** myoung|biaf is now known as myoung17:46
corvusShrews, mhu: it looks like the nodepool webapp is still built in to the launcher -- should we split it out into its own process?17:47
corvustristanC: ^17:47
corvusalso, 'if not no_webapp' takes me back to grammar school.  :)17:48
pabelangerha17:48
SpamapSyou aint webapp. You waint nothin.17:52
mordredcorvus, mhu, Shrews, tristanC: I was also thinking yesterday from looking at the nodepool webapp patches that perhaps we should migrate nodepool's web stuff from webob to aiohttp so that the two codebases are more similar17:57
corvusmordred: worth considering... though we also were talking about maybe just folding into zuul entirely17:58
mordredcorvus: that would also work18:00
openstackgerritMonty Taylor proposed openstack-infra/zuul master: WIP Rework log streaming to use python logging  https://review.openstack.org/54143418:00
corvusi brought it up now mostly in case we think we need to do something urgently before the v3.0 release18:00
corvusbut as i think about it -- launchers running webapps is actually probably fine18:01
corvuslike, it's a little weird, but there's probably nothing structurally wrong about it that we need to deal with before release... i think?18:01
corvuswe don't seem to be exposing them in openstack though, so it's hard for me to say for sure18:02
mordredcorvus: I dunno - webapps being on launchers will make it harder to incorporate node information into a dashboard - since something would have to somehow be aware of the launchers to be able to make the queries18:02
*** myoung is now known as myoung|food18:02
corvusmordred: oh yes absolutely -- i'm just trying to find the right thing for the 3.0 release here -- i don't think we have to, or want to, commit to this long-term, because you're right, it's hard to design around.  but it's also probably not completely broken.18:03
corvusmaybe we should just put a note in the docs indicating that the current nodepool webapp is likely to change in subsequent releasese.18:04
mordredyah18:04
mordredcorvus, Shrews, tobiash: the https://review.openstack.org/541434 above shifts the stream receiver into the callback plugin - the plumbing all works to get the port created by ssh and passing the info to the command module - but I'm not getting any hits on the receiver's handler method18:06
mordredoh! nope. I lied - I did something and the port forward isn't getting applied ...18:07
tobiashcorvus: +1 for a note and later making it zuul-web like18:09
*** elyezer has quit IRC18:09
*** elyezer has joined #zuul18:10
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Resolve paths before demonization  https://review.openstack.org/54235318:11
*** jpena is now known as jpena|off18:13
*** jimi|ansible has joined #zuul18:15
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Exit launchers and builders immediately  https://review.openstack.org/54193018:15
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Exercise pidfile before daemonizing  https://review.openstack.org/54231518:15
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Resolve paths before demonization  https://review.openstack.org/54235318:15
corvusoh right, Shrews is afk starting today18:16
tobiashcorvus: I'll be on vacation next week18:19
corvustobiash: thanks, enjoy!18:19
tobiash:)18:20
openstackgerritKrzysztof Klimonda proposed openstack-infra/zuul master: Support autoholding nodes for specific changes/refs  https://review.openstack.org/54003518:21
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54236018:25
openstackgerritKrzysztof Klimonda proposed openstack-infra/zuul master: Support autoholding nodes for specific changes/refs  https://review.openstack.org/54003518:26
tobiashmordred: looks like you're also fighting hard with log streaming18:31
mordredtobiash: yah - although hopefully in a different part18:32
tobiashchecking18:33
tobiashmordred: there will be some conflicts in zuul/ansible/library/command.py but I think they'll be easy to resolve18:34
mordredWOOT! I got it working!!!!18:36
mordredturns out hte issue was my continual inability to understand ssh -R port:host:port syntax18:36
tobiashthat's a thing I have to look up in the manpage everytime I use it ;)18:38
mordredme too - and I STILL get it wrong half the time :)18:39
tobiashhrm, the round trip times are getting longer now18:39
*** myoung|food is now known as myoung18:43
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Fix builds queued forever after failure to get node request  https://review.openstack.org/53733518:44
openstackgerritAndrea Frittoli proposed openstack-infra/zuul-jobs master: Change the list of extensions to a dict  https://review.openstack.org/54048518:52
*** sshnaidm|rover is now known as sshnaidm|off18:52
tobiashmordred: yay, https://review.openstack.org/#/c/542182/ fixes the debug task for ansible 2.4 while being still compatible to 2.3 :)18:56
*** sshnaidm|off has quit IRC18:57
tobiashso one step further, now binary output is broken with 2.4...18:59
mordredtobiash: woot!19:15
*** elyezer has quit IRC19:19
*** elyezer has joined #zuul19:24
*** zaro_ has quit IRC19:26
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54236019:28
*** zaro_ has joined #zuul19:29
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54236019:43
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54236019:47
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Store build logs automatically  https://review.openstack.org/54238619:55
rcarrillocruzcorvus, mordred : sorry, just reading scrollback. So for 3.0, one webapp per launcher, but intent is in the future to decouple it so we can reach out just one webapp which potentailly gives aggregate info from nodepool?19:59
corvusrcarrillocruz: i *think* currently each launcher-webapp should give you all the info.20:00
corvusbut otherwise, yes, i think that's probably what will happen, in some form.20:00
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54236020:00
rcarrillocruzah, so webapp is just a passthru to zookeeper, ergo doesn't matter which webapp endpoint you reach20:00
rcarrillocruzis that accurate?20:00
rcarrillocruzfrom info you can grab i mean20:01
corvusthat's my understanding.  i can't confirm that since i don't think we currently expose that in openstack-infra20:01
rcarrillocruzk thx20:01
tobiashcorvus: I can confirm that it just iterates over zk20:02
tobiashit's primitive compared to zuul-web but it works :)20:02
mordredcorvus: you know - we could jus keep it as one-webapp-per-launcher and just deal with it being a usable endpoint with a load balancer - since each launcher is a stateless http thing20:04
corvusmordred: that's an option too20:06
rcarrillocruzso folks, was thinking the other day, we have a vendor where they use openstack for their CI. So I thought 'oh nice, let's suggest him using zuul/nodepool'. The guy said that he knows nodepool , but he prefers using heat for doing on test trigger provisioning, as their IT team is not happy having nodepool keeping a $min-nodes quota used. Is it possible to set up nodepool to create nodes on demand, by having 020:06
rcarrillocruzmin-ready ? I think not, but you know better than me20:06
mordredrcarrillocruz: yes20:07
mordredrcarrillocruz: it's very possible20:07
rcarrillocruzi thought setting min-ready 0 meant disabling that node type ?20:07
mordredrcarrillocruz: that's -120:08
tobiashrcarrillocruz: min-ready was a problem in v2 world, with nodepool/zuulv3 that's absolutely no problem20:08
mordredrcarrillocruz: https://docs.openstack.org/infra/nodepool/configuration.html#labels20:08
rcarrillocruzLOL20:08
rcarrillocruzo-k20:08
rcarrillocruzthat's it, i had that assumption from the old days20:08
rcarrillocruzgeez20:08
rcarrillocruzso this week i learned:20:08
rcarrillocruzyou can set up nodepool to be complete private, by setting auto-floating-ips: False in provider plus default-interface: False in clouds.yaml20:09
rcarrillocruzand nodepool being able to create nodes in demand , by having 0 nodes per type20:09
rcarrillocruzlove this community20:09
mordred\o/20:09
rcarrillocruzTHANKS!20:09
* rcarrillocruz goes hack20:09
tobiashand with easy crontab scripting you even can change min-ready depending on office hours20:10
rcarrillocruztobiash: yeah, that's kind of the tihng i have in place (we have just-nodepool + DCI for our current CI), but the fact we CAN have zero nodes per label...OMG!20:10
corvusi think we should get rid of all the -1 things20:11
corvusthey shouldn't be necessary anymore, and they are confusing20:11
corvus(i don't tell anyone to use them anymore)20:12
corvusif you want to remove a label, just remove the label now20:12
rcarrillocruzaye, cos you have this dual meaning of -1 plus simply removing the label to 'disable this label'20:12
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Default min-ready to 0  https://review.openstack.org/54241020:13
openstackgerritTobias Henkel proposed openstack-infra/zuul master: DNM: fix streaming tests  https://review.openstack.org/54236020:24
pabelangerspeaking of min-ready and nodepool, https://review.openstack.org/540916/ would be good to get a few eyes on. Adds tests for multiple launchers and min-ready nodes20:26
*** jimi|ansible has quit IRC20:30
tobiashpabelanger: was that meant for going in now or as a base for starting to work on multi launcher races?20:32
pabelangertobiash: yah, mostly want to make sure everybody is aware how it works, before starting rework.  However, I am still trying to come up with solution to this.20:35
pabelangeractually, let me test something20:37
tobiashmordred: geez, I broke the binary data test with my additional debugging output...20:37
pabelangertobiash: another workaround, is to remove min-ready from all but 1 nodepool-launcher.yaml file.  It then will ensure specific providers / labels will be launched. No the best, but a way to deal with it until we figure out how to share config between launchers20:44
tobiashyeah, that's a possible workaround20:46
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Update to Ansible 2.4  https://review.openstack.org/53578120:47
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Disable action and lookup plugins from 2.4  https://review.openstack.org/53583920:47
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Add unit test for multiple launchers  https://review.openstack.org/54091620:49
pabelangertobiash: ^20:49
tobiashpabelanger: so this is two launchers, two clouds, one label?20:52
pabelangertobiash: right20:52
tobiashnext difficulty level would be two launchers, one cloud, but that would also need coordinated quota handling20:53
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Store build logs automatically  https://review.openstack.org/54238620:54
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Default min-ready to 0  https://review.openstack.org/54241020:54
pabelangertobiash: yah, I'd love us to support that, but maybe 4.0? :)20:55
tobiashprobably20:56
*** jimi|ansible has joined #zuul20:57
*** ChanServ has quit IRC20:57
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Update to Ansible 2.4  https://review.openstack.org/53578121:06
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Disable action and lookup plugins from 2.4  https://review.openstack.org/53583921:06
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add doc for executor state_dir  https://review.openstack.org/54243021:08
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Make min_starting_builds a heuristic  https://review.openstack.org/54243121:08
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Rework log streaming to use python logging  https://review.openstack.org/54143421:18
mordredcorvus, tobiash: ^^ ok. that works now locally in synthetic tests21:19
mordredit also uses json instead of pickle21:20
mordredthere is one more engineering challenge to solve - which is how to deal with controlpersist21:20
mordred(we have one controlpersist per remote host, but we have more than one ansible-playbook invocatoin - so we need to make sure subsequent listeners use the same local port ...)21:21
corvusmordred: how about unix domain sockets?  does that solve that?21:23
corvusput the socket in the build dir, call it done?21:23
mordredcorvus: you know what - it sure does21:26
mordredcorvus: cause I was already thinking of essentially writing out a json map with remote-hostname+port in it21:26
corvus\o/ turns out you warn't just whistlin' dixie thar21:26
mordredbut if we just name the unix socket predictably with the hostname ...21:27
mordredI also think we MIGHT be able to get away with just one listener rather than one per remote host - now that I've got this all plubmed through21:27
tobiash\o/ the ansible 2.4 stack is working now https://review.openstack.org/#/q/topic:zuul-ansible-2.4+status:open21:28
tobiash:)21:28
mordredtobiash: woohoo!21:30
corvustobiash: cool... i'm thinking maybe we should land that shortly after the v3.0 release?21:30
*** ChanServ has joined #zuul21:30
*** barjavel.freenode.net sets mode: +o ChanServ21:30
tobiashcorvus: do we already have a target for a release date?21:31
corvusi'm still aiming for around the ptg, ideally shortly before, less ideally shortly after21:32
*** dkranz has quit IRC21:32
tobiashI have to switch to 2.4 asap as the windows modules are all broken in 2.3 and py321:32
tobiashbut I'm ok having this in my staging branch for a few weeks21:32
*** sshnaidm has joined #zuul21:32
corvusah.  my suggestion was predicated on the assumption that 2.3 is working with zuul "well enough" for us to make a release, since we've stabilized a bunch of stuff over many months; i'm open to merging it sooner if folks think that would be better.21:33
mordredcorvus: I think the only thing we were waiting on wrt 2.4 was the openstack queens release being done ...21:33
dmsimard2.4.3 has a few fixes we're interested in21:33
mordredcorvus: so I'd support landing 2.4 support and updating openstack to 2.4 once queens is done21:34
mordredbut I don't have strong feelings in either direction - mostly whatever works for other people21:34
corvusmordred: that's the same timeframe as ptg... so maybe the plan to relase on 2.3 then immediately update is still best?21:34
tobiashcorvus: that's ok for me21:34
tobiashhow about windows support?21:35
tobiashis that for 3.0 or shortly after?21:35
tobiashthere are some small patches for that lingering around21:35
mordreddmsimard: you might find  https://review.openstack.org/541434 interesting21:35
corvustobiash: i don't think it's on our 3.0 roadmap, so i don't think we'd block on windows support, but can merge things as time permits21:36
tobiashok21:37
dmsimardmordred: very nice. I'll have to check it out.21:41
dmsimardmordred: btw the nodepool static driver landed so I might try my hand at the nested zuul idea we talked about a while back -- to test stuff like that.21:42
SpamapScorvus: https://github.com/facebook/pyre2/commit/35e71e99ba8fb20d1cec14493115137db6362ed821:52
corvusSpamapS: i'm shivering with antici21:55
corvuspation21:55
SpamapSnice21:56
*** hasharAway has quit IRC22:06
mordredcorvus: ok. unix domain sockets work - but don't actually solve the control persist issue22:21
mordredcorvus: the issue being that the first control-persist connection creates the connection and forwards the socket- but with unix domain sockets once the listening process (the first playbook) exits, subsequent playbooks can't re-open the same socket because no SO_REUSEADDR support in unix sockets22:26
corvusdoh22:26
mordredcorvus: so it's almost more like we need to spawn up a thing similar to how we do ssh agents22:26
mordredcorvus: although I'm pretty confident i can get it down to a single server listening on a single local socket for all of the remote connections22:27
corvusmordred: so a process that takes input on a socket and writes that to a file?22:27
mordredyah22:27
mordredor, more specifically, a process that takes input on a socket, decodes logging messages and emits them to the location for the logger as defined in the logging config file22:28
mordredbut yet22:28
mordredbut yes22:28
corvus*nod*22:28
corvusmordred: even after it exits, it can't be reused?22:31
mordredcorvus: not with it having been forwarded over the persistent ssh connection22:31
corvusoh i see22:32
mordredcorvus: hrm. also - when i said 'unix domain sockets work' earlier - I may not have been accurate22:37
mordrednevermind. inverted port forwarding arguments. AGAIN22:39
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Use unix sockets instead of TCP sockets  https://review.openstack.org/54246922:39
mordredcorvus: so - that totally works for one playbook - and will work again once control persist dies22:41
mordredcorvus: I'm going to step away from the computer for a second, but I'll figure out job-lifecycled version next22:42
*** elyezer has quit IRC22:43
*** elyezer has joined #zuul22:44
corvuskeystoneauth1.exceptions.http.BadRequest: Expecting to find domain in project. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-0b54d669-dbc1-4e32-b81b-e8cad33d3486)22:58
corvusmordred: ^ what does that mean?22:58
dmsimardSounds like keystone v2 vs v3 config mismatch23:19
corvusi tried using the v2 config too, but that wasn't working23:20
corvusi'm stumped23:21
*** elyezer has quit IRC23:43
*** elyezer has joined #zuul23:44

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