Monday, 2019-01-07

*** bhavikdbavishi has joined #zuul01:47
*** bhavikdbavishi has quit IRC02:37
*** bhavikdbavishi has joined #zuul03:55
*** bhavikdbavishi has quit IRC04:02
*** bhavikdbavishi has joined #zuul04:02
*** bjackman has joined #zuul05:48
*** bhavikdbavishi has quit IRC06:05
*** bjackman has quit IRC06:10
*** bjackman has joined #zuul06:26
*** AJaeger has quit IRC07:11
*** AJaeger has joined #zuul07:20
*** bhavikdbavishi has joined #zuul07:24
*** pcaruana has joined #zuul08:14
*** pcaruana has quit IRC08:24
*** rcarrillocruz has joined #zuul08:45
*** pcaruana has joined #zuul08:46
*** hashar has joined #zuul09:08
*** gtema has joined #zuul09:12
*** ssbarnea|bkp2 has joined #zuul09:37
*** ssbarnea has quit IRC09:39
tristanCjhesketh: would you mind if we rebase and continue the work on topic:freeze_job ?09:44
jheskethtristanC: not at all. I have a partial rebase, but it's probably outdated enough that I would just begin rebasing again09:46
jheskethtristanC: was there a part in particular you wanted to look at ?09:47
tristanCjhesketh: getting to the point where there is a documentation about how to run a job locally :)09:49
tristanCjhesketh: i mean, using the zuul-runner utility you proposed in that freeze_job topic09:51
tristanCif it's ok for you, we may allocate some time and work on this starting next week09:52
jheskethtristanC: sure, that'd be awesome. Hopefully the general direction and framework is there enough.09:56
jheskethIt should be pretty close to a kind of PoC for getting playbooks that can then be ran with some manual work around inventories and images09:57
tristanCjhesketh: yes, the stack looks great already, i'd like to give it a try and fix ci on the way09:58
jheskethCool :-)09:59
*** hashar has quit IRC10:02
*** hashar has joined #zuul10:06
*** bhavikdbavishi has quit IRC10:21
openstackgerritMerged openstack-infra/zuul master: dict_object.keys() is not required for *in* operator  https://review.openstack.org/62148210:27
*** sshnaidm|off is now known as sshnaidm10:30
*** arxcruz|brb is now known as arxcruz10:35
*** pcaruana has quit IRC11:11
*** pcaruana has joined #zuul11:16
*** hashar has quit IRC11:41
tobiashtristanC: is the swagger.json hand written or somehow generated?11:47
jheskethtobiash: there are tools that will help generate it, but afaik we aren't using any of those. So unless tristanC hacked something together to generate it my guess is that it would be hand written11:53
tobiashjhesketh: thanks11:53
jheskethwe should consider our options for deeper integration with it though. swagger could go in either direction. That is, either generated from our code, or we could have our routing defined by swagger.json11:53
jheskethI'd like to see something like that as it'll help ensure that our documentation reflects reality. However, all options (including manually writing obviously) have drawbacks11:54
*** bhavikdbavishi has joined #zuul11:54
tobiashhrm, ok, the current version of 535541 doesn't really seem to test the schema against the api11:55
tristanCtobiash: i wrote the initial swagger file in earlier patchset in yaml, and converted in json in later patchset so that it's part of the public file11:56
tobiashI fear that if we add such a detailed documentation without any coupling or testing it will become outdated pretty quickly11:57
* SpamapS would love to see that doc in-code somehow.12:00
tristanCtobiash: agreed, perhaps we could use something like https://github.com/apigee-127/sway to validate the reference12:01
tristanCSpamapS: that swagger file could probably be constructed from class method docstring12:01
tristanCnote that the initial goal was just to document what we have... :)12:02
SpamapStristanC: yeah that's what I was hoping.12:03
SpamapSbut, honestly, hand-written and mostly up to date is great12:03
jheskethI think there may have been a reason that doing it in the docstring wasn't straight forward. It might be due to the way we construct the routes. However, if we can move it into docstrings that would be awesome12:05
*** dkehn has quit IRC12:21
*** zigo has quit IRC12:31
*** bhavikdbavishi has quit IRC12:32
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Extract common config parsing for ProviderConfig  https://review.openstack.org/62509412:34
*** rlandy has joined #zuul12:42
*** gtema has quit IRC12:43
SpamapSFYI: https://www.vectorlogo.zone/logos/zuul-ci/index.html we exist! :-D12:46
*** gtema has joined #zuul12:47
*** evrardjp has joined #zuul12:54
*** bjackman has quit IRC12:55
*** evrardjp has quit IRC12:59
*** evrardjp has joined #zuul12:59
*** jhesketh has quit IRC13:05
*** bjackman has joined #zuul13:05
*** jhesketh has joined #zuul13:06
*** hashar has joined #zuul13:24
*** gtema has quit IRC13:34
*** gtema has joined #zuul13:44
openstackgerritMonty Taylor proposed openstack-infra/zuul-base-jobs master: Add fetch-output to base jobs  https://review.openstack.org/62897514:07
openstackgerritMonty Taylor proposed openstack-infra/zuul-base-jobs master: Ignore errors on ssh key removal  https://review.openstack.org/62897614:07
*** irclogbot_3 has quit IRC14:14
*** gtema has quit IRC14:25
*** needsleep is now known as TheJulia14:36
*** irclogbot_3 has joined #zuul14:41
mordredtristanC: btw - I absolutely love the 'show the errors' bit in the build page14:53
*** rlandy is now known as rlandy|rover14:56
tristanCmordred: yeah, i'm really looking forward to return the build page as job result now ;)14:57
AJaegertristanC: cool - didn't notice that one before14:59
tristanCit's just a small processing, we could extend it to display more things, such as the list of roles and how long they last each15:01
pabelangerso, I noticed we are leaking command sockets for zuul. Any objections on cleaning those up? I'm considering using them for an ansible playbook check to confirm a zuul service is stopped15:02
mordredtristanC: me too15:02
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Clean up command sockets on stop  https://review.openstack.org/62899015:03
pabelangerfor example: ^15:03
mordredpabelanger: I do not have any objections15:03
*** irclogbot_3 has quit IRC15:06
*** irclogbot_3 has joined #zuul15:15
*** openstackgerrit has quit IRC15:22
*** openstackgerrit has joined #zuul15:23
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Ensure command_socket is last thing to close  https://review.openstack.org/62899515:23
pabelanger^ is a follow up to command socket cleanup. All services should now stop it as the last step, that is how the scheduler was working15:24
tobiashpabelanger: do you think it makes sense to validate a cleaned up command socket in ZuulTestCase.shutdown?15:41
pabelangertobiash: great idea, can add a test to confirm15:42
tobiashcool15:42
tobiashanyone want to look at https://review.openstack.org/621391 ? This fixes an annoying warning in my ide ;)15:43
tobiashit's just a tiny gitignore fix15:44
*** pcaruana has quit IRC16:21
*** bjackman has quit IRC16:40
mordredtobiash: +A16:41
*** hashar has quit IRC16:51
*** rfolco has quit IRC16:58
*** rfolco has joined #zuul16:59
openstackgerritMerged openstack-infra/zuul master: Fix ignored but tracked .keep file  https://review.openstack.org/62139117:06
*** hashar has joined #zuul17:07
openstackgerritMatthieu Huin proposed openstack-infra/zuul-jobs master: [WIP] upload-pypi: add option to register packages  https://review.openstack.org/62901817:19
*** rf0lc0 has joined #zuul17:30
*** rf0lc0 has quit IRC17:31
*** rfolco has quit IRC17:33
*** rfolco has joined #zuul17:42
*** dkehn has joined #zuul18:29
dkehnclarkb: when running the zuul-migrate is there an easy apporach i.e. zuul-migrate layout.yam output-dir?18:29
clarkbdkehn: Its been about a year since I had to think about that stuff. I'm not sure. Basically you get a bunch of output broken up into some logical files18:31
dkehnclarkb: ok, is the run-magrate script around anywhere https://git.zuul-ci.org/cgit/zuul/tree/playbooks/zuul-migrate/run.yaml18:41
clarkbdkehn: https://git.zuul-ci.org/cgit/zuul/commit/tools?id=9e20f12ca84a0853d79090aebddd6fe3e9e0d1bc it was removed in that commit so if you checkout the commit previous you should have it18:42
dkehnclarkb: thanks, was wondering of the calling, because when I just do the layout and outdir I get the job-config error, it helps18:45
clarkbdkehn: I think the mapping file there is a hints file taht says rename foo to bar18:46
clarkbdkehn: but I don't remember all the details18:46
clarkbif you go back in the history of the git repo you'll likely find those details though18:46
pabelangerdkehn: keep in mind, zuul-migrate was very openstack specific. I used it to migrate rdoproject.org to zuulv3, but think i pushed up all my changes upstream19:11
pabelangerbasically, multi node jobs, you are better off re-writing from scratch IMO19:11
*** ianw_pto is now known as ianw22:26
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Update upload-logs to process docs as well  https://review.openstack.org/51185322:32
*** hashar has quit IRC22:47
openstackgerritMerged openstack-infra/zuul master: Add timer for starting_builds  https://review.openstack.org/62346822:57
*** ianychoi has quit IRC23:21
clarkbtobiash: corvus: I left some comments on the distributed scheduler spec23:35
clarkbfor some of that I don't actually know if one appraoch will turn out better than another, but tried to think about it in terms of avoiding the known drawbacks with the listed appraoches23:36
corvusclarkb: replied, something is unclear to me; maybe you can clarify23:43
clarkbcorvus: given the costs of git merges that makes sense (I wasn't really advocating for that method as much as sharing a high level of what other application have done) I also responded in gerrit so that this comment isn't lost :)23:48
corvusclarkb: cool, thx23:49
-openstackstatus- NOTICE: The Etherpad service at https://etherpad.openstack.org/ has been offline since 23:22 UTC due to a hypervisor issue in our service provider, but should hopefully return to service shortly.23:51

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