Thursday, 2018-04-05

*** acozine1 has quit IRC00:20
*** gouthamr has joined #zuul00:37
*** odyssey4me has quit IRC00:41
*** odyssey4me has joined #zuul00:41
*** sc68cal_ has joined #zuul00:42
*** rbergero1 has joined #zuul00:46
*** graffatcolmingov has joined #zuul00:48
*** mhu has joined #zuul00:48
*** ssbarnea_ has joined #zuul00:49
*** mhu` has quit IRC00:51
*** sc68cal has quit IRC00:51
*** eventingmonkey has quit IRC00:51
*** sigmavirus24 has quit IRC00:51
*** fbo_ has quit IRC00:51
*** ssbarnea has quit IRC00:51
*** rbergeron has quit IRC00:51
*** lennyb has quit IRC00:51
*** ssbarnea_ is now known as ssbarnea00:51
*** eventingmonkey has joined #zuul00:53
*** fbo_ has joined #zuul00:57
*** lennyb has joined #zuul00:58
*** harlowja has quit IRC01:42
*** JasonCL has quit IRC01:47
*** gouthamr has quit IRC02:33
*** elyezer_ has quit IRC02:56
*** elyezer_ has joined #zuul02:57
tristanCclarkb: according to https://gitlab.openci.io/openci/community/issues/3 , it seems like websocket is considered to be the protocol to exchange data between ci?03:12
tristanCthus we may have to implement a websocket source/reporter driver instead03:13
clarkbI dont think anything ia decided my undertsanding was they were still interested in exploring options03:14
clarkband had never heard of fedmsg before03:15
clarkb(so were happy to have more input)03:15
tristanCpabelanger: the nice thing with mqtt is that it's already being used for gerrit events, so it makes more sens to me to make zuul publish there directly03:17
clarkbya thats just an rfc03:17
clarkbso one proposal03:17
clarkbit is interesting that the proposal is to build a new pub sub on top of websockets though rather than using an existing implementation03:20
clarkbIf you are interested in that stuff I know fdegir is too and lrobably a good person to talk to03:20
tristanCclarkb: with mqtt, aren't you missing event if you are disconnected?03:21
clarkbtristanC: depends, you an configure the client to ask the server to queue for you iirc03:21
clarkbif the queue is smaller than eventa over your disconnection period you do los messages iirc03:22
tristanCperhaps it would be easier to consume using a feed protocol like jsonfeed or rss03:23
clarkbits too late for me to properly think this through but I'll have to give it a proper read in the morning03:25
clarkbI think the two things that initially stand out to me are that building a new pub sub state machine rather than using an existing protocol seems like more work than necessary. And it seems this protocol expects you to know who your dependents are which is likely not realistic (you can know what you depend on but not who depends on you)03:26
tristanCclarkb: that's my feeling too, though it sounds like a zuul driver could accomodate that protocol if needed03:28
fdegirtristanC: regarding rfc, as clarkb said, it’s a proposal from one of the participants03:34
fdegirtristanC: it seems he’s been thinking about similar stuff for a while and written rfc already03:35
*** harlowja has joined #zuul03:37
fdegirtristanC: so, it would be good if you can share anything you may have been thinking/doing already there for people to see03:37
tristanCfdegir: sure, i'll comment on the issue03:40
*** elyezer_ has quit IRC04:27
*** elyezer_ has joined #zuul04:36
*** harlowja has quit IRC05:22
*** haint_ has quit IRC06:14
*** nguyenhai has joined #zuul06:14
*** nguyenhai has quit IRC06:32
*** Wei_Liu1 has joined #zuul06:39
*** Wei_Liu has quit IRC06:41
*** Wei_Liu1 is now known as Wei_Liu06:41
*** nguyenhai has joined #zuul06:45
*** elyezer_ has quit IRC06:59
*** elyezer_ has joined #zuul06:59
*** hashar has joined #zuul07:22
*** jesusaur has quit IRC07:23
*** jesusaur has joined #zuul07:29
*** electrofelix has joined #zuul07:41
*** jpena|off is now known as jpena07:42
tobiashpabelanger: responded on 53568507:46
*** elyezer_ has quit IRC07:59
*** elyezer_ has joined #zuul08:02
*** elyezer_ has quit IRC08:07
*** elyezer_ has joined #zuul08:09
*** zaro__ has quit IRC08:10
*** zaro__ has joined #zuul08:10
*** logan- has quit IRC08:11
*** cmurphy has quit IRC08:11
*** odyssey4me has quit IRC08:11
*** pbrobinson has quit IRC08:11
*** dvn has quit IRC08:11
*** cmurphy has joined #zuul08:13
*** logan- has joined #zuul08:13
*** odyssey4me has joined #zuul08:16
*** pbrobinson has joined #zuul08:16
*** dvn has joined #zuul08:16
*** dvn has quit IRC08:24
*** persia has quit IRC08:26
*** persia has joined #zuul08:28
*** dvn has joined #zuul08:35
*** hashar has quit IRC08:35
*** JasonCL has joined #zuul08:48
*** JasonCL_ has joined #zuul08:53
*** yolanda_ is now known as yolanda08:54
*** JasonCL has quit IRC08:55
*** elyezer_ has quit IRC08:58
*** sshnaidm|afk is now known as sshnaidm|off09:00
*** JasonCL_ has quit IRC09:02
*** elyezer_ has joined #zuul09:03
*** JasonCL has joined #zuul09:07
*** JasonCL has quit IRC09:08
*** JasonCL has joined #zuul09:09
*** JasonCL has quit IRC09:13
*** JasonCL has joined #zuul09:14
*** JasonCL has quit IRC09:25
*** JasonCL has joined #zuul09:29
*** snapiri has quit IRC09:33
*** AJaeger has quit IRC09:38
openstackgerritMatthieu Huin proposed openstack-infra/nodepool master: Add separate modules for management commands  https://review.openstack.org/53630309:42
*** JasonCL has quit IRC09:56
*** JasonCL has joined #zuul09:57
*** JasonCL has quit IRC09:59
*** JasonCL has joined #zuul10:04
*** JasonCL has quit IRC10:09
*** elyezer_ has quit IRC10:20
*** elyezer_ has joined #zuul10:21
*** jpena is now known as jpena|lunch11:00
*** JasonCL has joined #zuul11:05
LinuxJedimordred, Shrews, corvus: so, the two things that are definitely missing in Zuul that we would need are: Grid Display, this is an output of builds in a grid similar to buildbot (see the grid display output here: http://buildbot.askmonty.org/buildbot/), proper log viewing and a deep search to find things like all of the failures of a certain test.11:06
*** xinliang has quit IRC11:25
*** elyezer_ has quit IRC11:35
*** xinliang has joined #zuul11:38
*** xinliang has quit IRC11:38
*** xinliang has joined #zuul11:38
*** elyezer_ has joined #zuul11:41
*** jpena|lunch is now known as jpena12:01
*** JasonCL has quit IRC12:06
*** elyezer_ has quit IRC12:27
*** elyezer_ has joined #zuul12:28
*** odyssey4me has quit IRC12:44
*** odyssey4me has joined #zuul12:44
*** elyezer_ has quit IRC12:45
*** elyezer_ has joined #zuul12:47
*** gouthamr has joined #zuul12:49
*** gouthamr has quit IRC12:49
*** gouthamr has joined #zuul12:49
*** pwhalen has quit IRC12:59
*** pwhalen has joined #zuul13:04
*** pwhalen has joined #zuul13:04
*** dkranz has joined #zuul13:04
*** JasonCL has joined #zuul13:40
*** JasonCL has quit IRC13:41
*** JasonCL has joined #zuul13:46
electrofelixhughsaunders: did the nodepool-plugin get moved?13:50
*** JasonCL has quit IRC13:51
*** elyezer_ has quit IRC13:56
*** JasonCL has joined #zuul13:57
*** elyezer_ has joined #zuul14:01
dmsimardmordred, corvus: https://review.openstack.org/#/c/556967/ was a pretty breaking change that merged quickly right before the release and it broke SF. We'll work on adding CI on our end (and potentially third party CI on Zuul directly) but I hope we can do better now that v3 is released.14:03
dmsimardI don't know if anyone else is following master but it probably broke them too14:04
corvusdmsimard: we know, that was the intent.  we knew that change was breaking which is why we delayed the release for several weeks while we worked on it.  we discussed it quite a lot, including with tristan.14:06
corvusdmsimard: we don't intend to make those kinds of breaking changes any more.14:06
corvusdmsimard: if you want to work on ci, please work on adding tests to zuul.  there's no reason that needs third-party ci.14:07
tristanCfwiw it didn't "broke SF" as we the change couldn't pass the ci with new api route, it needed some workaround to support both routes until sf zuul package using the tag landed14:07
corvusyeah, there was no reasonable way to roll that out without intervention14:10
corvuswe had to hold automatic updates and apply them manually for openstack14:10
corvusdmsimard: fyi, this file already has one test for how sf.io cofigures its web servers: http://git.zuul-ci.org/cgit/zuul/tree/tests/unit/test_web_urls.py14:11
corvushappy to add more :)14:11
dmsimardcorvus: I see what you mean by adding tests to Zuul -- but I still see value in knowing that a particular patch appears to be breaking an implementation of Zuul. I guess I could compare that to Nova working by itself vs working through devstack.14:12
tristanCcorvus: would be nice to have a real functional test, e.g. testing a base job with secret14:13
dmsimardIf BonnyCI was still a thing, I'd be interested in knowing if a patch breaks them14:13
dmsimardEven if it's just for the sake of fostering collaboration between the developers and the consumers/packagers14:13
corvusdmsimard: sure, but that should be the second line of defense -- make that test if we can't model it in the unit tests.14:14
corvusdmsimard: bonnyci is not a thing, so all the work they contributed to zuul's test suite lives on.14:14
corvustristanC: we can do that in zuul's unit test suite14:15
corvustristanC: we have quite a few similar tests14:15
dmsimardfair, but SF has to test it's implementation on top of the packaged master anyway -- the overhead of running this same job third party is probably minimal14:15
dmsimardFWIW I'm not telling you these should be voting jobs14:15
corvustristanC: the thing to keep in mind is that zuul's "unit" test suite is much more like any other program's "functional" test suite14:16
corvuseverything it does is as real as possible14:16
tristanCcorvus: though it's still using mock environment, while a functional test that install zuul, start the service, maybe even use zuul-jobs and trigger a job would provide valuable feedback imo14:17
corvustristanC: the only thing that is mocked is gerrit14:17
tristanCand nodepool?14:18
corvustristanC: and nodepool, for the tests which use nodes (though there's another job that uses a real nodepool)14:18
corvusfor example, here's a test that runs about 8 jobs testing various things by running actual ansible playbooks: http://git.zuul-ci.org/cgit/zuul/tree/tests/unit/test_v3.py#n203014:20
tristanCoh so maybe it's the zuul-jobs and secrets that could be added to the nodepool-zuul-functional job14:21
corvustristanC: yeah, we might want to use that job, or a new one, since the main unit tests don't require network access.14:23
tristanCcorvus: ftr, here is the sf-ci job that validate zuul is working as expected: https://softwarefactory-project.io/r/gitweb?p=software-factory/sf-ci.git;a=blob;f=health-check/zuul.yaml14:24
tristanCand because config-update are done by zuul too, post job are also validated like so: https://softwarefactory-project.io/r/gitweb?p=software-factory/sf-ci.git;a=blob;f=health-check/playbooks/config_submit_change.yaml14:27
dmsimardcorvus: I'm already planning on having a zuul-related integration job in ara's gate .. would I catch errors by installing ara from source (from the patch) and running those tests ?14:28
corvustristanC: i like that test :)14:28
tristanCcorvus: those were the test that detected the issue with the secret refactor that were not working for base job14:28
corvustristanC: yep, and led to you helping to improve the unit tests.  to be clear, i'm not opposed to more testing in the form of third-party ci, but i think it's important that it be auxillary -- any time it catches an error that the unit test suite didn't catch, we should fix the unit test suite if possible.  this is a good example :)14:31
corvustristanC: (that patch hasn't landed yet, but it will)14:31
corvusdmsimard: i think if ara-in-zuul has errors, zuul should ignore them, so the tests may not help as written (we'd need to come up with a way to validate results)14:32
corvusdmsimard: (they would *run* ara though, just not use the output)14:33
dmsimardcorvus: I suppose you could say it's more about the ara-report role from zuul-jobs14:33
tristanCcorvus: oh yes, i meant to add those kind of test in first-party ci. we actually can't afford to run sf-ci on every zuul change :-)14:33
corvustristanC: maybe someday :)14:33
dmsimardcorvus: What I was planning was to set up a nested zuul (in a multinode job, nodepool would use the second node as a static node) with ARA from source (with the gerrit patch) and then run a fairly regular job.. then check if the report was generated successfully14:34
dmsimardas the new version picks up momentum, it'll become important for me to know when a particular patch breaks something14:35
dmsimardFWIW doing nested Ansible things makes my brain hurt14:36
corvusdmsimard: what's the status of my 3 patches to ara?  you asked me to hold for 1.0 6 months ago...14:39
dmsimardcorvus: yup, that's sad isn't it14:39
dmsimardit makes me sad14:39
corvusi think they help significantly when using ara with zuul14:40
corvusdmsimard: do you want them on the master branch, on 1.0...?14:40
*** electrofelix has quit IRC14:42
dmsimardcorvus: I'll give another look at the patches. Long story short, there was not supposed to be a new release of the stable version but ara 1.0 has turned a bit into a zuul v3 thing. I'm planning a release sometime soon to address some issues I've seen with the middleware and other performance things based on feedback from other users14:43
corvusdmsimard: ok.  the patches as they stand do need work; but it'll be nice to know whether/when that work should happen14:44
dmsimardcorvus: will do14:45
dmsimardcorvus: just rebased your patches so they're at least current, I'll take a look at some point14:52
corvusdmsimard: okay, i'm happy to update them to address comments.  let me know when it's safe.  :)14:57
*** maeca has joined #zuul15:26
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Check out more appropriate branches of role and playbook repos  https://review.openstack.org/55864315:32
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Check out more appropriate branches of role and playbook repos  https://review.openstack.org/55864315:33
*** openstackgerrit has quit IRC15:34
corvusclarkb, tobiash, pabelanger, mordred: ^ i think that's ready now.  one question i think is worth asking -- is that the way to go?  i mean, ansible roles don't usually have parallel release tracks (ie, stable branches) do they?  though -- openstack-ansible does...  i guess the question is: does supporting multiple branches for roles make sense?  should we insist on only using a single branch from role repos?15:37
corvusor is that too prescriptive?15:37
*** yolanda_ has joined #zuul15:39
corvus(i believe we implicitly made the assumption (without realizing we were doing so) that roles repos wouldn't be branched, which is why we ended up with this case being unexamined)15:39
corvusalso, i wrote a long release note for that.  probably all release notes shouldn't be that long, but it's a complicated issue.  if anyone can suggest shorter wording i'm all for it.15:40
*** yolanda has quit IRC15:41
mordredcorvus: I think openstack-ansible provides an example of a case where a repo containing more than one role is legitimately branched - so I think supporting multiple branches for roles repos does make sense - also, projects that have roles that exist only in support of their zuul jobs - if the zuul jobs are branched, the roles need to be too ...15:52
*** colettecello has quit IRC15:53
*** gothicmindfood has joined #zuul15:53
mordredcorvus: that said, I think for single-role repos (which are more likely to be the form that we find roles in that are intended for more general use such as galaxy publication) the chances of having a branch are less?15:53
clarkbmordred: in osa case youd want roleA on branch A and role B on branch B from the same repo?15:54
mordredclarkb: I don't think so?15:57
corvustbh, that osa was branched has come as a surprise to me :)16:00
corvusi mean, it shouldn't have, since i've helped with their jobs.  i did not think through the implications :)16:01
corvusbut yeah, the queens branch of os_nova will install the queens branch of nova16:04
corvusso that's obviously a thing :)16:04
*** hashar has joined #zuul16:05
clarkbya I think osa woukd work in this system16:07
odyssey4meyep, OSA branches with the same series as openstack as each stable branch focuses on enabling the deployment of that series16:09
odyssey4mehowever, we're starting to also implement unbranched or differently branches infrastructure roles for non-openstack things16:10
corvusodyssey4me: do you distribute through galaxy at all?16:10
odyssey4mewe would like to, but the method to publish from openstack-ci as far as I know if not yet ready16:10
odyssey4me*is16:10
rcarrillocruzi believe tristanC has some role around for publishing to galaxy16:10
corvusodyssey4me: ah, yeah... if it were, how would the branching work?16:10
rcarrillocruzbut there are some issues , requireing user and password, not working with orgs or smth like that16:11
odyssey4meheh, yeah - galaxy only really publishes the last tag IIRC16:11
corvuslike, does galaxy let you say "install os_nova/queens"?16:11
odyssey4meso that's not something we've totally thought through16:11
corvusokay, so there indeed be dragons there :)16:11
odyssey4meour roles are all versioned in such a way that, for example, 16.x.x is pike, 17.x.x is queens16:11
odyssey4meso if we publish, hopefully we could publish any tag - I'm not sure, however, what galaxy would deliver if we published, say 16.0.6 after 17.0.116:12
odyssey4methat said, our interest in publishing at the point is more around our infrastructure roles - where we'd only really be concerned with people using the latest tag16:13
rcarrillocruzso galera and the likes?16:14
corvusthere are still some test failures on 558643 -- they look to be cases where the tests are relying on the playbook being inside the workdir to access content16:36
corvuswe have a carveout for 'trusted/' i think we just need to add 'untrusted/' to that16:37
*** openstackgerrit has joined #zuul17:02
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Check out more appropriate branches of role and playbook repos  https://review.openstack.org/55864317:02
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Allow lookup plugins to read from playbook dir  https://review.openstack.org/55913217:02
*** jpena is now known as jpena|off17:16
kklimondahmm, child jobs can't override variables set in parent (trusted) jobs?17:20
*** harlowja has joined #zuul17:21
*** hashar has quit IRC17:21
corvuskklimonda: they should17:21
corvuskklimonda: (but not 'final' jobs)17:22
*** harlowja has quit IRC17:25
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Allow some plugins to read from playbook dir  https://review.openstack.org/55913217:42
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Check out more appropriate branches of role and playbook repos  https://review.openstack.org/55864317:42
SpamapSOne thing about zuul-jobs17:55
SpamapSWe were trying to consume a few of them17:55
SpamapSand they assume things about the images you have17:55
SpamapSlike tox being installed17:55
SpamapSit would be good to have those assumptions clearly expressed somewhere, or even just the exact diskimage-builder elements to use.17:56
corvusSpamapS: ++ though i thought we had some handling for things like "install tox if it isn't already"18:03
corvusbasically, i think we wanted to keep assumptions about images as small as possible.  so when we find them, we should either document or fix them as appropriate :)18:04
Shrewsthat's the ensure-tox role (part of the tox job)  http://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/ensure-tox/tasks/main.yaml18:05
corvusShrews: yeah that's what i was remembering!18:06
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Add README to ensure-tox role  https://review.openstack.org/55914218:07
SpamapShm18:10
SpamapSmaybe I need to merge more18:10
SpamapSpulled in zuul-jobs about 2 weeks ago18:11
SpamapSneed a strategy for tracking it18:11
mrhillsmanwhat is a proper statement for what .zuul.yaml is18:12
*** AJaeger has joined #zuul18:13
mrhillsman"The file used by Zuul to manage your project's jobs"18:14
Shrewsper-project job configuration file?18:14
mrhillsmanthx18:14
Shrewsi'm just throwing out words. corvus likely can come up with something better18:15
mrhillsmani was trying to find it in the docs but thought i would ask here18:15
mrhillsmanagreed, i could do the same based on the docs, but figured someone here may have had to provide such a statement before18:17
*** harlowja has joined #zuul18:29
*** bhavik1 has joined #zuul18:32
openstackgerritMerged openstack-infra/zuul-jobs master: Add README to ensure-tox role  https://review.openstack.org/55914218:36
*** bhavik1 has quit IRC18:44
corvusmordred, tobiash, clarkb, pabelanger: https://review.openstack.org/559132 and https://review.openstack.org/558643 are green and ready for review18:54
corvusi made the necessary path security changes in a separate change to make sure they didn't get lost in the larger change.  (but they're also an improvement on their own -- fixing some cases where we would erroneously deny access)18:55
corvus(i think with those, we should always be able to use {{ role_path }} to read files)18:56
*** elyezer_ has quit IRC18:57
*** elyezer_ has joined #zuul18:58
*** JasonCL has quit IRC19:03
*** JasonCL has joined #zuul19:04
*** gouthamr has quit IRC19:04
*** JasonCL has quit IRC19:07
mordredcorvus: nice work19:23
*** jesusaur has quit IRC19:25
mordredcorvus: first patch looks great - second patch also looks great but is going to take a little longer to read19:35
*** jesusaur has joined #zuul19:41
*** JasonCL has joined #zuul19:59
*** JasonCL has quit IRC20:00
*** JasonCL has joined #zuul20:01
*** JasonCL has quit IRC20:02
*** JasonCL has joined #zuul20:02
*** JasonCL has quit IRC20:04
*** JasonCL has joined #zuul20:04
*** JasonCL has quit IRC20:11
*** JasonCL has joined #zuul20:13
*** JasonCL has quit IRC20:21
*** pwhalen_ has joined #zuul20:56
*** pwhalen has quit IRC20:57
*** pwhalen_ is now known as pwhalen21:23
*** pwhalen has joined #zuul21:23
*** JasonCL has joined #zuul21:52
*** JasonCL has quit IRC21:53
clarkbcorvus: I've +2'd the first one but not approved it in case you want tobiash to look over it (I think that may be worthwhile considering his time in this area of the code and its security implications)21:58
clarkbhowever its a lot more straightforward than I initially thought once I realized that 'file' is an overloaded term in ansible21:58
corvusclarkb: yeah, i agree tobiash should look at it21:59
clarkbcorvus: now starting to digest https://review.openstack.org/#/c/558643/ how does ansible know to use a playbook in untrusted/ over trusted/ is that just a path ordering thing? (I'm sure I'll eventually find it as I get through the review but it was somethign that jumped out at me after reading the commit message )22:18
*** maeca has quit IRC22:20
corvusclarkb: it's preparePlaybook() in executor/server.py22:21
corvusclarkb: we specify the full exact path to the playbook; it's not an ansible search issue22:21
clarkbgotcha22:21
corvusclarkb: (roles, however, have a search path -- but we add either the untrusted or trusted checkouts to that search path as appropriate in prepareZuulRole)22:22
*** JasonCL has joined #zuul22:35
*** JasonCL has quit IRC22:36
*** JasonCL has joined #zuul22:36
*** maeca has joined #zuul22:40
*** JasonCL has quit IRC22:41
clarkbcorvus: https://review.openstack.org/#/c/558643/8/tests/fixtures/config/role-branches/git/project1/zuul.yaml line 5, where does parent-job-pre come from?22:45
*** threestrands has joined #zuul23:02
*** weshay is now known as weshay_pto23:05
*** JasonCL has joined #zuul23:06
*** JasonCL has quit IRC23:09
*** maeca has joined #zuul23:09
*** pwhalen has quit IRC23:10
*** maeca has quit IRC23:10
*** elyezer_ has quit IRC23:11
pabelangertobiash: good points on 53568523:45
clarkbcorvus: I'ev managed to do a first pass on the second change you linked finally23:45
clarkbcorvus: mostly still trying to fully wrap my head around it and left some questions. Nothing stnads out as needing to be completely redone or anything like that though23:45
*** gouthamr has joined #zuul23:51

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