Thursday, 2018-03-29

-openstackstatus- NOTICE: Zuul has been restarted to update to the latest code; existing changes have been re-enqueued, you may need to recheck changes uploaded in the past 10 minutes00:00
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Update github payload location docs  https://review.openstack.org/55755000:15
corvuspabelanger, tobiash, mordred: ^ that should be fixed before release.00:16
pabelanger+200:16
corvusnodepool 3.0.0 tagged00:27
corvushttps://pypi.python.org/pypi/nodepool/3.0.0 exists00:31
openstackgerritMerged openstack-infra/zuul master: Update github payload location docs  https://review.openstack.org/55755000:45
corvuszuul 3.0.0 tagged00:46
pabelangerYay, congrats all00:47
jlkWOO00:50
clarkbnow to find a drink once landed00:50
pabelangerI'm doing that myself now00:51
*** odyssey4me has quit IRC00:53
*** odyssey4me has joined #zuul00:53
corvushttps://pypi.python.org/pypi/zuul/3.0.0 exists00:54
corvusi think that means we actually released this thing :)00:54
corvusi just sent an announcement to zuul-announce00:54
pabelanger++00:55
*** ChanServ sets mode: -c 00:57
jlkhey wow, guess I"ll have a bit of whiskey tonight!00:57
corvusindeed!00:57
jlkbrought home some Irish whiskey, seems like a good reason00:57
corvuslet's make it festive in here00:57
*** ChanServ changes topic to "Zuul 3.0.0 release party | Website: https://zuul-ci.org/ | Docs: https://zuul-ci.org/docs/ | Source: https://git.zuul-ci.org/ | Channel logs: http://eavesdrop.openstack.org/irclogs/%23zuul/"00:58
pabelangerYah, I see a Zuul 3.0.0 released email00:59
corvusZuul v3 is released!00:59
clarkbI think I'm 30k feet over corvus' house too00:59
corvusclarkb: cheers!00:59
clarkbcorvus: indeed!01:00
corvusokay, i'm going to go out and eat and drink, and will continue celebrating with everyone tomorrow!01:00
pabelangerwell deserved, if I don't say so myself01:01
corvusthanks everyone!01:01
*** JasonCL has quit IRC01:03
*** JasonCL has joined #zuul01:04
*** JasonCL has joined #zuul01:09
*** JasonCL has quit IRC01:11
*** JasonCL has joined #zuul01:12
*** JasonCL has quit IRC01:13
*** JasonCL has joined #zuul01:13
* fungi cheers01:18
*** JasonCL has quit IRC01:49
*** JasonCL has joined #zuul01:49
*** JasonCL has quit IRC01:54
*** JasonCL has joined #zuul01:55
*** JasonCL has quit IRC02:13
mrhillsmanwoo hoo!02:23
mrhillsmanquite late to the party but i made it :)02:23
EmilienMcongrats folks, can't wait for zuul v4 ;-)02:28
mrhillsmanlol02:30
mrhillsmansoooooo02:30
mrhillsmando not shoot darts/arrows/etc my way but i have a question/request/plead02:30
mrhillsmanwe have done quite a bit of work with k8s as some may be aware re openlab (gophercloud/terraform/cloud-provider-openstack)02:32
dmsimardcongrats everyone :D02:32
mrhillsmanopenlab using zuul of course02:32
mrhillsmanwe requested to add github app into kubernetes/cloud-provider-openstack annnnnnnnd...not going to happen as of right now02:33
mrhillsmansuggested approach is to add a driver/plugin/connector for prow+zuul02:33
mrhillsmanthere is some stuff that was done for jenkins which was mentioned as potential reference02:34
mrhillsmanhttps://github.com/kubernetes/test-infra/tree/master/prow/jenkins02:34
mrhillsmanneedless to say, it is all go02:34
mrhillsmanso asking for some eyes/minds to provide some suggestions other than having to develop a driver/plugin/connector02:35
clarkbmrhillsman: it would probably help if some of the thought behind that was provided too02:35
clarkbso that we can understand the need02:36
*** dims_ has joined #zuul02:36
mrhillsmandims should be joining in a sec to help with that02:37
clarkb(and actually address that rather than making a random plugin because someone said "no")02:37
dims_o/02:37
mrhillsmansure02:37
mrhillsmanhence my asking for thoughts/eyes on this of you all who know the things better than me02:38
dims_http://paste.openstack.org/show/716958/02:38
mrhillsmandims_ can you see the stuff i typed earlier?02:38
mrhillsmanok cool, was not sure if that was shareable02:39
dims_public slack ...02:39
dims_just was not sure if everyone here had accounts02:40
corvusso, if i understand correctly, you're offering your services as a third-party ci system for a kubernetes repo.  and they have rejected that offer because they don't like the technology you're running.02:40
corvusand that would be akin to openstack requiring all third-party ci systems to run zuul.02:40
dims_corvus : it's not a rejection, exploring options02:40
corvusin fact, we don't do that, because that's not very friendly.  we have plenty of folks running jenkins third-party ci systems reporting on openstack.02:41
tristanCyay a tag, finally :-)02:41
corvusdims_: oh, okay, i misunderstood mrhillsman's "annnnnnnnd...not going to happen as of right now"02:41
mrhillsmanhehe, yes, yes you did02:41
corvusso what is the situation?02:42
mrhillsmansorry, i should have been more tactful02:42
dims_"This would be better because a) other prow users would then have access to OpenLab CI and/or Zuul and b) it will interface better with the rest of our automation like tide (so /retest would work, for example)" <<< very valid!02:42
clarkba) would just be a matter if them adding the app too02:42
corvuswhat's "/retest" ?02:43
clarkbnot sure thats an actual concern02:43
dims_corvus : prow has a jenkins plugin. so they asked if we could look into a similar one for zuul02:46
dims_issue is here - https://github.com/kubernetes/test-infra/issues/737102:46
pabelangerif you keep your job config out of kubernetes/cloud-provider-openstack, you don't need to add the bot02:48
pabelangerwe are actually testing kubernetes-incubator/kubespray with zuul.o.o today02:48
corvuspabelanger: how so?  i suspect they'd like to report on pull requests.02:48
dims_pabelanger : can we do testing and reporting on PR(s)?02:48
dims_yes corvus02:48
mrhillsman^02:49
pabelangerright, we don't report on PRs02:49
dims_pabelanger : we need that02:49
pabelangerdims_: right, but test-infra basically said no right now02:49
dims_pabelanger : they asked me to check on something and i am here trying to do that02:50
mrhillsmandims mentioned also maybe write a zuul driver based on timer that uses github v3 notifications api02:50
pabelangerbut agree, it is pretty limiting to only say prowl for testing02:50
corvuswhat's "/retest"?02:50
dims_pabelanger : we can do periodic right away and report results to the central dashboard02:50
dims_they do want us to do that for sure02:51
mrhillsmanidk corvus - thought dims_ would be able to answer that02:51
mrhillsmani suspect it is the same as recheck02:51
*** JasonCL has joined #zuul02:52
dims_it's one of the bot commands02:52
mrhillsmanfound it02:52
mrhillsmanhttps://prow.k8s.io/command-help02:52
dims_yes like recheck02:52
mrhillsmanRerun test jobs that have failed.02:52
corvusif so, then it's probably a very small change to the pipeline config in openlab to support it; of course it's mrhillsman's decision on whether that's desirable.  but in general, i'd say that if there's a concern about matching their environment -- well, zuul is *very* configurable in that regard.02:53
corvusto put it succinctly, it's going to be way easier to add 2 lines of yaml to support "/retest" than it would be to write plugins02:53
corvusdims_, mrhillsman: i'll try to speculate on more direct answers to your question, but i have limited knowledge of prow02:54
dims_corvus : the main thing is how do we push events from prow to zuul so we could do pr(s)02:55
corvusin general, zuul has a driver interface for supporting multiple trigger sources.  it may be possible to create one that is compatible in some way with prow.  i'm not sure what form that would take -- is it push? pull?  it'll take some thought.02:55
corvussimilarly, reporters are a driver interface as well.  so it might be possible to report to prow.02:55
dims_either we write a prow plugin to send something from prow to zuul ... or just use github notifications api as the source of events to zuul02:56
corvusdims_: well, the github notification api is "install the openlab github app"02:56
pabelangeris there a passive way to get some events with installing github app?02:57
dims_not that one ... "GET /notifications" (from https://developer.github.com/v3/activity/notifications/) then they don't have to install github app or configure our webhook02:57
pabelangerwithout*02:58
dims_y pabelanger ^^02:58
corvusdims_: what's the rate limit on that?02:59
dims_pabelanger : zuul has a timer driver right, we can use that with GET /notifications?since=02:59
dims_corvus : dunno will have to check02:59
clarkbcorvus: I think all github api is 5k requests per hour02:59
mrhillsmanit would be per user yes?02:59
pabelangeryah, I guess that is the down side of not adding the app, lower rate limit?03:00
corvusmrhillsman: something like openlab could eat that *very* quickly.03:00
corvusit takes a lot of api requests to do anything with github03:00
mrhillsmanah ok03:01
*** JasonCL has quit IRC03:01
dims_create a new "bot" for each repo that we would like to be notified about?03:01
mrhillsmani thought it was a push rather than a pull03:01
corvusdims_: i think that the notification api is not going to be a good experience for users (due to the lag and the impact on requests).  there is a significant benefit to using app installs.  that's what github encourages folks like us to do.03:01
mrhillsmanwhile github app is a push03:01
dims_ack corvus . will point @fejta to this discussion03:02
dims_corvus : the other one was "if prow can talk to jenkins api, can we not write one that talks to zuul api"03:03
dims_that would be a push from prow plugin calling something in zuul03:03
corvusdims_: zuul doesn't have a generalized trigger api, yet, though it potentially could.  that's a better solution than the notifications api, however, it's still going to need to talk to github to learn about the actual PRs, so we'll run into the rate limit too.03:04
corvus(for that matter, i'd argue jenkins doesn't really have one either -- that's why we wrote the gearman plugin)03:05
corvus(it sort of has a rest api for triggering jobs, but it's gotten more and more limited over time)03:05
dims_ack thanks for the chat i think i have enough to take back to them and keep the conversation going03:07
dims_thanks pabelanger corvus clarkb03:07
mrhillsman^03:07
corvusdims_: np.  keep me posted.  :)03:07
mrhillsmansorry to interrupt the party :)03:07
dims_will do03:08
corvusdims_, mrhillsman: you *must* have a drink before you go.  :)03:08
pabelangerdims_: reading the backscroll, I didn't see a specific reason not to allow the openlab app into k8s. Might be good to better understand why that isn't liked03:08
* mrhillsman sips twice03:08
dims_ah apologies. congrats on the new release!03:08
dims_where are my manners03:08
mrhillsmani don't think it was not liked pabelanger rather than are there other options03:08
* mrhillsman puts words in bad order at times causing confusion03:09
dims_pabelanger : that's not ruled out yet, just looking for better ux for folks who already use prow infra03:09
pabelangerack03:09
corvusyeah, very valid concern -- we have the same in openstack -- we just proscribe the UX and are ambivalent about the tooling03:09
corvusdims_, mrhillsman: cheers!03:10
mrhillsmanthank you!03:10
tristanCcorvus: fwiw, https://review.openstack.org/554839 demonstrate a POST api/job/$job-name to trigger a single job03:23
*** harlowja has quit IRC03:24
tristanCthis even creates a little web form with the job variables :-)03:24
*** JasonCL has joined #zuul03:25
*** JasonCL has quit IRC03:29
openstackgerritBernd Bausch proposed openstack-infra/zuul master: Add clarity to *Zuul from Scratch* instructions  https://review.openstack.org/55634403:30
*** patriciadomin has quit IRC03:50
*** patriciadomin has joined #zuul03:51
*** bhavik1 has joined #zuul03:57
*** harlowja has joined #zuul03:59
*** jimi_|ansible is now known as jimi|ansible04:12
jimi|ansiblecongrats all :)04:13
* jimi|ansible is late to the party04:13
tobiashYay release :)04:20
openstackgerritBernd Bausch proposed openstack-infra/zuul master: Add clarity to *Zuul from Scratch* instructions  https://review.openstack.org/55634404:57
openstackgerritBernd Bausch proposed openstack-infra/zuul master: Add clarity to *Zuul from Scratch* instructions  https://review.openstack.org/55634405:27
openstackgerritJoshua Hesketh proposed openstack-infra/zuul master: Add clarity to *Zuul from Scratch* instructions  https://review.openstack.org/55634405:29
openstackgerritIan Wienand proposed openstack-infra/nodepool master: add gentoo systemd image for testing  https://review.openstack.org/55666105:37
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Test growroot in boot tests  https://review.openstack.org/55510305:37
*** harlowja has quit IRC06:06
*** flepied__ has quit IRC06:19
openstackgerritMerged openstack-infra/nodepool master: add gentoo systemd image for testing  https://review.openstack.org/55666106:31
*** flepied__ has joined #zuul06:53
*** JasonCL has joined #zuul07:43
*** JasonCL has quit IRC07:48
*** electrofelix has joined #zuul07:54
*** flepied_ has joined #zuul08:00
*** flepied__ has quit IRC08:01
*** flepied__ has joined #zuul08:02
*** flepied_ has quit IRC08:04
*** flepied_ has joined #zuul08:08
*** flepied__ has quit IRC08:10
*** flepied__ has joined #zuul08:14
*** flepied_ has quit IRC08:16
*** hashar has joined #zuul08:21
*** flepied__ has quit IRC08:32
*** sshnaidm is now known as sshnaidm|afk08:33
*** JasonCL has joined #zuul08:52
*** JasonCL has quit IRC08:57
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: zuul-changes: update for the new api url  https://review.openstack.org/55765609:13
*** JasonCL has joined #zuul10:09
*** sshnaidm|afk is now known as sshnaidm10:23
*** flepied has joined #zuul10:48
*** bhavik1 has quit IRC10:51
*** JasonCL has quit IRC11:00
tobiashjlk, corvus: found another problem with the github3.py: http://paste.openstack.org/show/717856/11:27
tobiash:(11:27
tobiashI don't know yet in which cases this occurs11:29
tobiashbut frequently inhibits changes to be enqueued11:29
tristanCtobiash: it doesn't seems to happen with public github.com11:29
tobiashtristanC: yah, that's only a problem with github enterprise11:29
electrofelixwe have a few people asking for us to support squashing instead of merging, while I might disagree with the idea, imo should consider the commit state as part of the review11:45
electrofelixbut it looks like something that will have to be done for those using github locally11:45
electrofelixwhat approach would be acceptable? make the most sense to deliver upstream?11:45
electrofelixin repo configuration option to 'merge' or 'squash' on submit?11:47
electrofelixsupport enabling of the 'squash' option only in the github repo conf and query for configured behaviour (if possible) or simply try 'squash' if 'merge' receives an error saying not allowed?11:47
electrofelixor support a second label controlling whether to 'merge' or 'squash' and perform the action depending on which label is applied?11:47
tobiashelectrofelix: you mean using githubs functionality merge with sqash?11:59
tobiashwe probably should extend the github driver that it can select the desired merge method11:59
tobiashthere is already a per repo setting of a merge mode12:00
tobiashbut I don't know if that only applies to merging in zuul or if it's also intended to select the merge method of gerrit/github12:00
electrofelixtobiash: I couldn't see that any of the code attempting to perform a squash instead of merge?12:04
electrofelixmergePull at https://github.com/openstack-infra/zuul/blob/master/zuul/driver/github/githubconnection.py#L1065 seems to be the only method called12:04
tobiashelectrofelix: yes, that's unimplemented currently12:04
electrofelixyeah, that's what I thought. we're still on zuulv2 so I was hoping to get an idea of what 'squash merge PR' might be in zuulv3 in the future so I can try and retrofit something close enough in the mean time12:05
tobiashthe github3.py supports the merge method: http://github3.readthedocs.io/en/latest/pulls.html?highlight=merge#github3.pulls.PullRequest.merge12:06
electrofelixtobiash: right, I guess I'm really trying to get a feel for what method of exposing that to github projects might be acceptable in zuulv3 to see if I can mimic it in our v2 so there is no change in behaviour or need to carry patches when we do migreate12:14
tobiashelectrofelix: I think this or a submit-mode sibling would do the job: https://zuul-ci.org/docs/zuul/user/config.html#attr-project.merge-mode12:17
tobiashso we either could link that to the driver or add a submit-mode setting to that12:17
*** elyezer has quit IRC12:33
*** elyezer has joined #zuul12:34
electrofelixtobiash: cool, so in repo control only?12:34
electrofelixs/control/config/12:34
tobiashyes, that's the idea12:34
tobiashyou already now can configure the merge behavior in zuul itself12:34
tobiashso I think it makes sense to make the submit method configurable the same way12:35
tobiashtristanC: just found out the github3.py problem is not limited to github enterprise12:42
tobiashit occurs when fetching the files from a pr and you added a large file (>3000 lines)12:43
tobiashthen github skips the patch field12:43
tobiashlike curl -s https://api.github.com/repos/tobiashenkel/sandbox/pulls/1/files | jq .12:43
electrofelixtobiash: thanks, I guess for zuulv2 it'll have to be a hack with either using the configured settings/retrying or support a custom label12:45
electrofelixtobiash: does github require a particular header to return large files? e.g. by default the web interface doesn't display large diffs either12:46
*** electrofelix has quit IRC12:46
tobiashI don't think so it just doesn't include it and you need to get the content via the content links12:47
tobiashalso this behavior doesn't seem to be documented: https://developer.github.com/v3/pulls/#list-pull-requests-files12:48
tobiashcorvus, jlk: https://github.com/sigmavirus24/github3.py/issues/81612:49
tobiashtristanC: ^12:49
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Reorganzie "Zuul From Scratch" document  https://review.openstack.org/55698812:53
*** odyssey4me has quit IRC12:57
*** odyssey4me has joined #zuul12:57
Shrewswow, i cannot spell12:59
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Reorganize "Zuul From Scratch" document  https://review.openstack.org/55698812:59
tobiashany gearman cracks here?13:00
tobiashI have a frozen zuul-web waiting for gearman response after a scheduler restart13:01
pabelangeryah, believe you still need to restart it manually13:02
tobiashthat doesn't occur every time13:02
tobiashjust sometimes13:02
tobiashnormally it just reconnects13:02
tobiashhttp://paste.openstack.org/show/717897/13:03
pabelangerwhen we stop / start scheduler on zuul.o.o we also have to do zuul-web too13:03
pabelangertobiash: is scheduler running gearman server?13:04
tobiashyes13:04
pabelangerwork around would be to use geard, but yah we need to fix it13:04
tobiashah, ok so I'll work around that with liveness probes for now :)13:05
pabelangeryah, believe so. we might be able to reproduce with unit test too13:08
pabelangertobiash: github question, are you using exclude-unprotected-branches setting at all? https://zuul-ci.org/docs/zuul/admin/tenants.html#attr-tenant.exclude-unprotected-branches13:08
tobiashpabelanger: I use that for all github repos13:08
tobiashit's crucion if you don't work with forking13:09
pabelangerkk, that's what I figured13:09
pabelangercurious why it is disabled by default13:09
tobiashin github enterprise the more common working model is just branching and pr13:09
tobiashit's disabled by default because of the common work pattern fork&pull on github.com13:10
pabelangerah, so this will not allow that?13:11
tobiashI'm not sure if that really makes sense but I'm ok with that and just set it on every tenant13:11
tobiashwith fork&pull it's not really an issue because the speculative source is in a different repo (which is not known by zuul)13:12
pabelangeryah13:12
tobiashbut as soon as you allow branch&pull it's an issue13:12
pabelangeryes, that is what happening now. branches are getting created on project zuul is on, then PR from it, which is breaking zuul config13:12
pabelangerAs I understood, branch protection and this setting help protect that13:13
tobiashyes13:13
pabelanger++13:13
pabelangerthank you13:13
tobiashenable branch protection and this setting and zuul will ignore any config in a non protected branch13:13
tobiashyou even can set this per repo btw13:13
pabelangeryah, I think we can do that to test13:14
*** flepied_ has joined #zuul13:28
*** flepied has quit IRC13:31
*** JasonCL has joined #zuul13:48
*** JasonCL has quit IRC13:52
*** JasonCL has joined #zuul13:52
openstackgerritMerged openstack-infra/zuul-jobs master: Fix ansible-lint job  https://review.openstack.org/55750713:52
*** JasonCL has quit IRC13:55
*** JasonCL has joined #zuul13:56
*** JasonCL has quit IRC13:58
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Upgrade from angularjs (v1) to angular (v5)  https://review.openstack.org/55198913:59
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Use glyphicons for status balls  https://review.openstack.org/55199213:59
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Stop falling back to job name for missing url  https://review.openstack.org/55405613:59
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Remove dashboard workaround for missing log_url  https://review.openstack.org/55406613:59
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Add zuul-build-dashboard-multi-tenant  https://review.openstack.org/55771313:59
*** flepied__ has joined #zuul14:07
*** JasonCL has joined #zuul14:07
*** flepied_ has quit IRC14:09
*** dkranz has joined #zuul14:12
*** JasonCL has quit IRC14:12
*** JasonCL has joined #zuul14:13
dmsimardmordred: the new glyphicons look nice!14:15
*** jlvillal has quit IRC14:15
dmsimardit looks like some of them could be pushed up just a tiny bit (2-3 pixels?), triggered my OCD https://i.imgur.com/M0J6yLT.png14:17
*** JasonCL has quit IRC14:24
ShrewsAm I so far removed from web dev that I've never heard the term "glyphicon" before? I think I'm happy about that14:28
*** JasonCL has joined #zuul14:29
*** flepied_ has joined #zuul14:30
*** maeca has joined #zuul14:33
*** flepied__ has quit IRC14:33
*** JasonCL has quit IRC14:35
mordredShrews: :)14:37
mordredShrews: it's the web-dev version of windings - a font that contains a set of symbols you can use for things without having to use image files14:38
mordredShrews: I put up a patch suggesting we use them instead of the balls on the status page: http://logs.openstack.org/92/551992/11/check/zuul-build-dashboard/373e86e/npm/html/status.html14:40
pabelangertobiash: mind a review on https://review.openstack.org/556624/ since we talked about it the other day14:42
pabelangerShrews: may you also ^14:42
Shrewspabelanger: do host keys ever get populated in our tests?14:52
Shrewsoh yes, i see the test above expects them14:53
pabelangeryah14:53
Shrewspabelanger: 1 minor suggestion14:56
Shrewsotherwise lgtm14:57
*** JasonCL has joined #zuul14:57
*** bramwelt has quit IRC14:58
pabelangerk14:58
Shrewspabelanger: oh! ignore that15:00
Shrewspabelanger: i didn't realize that it was already under the OpenStack driver section15:00
pabelangernp15:00
Shrews+2'd15:01
*** JasonCL has quit IRC15:01
*** JasonCL has joined #zuul15:02
*** JasonCL has quit IRC15:04
pabelangertyty15:04
*** JasonCL has joined #zuul15:04
SpamapS^5's to everyone for the 3.0.0 release! :-D15:06
*** JasonCL has quit IRC15:06
* SpamapS goes back into the salt mine15:06
*** JasonCL has joined #zuul15:08
*** JasonCL has quit IRC15:11
*** JasonCL has joined #zuul15:11
*** jlvillal has joined #zuul15:12
ShrewsHow do folks feel about splitting up the "Zuul From Scratch" doc into separate docs for different distros/configurations, as I've suggested here: http://logs.openstack.org/88/556988/3/check/build-sphinx-docs/23aea68/html/admin/zuul-from-scratch.html15:13
ShrewsI'd like to begin adding docs for a static nodepool, and a gerrit setup, and possibly some ubuntu specific setup15:13
Shrewsalternative, we could just do an entirely separate document15:14
Shrewsbut there is enough in common, this felt like the better way15:14
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Update pypi metadata  https://review.openstack.org/55773815:14
pabelangerShrews: corvus: is ^ the correct metadata now? Not that I'm trying to remove the accomplishments of the openstack infra team15:16
corvusShrews: openstack was unable to muster the resources to keep all of the installation methods up to date15:17
corvus(i mean documentation of all the methods)15:18
*** JasonCL has quit IRC15:18
corvusi worry that as soon as we add a second, the first will be out of date.  i'm not saying we should always stick with fedora27 (after all, it'll be out of date automatically in a few months?)15:19
Shrewscaveat emptor15:19
corvusbut i wonder whether having a fedora and ubuntu section is sustainable15:19
corvus(especially since the differences are not significant)15:20
Shrewscorvus: i'm less enthusiastic about the distro part. it's the nodepool driver and repo backends i'd like to see some docs for15:20
corvus(though now that i look at it, what, we only have like 10 lines of fedora-specific stuff in there?  maybe i'm over thinking this :)15:21
corvusShrews: oh, maybe i misunderstood your question15:21
ShrewsIf someone wants to try zuul, but doesn't have access to an openstack cloud, showing how to setup the static driver with some VMs could be valuable.15:21
corvusShrews: i wholeheartedly agree there.  i definitely think we should add that15:22
ShrewsAnd there was LOTS I learned about gerrit trying to set it up myself (stuff we don't have documented)15:22
Shrewsjust need someplace to vomit my learnings15:22
ShrewsI can leave the fedora stuff as-is15:23
corvusShrews: i think i'd like to walk back what i said about fedora/ubuntu; cause i think i like your change as is15:23
corvusShrews: and that has me wondering if we should move everything in zuul-from-scratch.rst into its own pages, so you're only looking at one section at a time.15:27
corvusShrews: (ie, move "zuul and nodepool installation" into a page, etc)15:27
Shrewscorvus: i'm open to whatever seems best. That might make the entire doc easier to follow15:29
corvusShrews: i'm +2 on the current change, we can continue down that path in a followup if you want15:29
Shrewsi noticed some open reviews from others for that doc, so maybe we should land those first and then i can rework mine?15:30
corvusShrews: probably a good idea -- https://review.openstack.org/556344 ?15:30
Shrewscorvus: yeah15:31
corvusShrews: i'm reviewing that now15:31
Shrews"For experimentation, DevStack is fine" ---  LOL, good luck with that if you try to run it in a separate vm15:34
Shrewsi wasted so many hours trying to get that to work15:34
clarkbcorvus: Shrews re install docs my personal opinion on that is don't specify a distro at all. Install zookeeper from upstream tarball and zuul to a virtualenv. Bindep will mostly let us hand wave around the distro differences in this case I think15:35
Shrewsclarkb: yeah, i'd prefer if we had never assumed a particular distro for that15:36
corvusclarkb: yeah, we're basically there already.  http://logs.openstack.org/88/556988/3/check/build-sphinx-docs/23aea68/html/admin/fedora27_setup.html15:36
corvusclarkb: it's only the top 3 blockquotes which are distro specific15:36
clarkbmaybe assume systemd so that you can copy the zk init scripts to the right location and systemctl daemon-reload. But that should be mostly safe at this point as most distros are using it (even gentoo has an option for systemd)15:37
Shrewsi think we can split the service management stuff out too15:37
corvusclarkb: fedora and ubuntu provide zookeeper packages though, i think it's friendlier to new users to tell them to use those.15:38
corvusclarkb: yeah, we do use systemd15:38
corvusShrews: and yes, we can probably carry those files in zuul somewhere; that will reduce the bulk of the instructions nicely15:38
Shrewscorvus: ooh, that would be nice15:38
corvusclarkb: maybe we can re-order the bindep stuff so that the "sudo dnf install git redhat-lsb-core python3 python3-pip python3-devel make gcc openssl-devel python-openstackclient -y" step isn't necessary.15:39
clarkbcorvus: ya bindep just needs a python install (2 or 3) and lsb_release maybe we can specify those are dependencies then go from there assuming bindep?15:40
pabelanger+115:40
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Upgrade to webpack 4  https://review.openstack.org/55198715:41
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Upgrade from angularjs (v1) to angular (v5)  https://review.openstack.org/55198915:41
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Use glyphicons for status balls  https://review.openstack.org/55199215:41
corvusclarkb: i bet "dnf install python lsb_release" or "apt install python lsb_release" won't be too hard for us to maintain15:43
corvusonce we get that down to the minimum15:43
corvusShrews, mrhillsman: i left questions on https://review.openstack.org/556344 -- perhaps as recent users of that, you can offer insight15:44
corvusclarkb: ^15:44
Shrewscorvus: yeah saw those. i do not have answers though  :(15:45
Shrewsand i actually never "used" that doc since i did something TOTALLY different (ran from git repos and used gerrit)15:46
mrhillsmansure thing corvus15:46
*** JasonCL has joined #zuul15:47
mrhillsmanas a general blanket statement i take zuul from scratch as the thing i should use to deploy something i can expect to use in production15:47
Shrewsmrhillsman: you would recommend an all-in-one for production?15:47
mrhillsmanand getting started as a quick start allinone just want to try out and get up and running15:47
corvusShrews: aio for prod should be fine15:48
corvusit's a matter of scale, not sustainability15:48
corvusmrhillsman: i think the thing trying to be conveyed by the name was that it would walk you through the whole process, without the crutches of any pre-made images, etc.15:48
mrhillsmanand getting started as a quick start just want to try out and get up and running15:49
mrhillsmanyes15:49
clarkbcorvus: ++ one of my biggest gripes with the move to automagic container images is you never learn how anything works (and consequently have little idea of where to look when things break)15:49
mrhillsmanand of course it can grow as noted by the disclaimer at the top15:49
mrhillsmanjust a quick skim of the review15:50
corvusclarkb: yeah, a thing leifmadsen says is that, at some point, you need the documentation that the person making the container images uses to figure out what they need to do15:50
mrhillsmani think some of the things there are because of some pieces being too specific15:50
mrhillsmani.e. useradd vs adduser15:50
*** JasonCL has quit IRC15:50
corvusi don't understand that one -- i'm pretty sure i copy/pasted that when i ran through; is adduser wrong?15:52
mrhillsmani don't know what bernd used15:52
mrhillsmanbut i used ubuntu15:52
mrhillsmanand adduser was/is not available15:52
mrhillsmani did not try to install it because i knew to use useradd :)15:53
corvusmrhillsman: it's available in the adduser package on ubuntu15:53
mrhillsmanunfortunately i have not got to spend another iteration of zfs15:54
Shrewsi have both available on my ubuntu15:54
mrhillsmanbut an example i have in the notes i think will help me explain better15:54
mrhillsmanhttps://etherpad.openstack.org/p/zuul-quickstart-and-zfs(zuul-from-scratch)15:54
mrhillsmanunder the Section: Environment Setup15:54
corvusbut that's a good thing to know.  perhaps bernd also used ubuntu.  the instructions are currently for fedora.  i'm in favor of normalizing the instructions to support both, but we need to be clear about what we're doing.  we can't just switch between the two and end up with a document that says "use fedora and run this ubuntu command"15:54
*** JasonCL has joined #zuul15:54
mrhillsmanlike the package names for fedora of course are different than ubuntu and some others i am sure15:54
mrhillsmanso if you look at that etherpad15:55
mrhillsmani hoped to go through sections and do stuff like that section15:55
mrhillsmanmore generic info even though fedora is used15:56
mrhillsmanwindows and macos may never be supported/able to be used, but i was basically trying to make that statement15:57
mrhillsmanyou need these packages, however you get them, you should know15:57
corvusmrhillsman: yeah, we discussed minimizing ways to minimize the packages section earlier (15:38)15:58
mrhillsmanzuul and nodepool install pieces could explain why you need the users and the home dirs where they are vs /home/$USER15:59
mrhillsmani say that based on doing install without these instructions and getting perms errors from the executor15:59
corvusmrhillsman: you're going to push up changes at some point, right?  :)15:59
mrhillsmanyes sir15:59
mrhillsmanwhat i will do is reach out to bernd and lxj to maybe explain what i was hoping to do with that etherpad16:00
mrhillsmanit got out of control quickly lol16:00
leifmadsenI say what? lol16:00
corvusmrhillsman: we can discuss the specifics in code review pretty easily, but if we want to schedule a call with folks to talk about the notes in the etherpad, that works too.  that might work for getting the big picture.16:01
corvusleifmadsen: important sensible things :)16:01
leifmadsensounds wrong16:01
leifmadsenI assume you meant someone else16:01
mrhillsmani got to the section about zuul and nodepool and started just taking some quick notes via ## to come back and do the same as i was doing with the environment setup section16:02
mrhillsmanyeah16:02
mrhillsmani think getting the big picture is important16:02
mrhillsmanbecause some of those changes you commented on i think were done by bernd because of being specific to his setup16:02
pabelangerShrews: what size was your all-in-one instance? So far 8GB seems to work in my local testing, with a large HDD16:03
pabelanger8GB ram I should say16:03
Shrewspabelanger: 64GB  :)16:03
pabelangerHA16:03
mrhillsmanhehe16:03
Shrewsit's my monster machine16:03
mrhillsmani use 3 tiny instances16:03
mrhillsmanjust like to keep things separate; want to separate them even more16:04
pabelanger++16:04
pabelangeransible makes that easy with group_vars too16:05
mrhillsmancorvus i will reply to the review16:05
Shrewsi was originally going to do vms (1 per service), but i gave up on that pretty quickly16:05
mrhillsmanand i think there is a thread on zuul-discuss so i can respond to that16:05
mrhillsmanah, it's not that bad :)16:06
pabelangercorvus: I'd also love to discus our playbook / role story for zuul / nodepool deployments too. When every you think that is appropriate.16:06
mrhillsmani am using containers right now and they are working fine16:06
corvusi could see us adding a note saying "open these ports if you want to run the servers on separate hosts".  but i definitely think aio is a legit use-case, and we don't wan to scare new folks off by giving them the impression they need to run on an openstack scale server farm.  :)16:06
pabelangermrhillsman: which container tech?16:07
mrhillsmanplain old docker via lxd16:07
mrhillsmansorry, plain old lxc via lxd16:07
mrhillsmanor whatever lol16:07
mrhillsmanlxc16:07
Shrewscorvus: i'm surprised we'd recommend an aio, but i guess we've never really mapped out how much resources are required. i just assumed "a lot"16:07
pabelangerah, I've had some early success using this http://git.openstack.org/cgit/openstack/openstack-ansible-plugins/tree/connection/ssh.py plugin that OSA used to manage lxc / systemd-nspawn containers on a remote nodes with ansible.16:07
pabelangerjust add a few magic variables into an inventory file, and now things are installed into system containers on the remove node16:08
pabelangerremote*16:08
mrhillsmanmaybe we can address that with something like16:08
mrhillsmanaio setups are perfectly valid even for production16:09
corvusShrews: not much, actually -- it scales with the size of the system.  i think a single 8G vm should be plenty for a 'workgroup-sized' deployment16:09
*** acozine1 has joined #zuul16:09
corvusShrews: but yeah, we should quantify that :)16:09
corvusmaybe i still have my server up...16:09
mrhillsmanright16:09
Shrewsperhaps we should say that somewhere16:09
pabelangermrhillsman: yah, I've been testing with single node, but into virtualenvs for services. Not production, but works well in my local 3rd party CI16:09
pabelangermrhillsman: http://paste.openstack.org/show/717920/ is an example inventory file to create gear01 in a lxc container on bm0116:10
pabelangerusing the connection plugin above16:10
mrhillsmannice16:11
pabelangerOSA has some pretty nice things around lxc16:11
corvusShrews: when i went through the ZfS guide, i did so on a 4G vm which currently has 1G of ram used.16:11
corvusthat's running scheduler, web, executor.16:11
Shrewsit's the java things (gerrit, zk) that i wondered about16:12
corvusoh, also running zk16:12
corvusit is not running gerrit16:12
pabelangerwhat are thought of using review-dev.o.o or gerrithub.io for gerrit example bits? Rather then deployment guide of gerrit?16:13
corvuspabelanger: that could end up with folks stepping on each others toes, since it's not easy to create new projects16:14
pabelangerdidn't think of that16:15
SpamapSShrews: regarding your docs split up.. I'd basically like to have two versions.. 1 "the distro way" and 2 "the container way"16:15
SpamapSI'd really like to move my Zuul into Kubernetes at some point.16:16
mrhillsman^16:18
mrhillsmanwell, not k8s necessarily hehe16:18
Shrewspabelanger: also, there are important pieces in setting up gerrit that we don't document anywhere (ACLs, pipeline label mapping)16:18
mrhillsmanbut would love to be able to deploy zuul via containers16:18
pabelangerShrews: traditionally that's been https://docs.openstack.org/infra/system-config/gerrit.html16:19
mrhillsmani think it is ok to remove github from ZfS16:19
pabelangerbut agree, we docs for gerrit16:20
mrhillsmanand put at top of github page16:20
mrhillsmanand then be like, at this point your zuul is ready to do its job16:21
Shrewspabelanger: that really didn't help me much for my setup. we should have something internal to zuul docs16:21
mrhillsmannext steps - connector (link link link), reporter (link link link), etc whatever, but your ZfS is done16:21
corvusSpamapS: i have a todo item to write up how we'll build images; once we have that, we can start building docs around it.  hopefully now that we released, i'll have time to do that writeup next week.16:22
clarkbShrews: maybe there is an upstream gerrit doc we can link to? (I've not actually looked)16:22
corvusmrhillsman: well, the idea was to walk all the way through getting a job to run and report, somewhere.16:22
Shrewsclarkb: for... ?16:22
clarkbShrews: for installing gerrit16:22
corvusShrews, clarkb: last i looked, upstream gerrit's "here's how to set this up in dev" was really good and short.16:23
Shrewsclarkb: oh, installing gerrit was not the problem16:23
clarkbShrews: then zuul only has to deal with make sure stream events acl is set for your user and so on16:23
mrhillsmangotcha16:23
corvusShrews, clarkb: last i looked was 7 years ago.16:23
Shrewsit was linking gerrit and zuul that was the issue16:23
corvusShrews, clarkb: i assume it's only gotten better and shorter since then :)16:23
clarkbShrews: gotcha16:23
corvusSpamapS: btw, we released.  welcome to the party!16:24
* Shrews celebrates with lunch. bbl16:24
*** flepied__ has joined #zuul16:25
*** flepied_ has quit IRC16:27
SpamapScorvus: I saw, congrats, and thanks, and hooray!16:30
*** JasonCL has quit IRC16:36
*** JasonCL has joined #zuul16:38
*** JasonCL has quit IRC16:43
tobiashcorvus, jlk: created a pr to fix that new github3.py issue: https://github.com/sigmavirus24/github3.py/pull/81716:48
*** JasonCL has joined #zuul16:49
*** sshnaidm has quit IRC16:50
corvustobiash: ++16:50
*** JasonCL has quit IRC16:55
*** JasonCL has joined #zuul16:56
*** JasonCL has quit IRC16:57
openstackgerritMerged openstack-infra/nodepool master: Add host-key-checking option to openstack providers  https://review.openstack.org/55662417:00
fdegircongrats all!17:04
pabelangerfdegir: thanks!17:05
fdegirjust saying, I will be coming back with more questions and hopefully contributions as well17:07
fdegirI can't say how much important zuul is17:07
corvusfdegir: thanks! i love both of those!17:07
*** JasonCL has joined #zuul17:08
*** JasonCL has quit IRC17:13
rcarrillocruzfolks, on PTO this week17:15
rcarrillocruzcongrats on v3 release, great work. Ansible network salutes you!17:15
rcarrillocruzmordred: does it mean you got all the zuul-web stuff in? haven't followed latest changes17:15
clarkbrcarrillocruz: I think the api changing stuff all got it17:16
clarkb*got in17:16
clarkbrcarrillocruz: but there are other items that weren't going to rpesent compatibility issues that were deferred17:16
rcarrillocruzok17:16
mordredrcarrillocruz: what clarkb said17:16
*** JasonCL has joined #zuul17:18
*** JasonCL has quit IRC17:19
*** elyezer has quit IRC17:19
pabelangerrcarrillocruz: host-key-checking for nodepool above ^17:22
*** flepied__ has quit IRC17:22
*** JasonCL has joined #zuul17:22
rcarrillocruzah nice17:23
*** JasonCL has quit IRC17:30
*** elyezer has joined #zuul17:32
*** JasonCL has joined #zuul17:41
*** JasonCL has quit IRC17:47
*** JasonCL has joined #zuul17:56
*** JasonCL has quit IRC17:58
*** JasonCL has joined #zuul17:59
*** flepied__ has joined #zuul18:01
*** harlowja has joined #zuul18:01
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Reduce logging in _cleanupCurrentProviderUploads function  https://review.openstack.org/55779118:17
pabelangerShrews: tobiash: corvus: ^noticed on nb01.o.o we are filling INFO logs with those statements. I think dropping them to debug might be more appropriate18:18
*** JasonCL has quit IRC18:21
*** mugsie has joined #zuul18:22
clarkbThis channel may be interested as well, I've sent an email to the openstack-infra list with a recap of the cross community infra/ci/cd event from last weekend18:26
pabelangerclarkb: As somebody who didn't attend, thank you18:32
clarkbhttp://lists.openstack.org/pipermail/openstack-infra/2018-March/005887.html should you not already be subscribed18:32
*** sshnaidm has joined #zuul18:37
*** JasonCL has joined #zuul18:38
gundalowHi all, where can I see the defination of centos-oci, in particular I'm interested in which version of Python are available18:41
gundalow(nodeset)18:42
clarkbgundalow: it will be in the nodepool config for your zuul. I lack context for what that zuul might be though18:42
*** gouthamr has joined #zuul18:43
clarkbgundalow: in the nodepool config it will either be configured to boot a predefined image or have disk image builder elements listed for building an image in nodepool direclty18:43
gundalowclarkb: ah, yes, the nodeset is just a pointer to a something in nodepool, thanks18:44
clarkbthat said isn't centos 7 effectively python2.7 only?18:44
clarkbyou can use software collections but any time tripleo brings that up everyone says its not practical18:44
*** flepied__ has quit IRC18:47
gundalowah, good point. I forgot centos 7 doesn't have py3. I'll stick with what I have for the moment and once I get further on maybe look at building my own image with all the tooling I need18:48
gundalowclarkb: Thanks :)18:49
pabelangerYah, we do fedora-27 currently to pick up python3 in openstack-infra18:49
*** JasonCL has quit IRC19:00
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Reduce logging in _cleanupCurrentProviderUploads function  https://review.openstack.org/55779119:00
*** JasonCL has joined #zuul19:04
*** JasonCL has quit IRC19:04
*** JasonCL has joined #zuul19:05
*** JasonCL_ has joined #zuul19:06
*** flepied__ has joined #zuul19:08
*** JasonCL has quit IRC19:09
*** JasonCL_ has quit IRC19:11
clarkbcorvus: I'm going to review the changes to add reno now. Will likely approve them. Please yell if you don't want them approved yet19:26
clarkbshrews acked the nodepool change so decided enough +2s on that one and approved it. Now to the zuul change which looks a bit more involved19:29
Shrewsclarkb: *nod*19:29
pabelangertobiash: do you have an example gate pipeline for github? Would like to compare with SF if possible, trying to debug an issue19:30
SpamapSI have one for GHE19:30
*** weshay is now known as weshay_brb19:30
*** weshay_brb is now known as weshay19:31
pabelangerSpamapS: great19:31
SpamapSpabelanger: http://paste.openstack.org/show/717939/ <-- but I may be weird.. I only gate on the 'approved' label19:31
SpamapShttp://paste.openstack.org/show/717940/ <-- those keep that sane19:32
clarkbShrews: were you interested in also reviewing the zuul change?19:32
Shrewsclarkb: just did19:32
Shrewslgtm19:32
SpamapSBTW it would be good to have a way to suppress those utility pipelines from the status page.19:32
clarkbShrews: oh nice gerrit says we +2'd at the same time19:32
clarkbI'm just going to go ahead and approve thato ne now as I think we have good consensu19:33
Shrewsclarkb: we are, like, in sync and stuff19:33
Shrews:-P19:33
Shrewsi double approved, in case there was any doubts19:33
SpamapSpabelanger: also 0259b1d083a4ecm is the github user that zuul uses, in case you are wondering.19:34
pabelangerSpamapS: thanks, trying to digest the info19:35
pabelangerreally helpful19:35
SpamapSYeah, there's a bit that is very us-specific there19:35
openstackgerritMerged openstack-infra/nodepool master: Add reno releasenotes support  https://review.openstack.org/53686119:36
pabelangerSpamapS: thanks, line 16 is what we are missing: http://paste.openstack.org/show/717939/19:42
pabelangerif I understand, that is applied when somebody clicks approve right?19:43
*** gouthamr has quit IRC19:44
*** JasonCL has joined #zuul19:45
*** JasonCL has quit IRC19:46
SpamapSpabelanger: nope, that is when you add a label named approved19:47
SpamapSpabelanger: if you want to rely on *reviews*, use http://paste.openstack.org/show/717940/ 41-4319:48
SpamapSpabelanger: we use label, so that people can self-approve19:48
SpamapSsince github won't let you approve your own change19:48
SpamapSand then we use that pipeline to add the approved label if an admin approves19:48
pabelangerI see19:48
*** JasonCL has joined #zuul19:49
pabelangerand, crazy question, how can I tell is a PR is approved, by looking at github UI?19:49
pabelangereg: https://github.com/ansible-network/ansible-zuul-jobs/pull/419:50
*** JasonCL has quit IRC19:51
*** JasonCL has joined #zuul19:55
*** JasonCL has quit IRC19:56
*** dkranz has quit IRC19:57
pabelangerokay, I see it now19:59
pabelangerbig green check, with <user> approved these changes19:59
*** hashar is now known as quibble19:59
pabelangerthanks, I'll have somebody look into scheduler logs and see what happened19:59
*** JasonCL has joined #zuul20:00
*** JasonCL has quit IRC20:02
dmsimardI know we had discussed the deprecation and removal of a role in zuul-jobs but I forget what we had agreed on20:03
clarkbdmsimard: zuul list next steps email has outline of process for stuff like that20:04
dmsimardoh? I saw the mail but haven't read it yet, looking.20:04
dmsimarddoesn't go into the details at least as far as zuul-jobs is concerned20:05
* dmsimard search his irc logs20:05
corvusdmsimard: talking about the ara role?  maybe just leave it there -- after all, it's still a valid way to use ara, right?20:06
openstackgerritMerged openstack-infra/zuul master: Use reno for release notes  https://review.openstack.org/26259720:07
dmsimardcorvus: new role is backwards compatible with same defaults as emit-ara-html -- you could say it's a rename of the role because it does more than just html and had additional functionality20:08
corvusdmsimard: ack; then i'd suggest sending a note to zuul-announce, wait a few weeks, then remove.  how's that sound?20:09
dmsimardcorvus: yeah, I planned on at least including a note in the role README and a debug task to warn about the deprecation notice but I don't expect everyone to actually notice20:09
corvusdmsimard: maybe make the subject really clear, like: Deprecating emit-ara-html role in zuul-jobs20:10
corvusdmsimard: that sounds good too20:10
dmsimardfwiw I was already preparing an email to openstack-dev, doing one for zuul-announce is good too. Does everyone have posting rights there ?20:10
corvusdmsimard: it's fully moderated; the intent is for it to be a communication channel for the software and the zuul-jobs repos, so i think it's appropriate.  i'll moderate it through20:11
dmsimardack20:11
*** JasonCL has joined #zuul20:12
pabelangertobiash: looks like we are seeing http://paste.openstack.org/show/717856/ on zuul.o.o too, just noticed it by chance20:14
*** JasonCL has quit IRC20:15
*** JasonCL has joined #zuul20:16
*** flepied__ has quit IRC20:21
*** flepied has joined #zuul20:22
*** JasonCL has quit IRC20:24
*** JasonCL has joined #zuul20:27
openstackgerritDavid Moreau Simard proposed openstack-infra/zuul-jobs master: Deprecate the emit-ara-html role  https://review.openstack.org/55782420:32
*** JasonCL has quit IRC20:33
*** JasonCL has joined #zuul20:36
*** JasonCL has quit IRC20:38
*** JasonCL has joined #zuul20:42
SpamapSFor us, and ARA, I've thought about having our runs feed into a live ARA db20:43
SpamapSright now we're doing the emit-ara-html method, but it would be pretty nice to be able to hit a live ARA and see the ongoing jobs20:43
*** JasonCL has quit IRC20:47
openstackgerritMike Fedosin proposed openstack-infra/zuul master: Set default speed_limit and speed_time for the merger  https://review.openstack.org/55782620:47
*** quibble has quit IRC20:56
dmsimardSpamapS: yeah there are (as you know) certain constraints/limitations in doing that with the current version of ARA but it'll be easier with 1.0, promise21:02
dmsimardcorvus: how does that sound ? https://etherpad.openstack.org/p/GEOCeAuKhU21:02
*** flepied has quit IRC21:04
*** JasonCL has joined #zuul21:12
*** JasonCL has quit IRC21:21
*** JasonCL has joined #zuul21:22
SpamapSdmsimard: do you want/need help with 1.0?21:24
dmsimardSpamapS: wouldn't turn that down at all21:25
dmsimardSpamapS: I'm working on settling the new 1.0 stuff in place, happy to chat about it sometime next week -- planning some time during this 4 day weekend21:26
dmsimardtl;dr, I threw away ~6 months of on/off work I had put towards 1.0 and went with a different technology stack21:26
*** JasonCL has quit IRC21:30
*** JasonCL has joined #zuul21:36
*** JasonCL has quit IRC21:37
*** elyezer has quit IRC22:01
*** elyezer has joined #zuul22:02
*** dvn has joined #zuul22:07
*** acozine1 has quit IRC22:22
dmsimardcorvus: I ended up sending a slightly different version to zuul-announce since I'm EOD, feel free to moderate it if there's anything wrong with it22:35
openstackgerritMerged openstack-infra/zuul-jobs master: Deprecate the emit-ara-html role  https://review.openstack.org/55782422:48
corvusdmsimard: lgtm, thanks!22:56
*** ChanServ sets mode: +c 22:57
*** ChanServ changes topic to "Discussion of the project gating system Zuul | Website: https://zuul-ci.org/ | Docs: https://zuul-ci.org/docs/ | Source: https://git.zuul-ci.org/ | Channel logs: http://eavesdrop.openstack.org/irclogs/%23zuul/"22:58
*** JasonCL has joined #zuul23:06
*** JasonCL has quit IRC23:07
clarkbcorvus: https://storyboard.openstack.org/#!/story/2001392 can be closed I Think23:58

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