Monday, 2018-03-19

*** odyssey4me has quit IRC00:09
*** odyssey4me has joined #zuul00:09
*** xinliang has quit IRC00:11
*** mrwtaqjb has joined #zuul00:12
*** mrwtaqjb has quit IRC00:12
*** xinliang has joined #zuul00:24
*** xinliang has quit IRC00:24
*** xinliang has joined #zuul00:24
*** JasonCL has joined #zuul00:33
*** JasonCL has quit IRC00:38
*** JasonCL has joined #zuul01:11
*** JasonCL has quit IRC01:17
*** JasonCL has joined #zuul01:29
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: Add allowed-triggers and allowed-reporters tenant settings  https://review.openstack.org/55408201:30
*** JasonCL has quit IRC01:34
tristanCSpamapS: tobiash: here you go: https://review.openstack.org/#/q/topic:nodepool-web01:39
SpamapSsweeeeeeet01:40
tristanCit actually deployed it here: https://softwarefactory-project.io/zuul/local/labels.html01:40
*** Wei_Liu has joined #zuul02:07
*** swest1 has joined #zuul02:17
*** swest has quit IRC02:18
*** JasonCL has joined #zuul02:59
*** JasonCL has quit IRC03:04
jheskethtristanC: those improvements to the webui are awesome btw :-)03:27
dmsimardtristanC: I'm not sure I would expose the IP and the port in the web UI by default. Can you make that an opt-in toggle maybe ?03:31
dmsimardIs the node name/id available to display?03:33
tristanCjhesketh: glad you like them, I hope we'll be able to demonstrate admin action through the webui soon, like hold a build, retrigger a job or even delete nodes04:12
tristanCdmsimard: yes sure, i think we need to announce admin capabilities on the /info endpoint, and then the ui could be adapted04:13
*** JasonCL has joined #zuul04:35
*** JasonCL has quit IRC04:41
jheskethtristanC: neat :-)04:41
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add zookeeper driver and /{tenant}/labels controller  https://review.openstack.org/55397905:06
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add nodepool labels list page  https://review.openstack.org/55398005:06
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add /{tenant}/nodes controller  https://review.openstack.org/55399805:06
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add nodepool nodes status page  https://review.openstack.org/55399905:06
*** openstackgerrit has quit IRC05:49
*** bhavik1 has joined #zuul06:10
*** flepied has quit IRC06:32
*** bhavik1 has quit IRC06:35
*** yolanda_ is now known as yolanda07:21
*** swest1 has quit IRC07:37
*** AJaeger has quit IRC07:53
*** aluria` is now known as aluria08:04
*** aluria has quit IRC08:05
*** aluria has joined #zuul08:05
*** flepied has joined #zuul08:08
*** jpena|off is now known as jpena08:59
*** hashar has joined #zuul09:32
*** JasonCL has joined #zuul09:33
*** hashar has quit IRC09:39
*** JasonCL has quit IRC09:43
*** jamielennox has quit IRC09:43
*** jamielennox has joined #zuul09:48
*** hashar has joined #zuul10:03
*** Wei_Liu has quit IRC11:01
*** Wei_Liu has joined #zuul11:02
*** JasonCL has joined #zuul11:41
*** logan- has quit IRC11:52
*** logan- has joined #zuul11:52
*** dmellado has quit IRC12:24
*** dmellado has joined #zuul12:27
*** odyssey4me has quit IRC12:42
*** odyssey4me has joined #zuul12:42
*** rlandy has joined #zuul12:43
*** dkranz has joined #zuul12:48
*** jpena is now known as jpena|lunch12:56
*** AJaeger has joined #zuul13:14
*** sshnaidm is now known as sshnaidm|afk13:31
*** myoung|afk is now known as myoung|rover13:58
*** jpena|lunch is now known as jpena14:06
*** flepied has quit IRC14:23
*** flepied_ has joined #zuul14:23
*** flepied_ is now known as flepied14:24
dmsimardbtw I came across this last weekend, just sharing -- it's a recording of what every Ansible callback does. I thought it was pretty cool, there's a lot of nice callbacks I didn't even know existed: https://rndmh3ro.github.io/14:31
dmsimardfungi: am I supposed to make that particular story public btw ?14:56
dmsimardcorvus: ^14:56
*** hashar is now known as hasharAway15:14
Shrewsugh. whenever i start over in playing around with devstack, i always fall into some fresh devstack-brokenness-hell that hinders my progress15:23
* Shrews (like Garfield) hates Mondays15:24
*** openstackgerrit has joined #zuul15:33
openstackgerritFabien Boucher proposed openstack-infra/zuul master: Add a loading_errors info to {tenant}/info endpoint  https://review.openstack.org/55387315:33
clarkbShrews: I tend to start it from scratch on a fresh VM which seems to make it happier than trying to resurrect old ones15:34
Shrewsclarkb: that's what i did15:35
Shrewsclarkb: just going to use the stable/queens branch15:35
Shrewsmaster is b0rked b/c of https://bugs.launchpad.net/nova/+bug/175575615:35
openstackLaunchpad bug 1755756 in OpenStack Compute (nova) "ImageUnacceptable: Image is unacceptable: 'qemu-img info' parsing failed" [Undecided,New]15:35
*** flepied has quit IRC15:37
Shrewsthis weekend, i finally got a machine with enough umph to run my own zuul, so trying to setup all the things15:38
corvusdmsimard: you mean 2001683?  if you're satisfied there isn't a security issue, then yes, please make it public.15:40
dmsimardcorvus: ack, I'll try and reproduce on a master deployment before opening it up.15:41
corvusdmsimard: sounds good, thx15:41
openstackgerritClark Boylan proposed openstack-infra/zuul-jobs master: Refactor "emit-ara-html" into a new role: "ara-report"  https://review.openstack.org/51387415:45
clarkbShrews: reporter on that bug says it affects pike too? in any case could not open /var/lib is probably a system level issue clashing with nova's expectations?15:50
Shrewsclarkb: doesn't matter. queens is working  :)15:50
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add irrelevant-branches negative matcher  https://review.openstack.org/55280916:00
corvusSpamapS: assume you're busy so i fixed up the things i saw wrong with that ^16:00
corvusi was thinking once again whether we could do something other than 'irrelevant'... maybe just 'not-branches' and 'not-files' would be okay.16:01
*** dtruong has joined #zuul16:02
*** flepied has joined #zuul16:16
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Update README and add GPL license  https://review.openstack.org/55428016:25
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul web: add admin endpoint, enqueue & autohold commands  https://review.openstack.org/53900416:43
openstackgerritMatthieu Huin proposed openstack-infra/zuul master: zuul autohold: allow operator to specify nodes TTL  https://review.openstack.org/54340316:43
*** jpena is now known as jpena|brb16:43
*** myoung|rover is now known as myoung|food16:48
*** weshay is now known as weshay_brb17:05
*** dtruong has quit IRC17:05
hughsaundersOh, no electrofelix today :(17:19
hughsaundersHey mordred, I'm working on a nodepool plugin for Jenkins (https://github.com/rcbops/nodepool-plugin) Its not in a working state but isn't that pretty. However it might be a good time to move it into the openstack-infra namespace, get some test and publication jobs going.. whos the best person to talk to about that?17:20
hughsaunders*it IS in a working state17:21
pabelangerI've noticed when I got to zuul.o.o, for a brief moment, I see some unrendered HTML (missing CSS) flash in the top left of my browser apply the CSS. Any ideas where to look to fix that?17:26
pabelangerbefore applying*17:26
pabelangerusing chrome17:27
clarkbpabelanger: I believe mordred's change series does correct that17:28
pabelangerah, cool!17:28
clarkbpabelanger: the problem was it loaded the templates before applying them or something but in proposed change there is a change that does it all together17:28
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Uninstall and reinstall siblings one at a time  https://review.openstack.org/55429717:28
pabelangerclarkb: nice17:28
clarkbhughsaunders: if you haven't read it yet the infra-manual has a project creators section that will walk you through adding projects to gerrit. I think with the proposed zuul split out of openstack proper we might consider not adding any new zuul related proejcts to openstack proper as well (they'd still be hosted by our gerrit just not in openstack governance)17:31
mordredpabelanger, clarkb: yes - you can verify the fix here: http://logs.openstack.org/27/551327/7/check/build-javascript-content/de50d9b/npm/html/status.html17:32
hughsaunders clarkb: Thanks.. so openstack-infra maybe but not openstack?17:32
hughsaundersclarkb: I guess I was also wanting to gauge interest as openstack is moving away from Jenkins so wondered if Jenkins plugins are still interesting.17:32
hughsaundersI know electrofelix is interested, but he isn't around :/17:33
clarkbhughsaunders: I think you'll find that many of us are not very interested in making jenkins things work at this point :) we'll happily host the project for you under "stackforge" if you want access to the tooling and CI17:33
pabelangermordred: ++ yup, no longer see the issue17:33
clarkbwhich is related to electrofelix's other question. I don't think the hosting of related projects changes for now. They still go in stackforge unless they want to be part of openstack governance.17:34
clarkbI should respond to that email thread once our zuul install is happy with new projects17:35
odyssey4meclarkb stackforge as a namespace still is used for things?17:35
clarkbodyssey4me: not as a namespace, but it is still technically what things are called that we host that aren't part of openstack governance iirc17:35
clarkbodyssey4me: ara for example is not an openstack project but we host it as a "stackforge" project I think17:35
clarkbfungi: ^ as our resident tc member can probably clarify anything I got wrong there17:35
dmsimardyeah ara is kinda like a stackforge project17:35
odyssey4meclarkb ah ok, alright - so where do we import the jenkins plugin to?17:36
mordredyah17:36
dmsimardI mean, unless it gets formally picked up by openstack foundation, openstack or zuul :p17:36
clarkbodyssey4me: openstack/your-project-here is the current location17:36
clarkbodyssey4me: the project creation docs should touch on that too I think17:36
clarkbbasically hosting on openstack's project hosting doesn't make an openstack project. Joining the openstack governance does17:36
odyssey4meok, we thought that *maybe* this might need to go into openstack-infra, rather than openstack, given that's where zuul lives17:36
fungiclarkb: odyssey4me: we stopped officially using the term "stackforge" a couple years back and just refer to "official OpenStack deliverable repositories" vs "unofficial repositories"17:37
*** jpena|brb is now known as jpena17:37
fungi"stackforge" is still sort of used as shorthand for unofficial repos17:38
fungiodyssey4me: nah, git namespaces are entirely irrelevant at this point17:38
fungiwe'd like to work out a way to get rid of them and flatten our git hosting17:39
odyssey4meokie dokey, 'openstack' it is hughsaunders :)17:39
fungithey're mostly an artifact of setting them up to map to different github orgs for repository mirroring17:39
hughsaundersk17:39
hughsaundersare they any jenkins plugins in stackforge that I can copy publishing pipelines from?17:40
fungibasically "openstack" is the catch-all git namespace we host things out of (official or unofficial)17:40
clarkbhughsaunders: some of our old plugins may have jobs but I'm unsure if they are tested post zuulv3 transition17:40
clarkbwith zuulv2 we did have maven publishing, but I'd be surprised if any of it is exercised post zuulv3 transition17:41
clarkbwe can move that discussion over to #openstack-infra too as its likely more service based than zuul specific17:41
clarkbunless maybe we want to bake that stuff into zuul-jobs for reuse?17:42
odyssey4meclarkb perhaps best to start small ;)17:42
hughsaundersodyssey4me: we will need maven publishing though17:43
odyssey4mehughsaunders That should be reasonably straightforward to setup as an in-repo job to start with.17:43
hughsaundersodyssey4me: yeah, doesn't matter where it is, just needs to be possible :)17:44
odyssey4meIt can be migrated into a built-in zuul job once it's stable.17:44
clarkbhughsaunders: it should be possible. You sign up for an account on the nexus. Add credentials to your secrets, push from there.17:45
openstackgerritMerged openstack-infra/zuul master: Update README and add GPL license  https://review.openstack.org/55428017:46
*** weshay_brb is now known as weshay17:50
openstackgerritMonty Taylor proposed openstack-infra/zuul master: web: add /{tenant}/jobs/{job_name} route  https://review.openstack.org/55097817:55
openstackgerritMonty Taylor proposed openstack-infra/zuul master: web: add /{tenant}/projects routes  https://review.openstack.org/55097917:55
openstackgerritMonty Taylor proposed openstack-infra/zuul master: web: add /{tenant}/pipelines route  https://review.openstack.org/54152117:55
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Rename javascript package to @zuul-ci/dashboard  https://review.openstack.org/55199917:55
*** myoung|food is now known as myoung|rover17:58
ShrewsWhat are we using to install bubblewrap on ubuntu?18:00
mordredShrews: ppa:openstack-ci-core/bubblewrap18:01
Shrewsmordred: thx18:01
dmsimardmordred: I've been meaning to peek at your frontend stack patches out of curiosity .. is the build-javascript-content job supposed to work ?18:02
dmsimardI got blank pages when I looked yesto18:02
dmsimardyesterday*18:02
mordreddmsimard: yes - there is a bug that needs to be fixed starting at the angularjs -> angular transition patch18:03
mordreddmsimard: ifyou look at the build-javascript-content jobs on the stack ahead of that, they shoudl all work18:04
dmsimardOk, neat. Thanks.18:04
mordredcorvus: 536882 to 551999 are ready for review18:04
dmsimardThe job was green but the page was blank so..18:04
dmsimard¯\_(ツ)_/¯18:04
*** myoung|rover is now known as myoung|taxi18:06
*** myoung|taxi is now known as myoung|biab18:06
mordreddmsimard: yah. generally speaking that page should ALWAYS work and if it doesn't it's a big problem. however, in some cases (that one is a good example) we don't have any tests yet that will turn red18:08
dmsimardThat's where stuff like selenium comes in I guess ?18:08
mordredobviously adding tests that turn red is a thing we should do18:08
mordreddmsimard: yah - it might be a selenium test - it might be possible to add more targetted unit/functional tests to the js code - it's possible we want both - or it's possible we can add a test to the python zuul-web unittests that would catch the break in the angular patch ... or, perhaps all of the above :)18:09
corvusmordred: do you want to merge some/all of that stack before the v3 release?18:09
openstackgerritMerged openstack-infra/zuul-jobs master: Refactor "emit-ara-html" into a new role: "ara-report"  https://review.openstack.org/51387418:10
mordredcorvus: yes, I'd like to get at least through 551327 before 3.018:14
corvusmordred: that's in a stack that is dependent on an outdated change18:15
mordredcorvus: yes - we need to land the API endpoints, and there is an update needed to one of those patches, so we're only good up through 55199918:17
corvusmordred: there's a lot of stuff that we were deferring post v3 there.  i'm surprised by this.18:17
corvusmordred: is there something that's broken that absolutely must be merged?  or is there something that can't wait until after v3 because it will prevent us from fixing it later?18:18
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Use unix sockets instead of TCP sockets  https://review.openstack.org/54246918:19
mordredcorvus: a little of both - it's more the second thing I'm concerned about, although the page flashing on load issue is pretty ugly and is the thing I'd consider in the first category18:20
corvusmordred: we're not advertising this as a public api right, so why can't we fix it later?18:20
mordredcorvus: the stestr patch is in there because I hit an "I can't figure out what in the test suite is hanging/timing out" moment and could only solve it by locally updating things to use stestr - that can be removed from the stack easily though if you prefer18:22
mordredcorvus: page flashing is a pure-javascript issue - although we could release without fixing it of course18:22
corvusmordred: from my pov, there are problems with the js/web stuff, but we've crossed the threshold we set for the v3 release, which was "make it installable".  i'd like to just focus on the remaining v3 blockers (tests for console streaming, and security issues).18:25
corvusmordred: https://review.openstack.org/547576 landed a bunch of "TODO: Fill in specifics in the next patch" to the docs.  where is that patch?18:27
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Start log receiver in executor  https://review.openstack.org/54630418:27
mordredcorvus: ok. there is still one more issue I want to solve to verify that we don't need to do anything that would require a simultaneous update of python/javascript to get it rolled out18:28
corvusmordred: okay, i agree that's the sort of thing we should try to avoid doing post-release :)18:29
mordredcorvus: that patch is on the todo list right after making sure we're good to go with being able to roll out changes18:29
mordredcorvus: yah- that's my #1 concern18:30
mordredcorvus: breaking people post 3.0 release would give me the sads :)18:30
*** rlandy is now known as rlandy|brb18:31
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Remove empty sections from docs  https://review.openstack.org/55431518:32
corvusmordred: ^ i think that patch would be a good idea, but i'd like to try to keep the docs as polished as possible, so i just removed the empty sections for now18:33
mordredcorvus: WFM18:33
corvus(i just went to look something up, and they looked broken: https://docs.openstack.org/infra/zuul/admin/installation.html#static-offload )18:34
mordredcorvus: well, the didn't just look broken... I'd contend they were broken :)18:34
corvusmordred: oh good, i'm not going more insane :)18:34
mordred:)18:34
*** openstackgerrit has quit IRC18:48
*** openstackgerrit has joined #zuul18:58
openstackgerritAndreas Jaeger proposed openstack-infra/zuul-jobs master: Uninstall and reinstall siblings one at a time  https://review.openstack.org/55429718:58
*** myoung|biab is now known as myoung|rover19:08
*** rlandy|brb is now known as rlandy19:12
*** jpena is now known as jpena|off19:15
Shrewscorvus: would it be safe to move writeLoggingConfig() from _execute() to before startLogReceiver() in your log streaming change (line 623 here https://review.openstack.org/#/c/546304/3/zuul/executor/server.py)?19:23
Shrewsi'm not seeing any immediate reason why not, and the log receiver needs that file to exist before we start it19:23
Shrewsok, that seems to make it break farther along, so seems ok19:27
corvusShrews: yeah, i can't think of a reason not to19:33
*** hasharAway has quit IRC19:46
*** openstackgerrit has quit IRC19:48
*** openstackgerrit has joined #zuul20:06
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Start log receiver in executor  https://review.openstack.org/54630420:06
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Start log receiver in executor  https://review.openstack.org/54630420:08
clarkbif I read that right it is essentially a proxy because we can only have a single connection back out of the ansible execution?20:09
clarkbthen executor can proxy as many connections from finger or wherever?20:09
clarkboh wait no its doing python logging so it can output to wherever?20:13
clarkbShrews: corvus left some comments but its mostly minor things that would be nice to address if new patchsets are required20:19
*** flepied has quit IRC20:19
*** hashar has joined #zuul20:21
Shrewsclarkb: i would not review yet20:22
Shrewstrying to fix the tests20:22
clarkboh I did just to understand what was going on20:22
*** flepied has joined #zuul20:24
openstackgerritJeremy Stanley proposed openstack-infra/zuul master: Add instructions for reporting vulnerabilities  https://review.openstack.org/55435220:44
fungicorvus: i may not be around for the meeting in a couple hours, but that's ^ a start at vulnerability reporting instructions. i'm still working on the vulnerability management process document to go with it20:44
*** dtruong has joined #zuul20:59
Shrewswait, meeting is in a couple of hours?21:01
pabelangeryah another 58mins21:02
pabelangerI won't be able to attend this week21:03
*** hashar has quit IRC21:08
Shrewscorvus: in your 546304 review, did you get familiar enough with the ansible python api to figure out what "task._host.get_name()" should actually be? (task does not have a _host attribute)21:25
jheskethMorning21:56
corvusit's zuul meeting time in #openstack-meeting-alt22:02
*** eb0t- has joined #zuul22:38
jlkDropped a comment on the github3.py bug: https://github.com/sigmavirus24/github3.py/issues/794#issuecomment-37441333923:01
corvusSpamapS: https://review.openstack.org/552809 looks like it still has a test failure; i haven't had a chance to dig into that today23:01
ianwcorvus: i was going to ask if we had free time in mtg, but https://review.openstack.org/#/c/553999/ with the nodepool web stuff in zuul.  that's the direction we're going?  i wasn't sure on the coupling there23:02
ianw(sorry, asked in infra but here is better)23:02
corvusianw: i think the thing we discussed at the ptg was: 1) make a real nodepool-web service similar to (but independent from) zuul-web.  2) have zuul-web use the api from #1 to incorporate information into a single dashboard.  maybe even use the same javascript code.23:04
corvusianw, tristanC: it doesn't look like that quite matches that discussion23:05
ianwyeah, i wasn't sure how much zuul-web was going to turn into horizon :)23:07
corvusindeed.  i'd rather not implement that twice, so i think the ptg plan is a good compromise -- it'll look the same for the user, but we don't have to have two web apis.23:08
corvusmoreover, there's a *bunch* of stuff about nodepool that zuul doesn't need to know right now.  i'd like to keep it that way.23:09
SpamapScorvus: yeah it's just half-done. I've got some non-zuul stuff the next 2 days so will likely get to it mid-week.23:10
ianwright, it was too a deep a coupling that i thought might not be so great longer term; my thought was that it would want to be behind a enable/disable flag at least23:11
corvusSpamapS: cool, thanks.  while you're doing the non-zuul stuff -- i was thinking of opening pandora's box-of-names again and using "not-files" and "not-branches" instead of irrelevant... maybe you can cipher on whether that's a good idea :)23:11
SpamapScorvus: i'll let it bounce in my head until then. :)23:12
SpamapSpretty echo-y in there today :-P23:12
*** myoung|rover is now known as myoung|bbl23:13
corvusianw: in fact, i think the 'info' endpoint for zuul is turning into a place for things like that.  so presumably, if there was no nodepool or the admin turned it off, then that page wouldn't show up in zuul.23:13
corvusianw: but in general, zuul is pretty tied to nodepool; there's no other option right now other than "run jobs with no nodes".  so some degree of coupling is okay i think.  for me, it's mostly about making sure it ends up in the right place (most of the implementation should be closer to nodepool than zuul)23:14
ianwcool; well i think what nodepool outputs is looking pretty api-ish; especially after we did the stuff like made it use content detection for json etc.23:16
fungiis tests.unit.test_github_crd.TestGithubCrossRepoDeps.test_crd_dependent known to sometimes yield nondeterministic results?23:51
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Uninstall and reinstall siblings one at a time  https://review.openstack.org/55429723:59

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