Thursday, 2018-04-12

mrhillsmanthx00:04
mrhillsmanmaybe i am overcomplicating things00:04
*** JasonCL has quit IRC00:04
mrhillsmanbecause i can see pipelines listed on the status page getting out of hand00:04
*** JasonCL has joined #zuul00:05
EmilienMwhy zuul is always restarted when code is updated?00:05
clarkbEmilienM: the same reason you restart nova when code is updated00:05
clarkbEmilienM: you need to run the new executables00:05
EmilienMclarkb: mutable config?00:05
clarkbEmilienM: its not config, its the actual code00:05
EmilienMok00:06
EmilienMright00:06
clarkbthe config is dynamically updated all the time00:06
EmilienMthat's good00:06
clarkbevery time .zuul.yaml change merges for example00:06
EmilienMI'm wondering if containerizing zuul would help00:07
clarkbI think the only config you may need to restart for currently is the ini config which has stuff like driver connection details in it00:07
clarkbEmilienM: you'd still have to restart it to pick up new code00:07
clarkb(same as nova)00:07
pabelangeri think we could CD nodepool-launcher today, right? Since all that data is stored in zookeeper00:07
clarkbpabelanger: we do CD nodepool launcher today00:07
pabelangerwe do?00:08
clarkbyes we continuously deploy it00:08
clarkbstraight from master00:08
pabelangerright :) What is the restart part called00:08
*** harlowja has quit IRC00:08
clarkbthats part of it00:08
clarkbit just happens to be the manual step in the process00:08
pabelangerdeploy / restart on each commit. I think we could write a pipeline in zuul to do that, without a downtime on nodepool-launcher00:09
pabelangerIIUC00:09
clarkbneeding to restart processes to pick up new code is somewhat orthogonal to CD and containers00:09
clarkbunless you have some way to transition from one process into a new fork (which is doable in some cases see weechat for example) you have to do that00:10
clarkbpabelanger: its like a one line chagne in existing puppet if you want to do that00:10
clarkbsubscribe => Exec[nodepool-install] in the service00:10
pabelangerclarkb: yah, agree. But would be cool to drive it directly from zuul.o.o :)00:11
clarkbEmilienM: the major issue is the zuul scheduler is still a spof. So you can't restart it without a downtime00:11
EmilienMI see00:11
clarkbexecutors can be restarted without downtime, nodepool launchers without downtime and nodepool builders. Zuul web too I think if you ran them behind a load balacner00:12
pabelangerEmilienM: FWIW: tobiash is deploying zuul / nodepool in containers on openshift00:12
clarkbbut if you have to retart the scheduler its a downtime00:12
pabelangeryah00:12
pabelangerI think nodepool-builder needs a little more work to clean up diskimage-builder on shutdown, but agree no downtime for it00:13
clarkbthe fingergateway holds open long term connections but I think it too could be load balacned00:13
clarkbits just users would noticed when it flapped but immediately be able to reconnect00:14
EmilienMpabelanger: sweet00:14
*** JasonCL has quit IRC00:29
*** JasonCL has joined #zuul00:31
tristanCis there a role/task to accept inbound port 19885 (zuul-console) for slave running firewalld?00:35
clarkbtristanC: looks like we bake that into our images00:36
clarkbquick grepping doesn't show it in the jobs00:36
tristanCor maybe we should just wait for the zuul_stream refactor where the console stream goes through ssh tunnel00:38
tristanCotherwise, this deserve a bit more of documentation00:38
*** dtruong_ has joined #zuul00:42
*** nguyenhai_ has joined #zuul00:43
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add ansible-lint job  https://review.openstack.org/53208300:44
pabelangeryah, we back it into a DIB element today00:44
*** dtruong has quit IRC00:46
*** nguyenhai has quit IRC00:46
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add ansible-lint job  https://review.openstack.org/53208300:46
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add ansible-review job  https://review.openstack.org/53522300:49
*** odyssey4me has quit IRC00:51
*** odyssey4me has joined #zuul00:51
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add ansible-upload-to-galaxy job  https://review.openstack.org/53208400:54
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add ansible-spec job  https://review.openstack.org/53208500:55
tristanCthanks for the information, that's good to know00:55
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: mqtt: add basic reporter  https://review.openstack.org/53554301:04
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: model: add empty branch attribute to the Tag object  https://review.openstack.org/56070001:10
*** JasonCL has quit IRC01:14
*** gouthamr has joined #zuul01:46
*** gouthamr has quit IRC01:49
*** gouthamr has joined #zuul01:50
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: launcher: handle ZK session loss during handler poll  https://review.openstack.org/55633501:56
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: zk: use kazoo retry facilities  https://review.openstack.org/53553701:57
*** kmalloc has quit IRC02:06
pabelangerclarkb: clarkb: tobiash: replied to 3.0.1 ML post about maybe also removing zuul-cloner, since it is broken and no longer needed.02:17
*** sshnaidm has quit IRC02:26
*** gouthamr has quit IRC02:33
*** gouthamr has joined #zuul02:35
*** gouthamr_ has joined #zuul02:40
*** gouthamr has quit IRC02:40
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Refactor run_handler to be generic  https://review.openstack.org/53555402:50
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: Refactor NodeLauncher to be generic  https://review.openstack.org/53555502:56
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: openstack: convert rate to float  https://review.openstack.org/53725002:59
openstackgerritTristan Cacqueray proposed openstack-infra/zuul-jobs master: Add emit-job-report role  https://review.openstack.org/54842503:11
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: configloader: add variant-description  https://review.openstack.org/54974803:11
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: zuul-changes: update for the new api url  https://review.openstack.org/55765603:20
*** jimi|ansible has quit IRC03:24
*** jimi|ansible has joined #zuul03:27
*** jimi|ansible has joined #zuul03:27
*** gouthamr_ is now known as gouthamr03:31
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: reporter: do not expect branch attribute in Tag object  https://review.openstack.org/56070003:39
*** rlandy has quit IRC04:04
*** gouthamr has quit IRC04:10
openstackgerritMerged openstack-infra/zuul master: Report to all reporters even if one fails  https://review.openstack.org/55785904:29
openstackgerritMerged openstack-infra/zuul master: Reorganize "Zuul From Scratch" document  https://review.openstack.org/55698804:29
*** openstackgerrit has quit IRC05:48
*** openstackgerrit has joined #zuul06:02
openstackgerritMerged openstack-infra/nodepool master: openstack: convert rate to float  https://review.openstack.org/53725006:02
*** threestrands has joined #zuul06:05
*** hashar has joined #zuul06:51
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Fix implicit role for repos named ansible  https://review.openstack.org/56055406:52
*** electrofelix has joined #zuul07:24
*** xinliang has quit IRC07:30
*** jpena|off is now known as jpena07:33
*** xinliang has joined #zuul07:35
*** sshnaidm has joined #zuul07:52
*** JasonCL has joined #zuul09:49
*** kmalloc has joined #zuul10:01
*** threestrands has quit IRC10:24
*** odyssey4me has quit IRC10:55
*** odyssey4me has joined #zuul10:55
*** sshnaidm is now known as sshnaidm|lnch10:58
*** odyssey4me has quit IRC11:00
*** odyssey4me has joined #zuul11:00
*** Wei_Liu1 has joined #zuul11:10
*** Wei_Liu has quit IRC11:10
*** Wei_Liu1 is now known as Wei_Liu11:10
*** jpena is now known as jpena|lunch11:53
*** JasonCL has quit IRC12:04
*** dkranz has quit IRC12:06
*** rlandy has joined #zuul12:28
*** sshnaidm|lnch is now known as sshnaidm12:32
*** pwhalen has quit IRC13:10
*** pwhalen has joined #zuul13:18
*** pwhalen has joined #zuul13:18
*** gouthamr has joined #zuul13:32
*** jpena|lunch is now known as jpena13:36
*** JasonCL has joined #zuul13:38
*** JasonCL_ has joined #zuul13:42
*** JasonCL_ has quit IRC13:42
*** JasonCL_ has joined #zuul13:43
mordredclarkb, Shrews, tobiash: sorry, I was out yesterda - I see shade chat in the scrollback but it seems all is good and nothing needed from me on that?13:43
*** JasonCL has quit IRC13:43
*** JasonCL_ has quit IRC13:45
*** sshnaidm is now known as sshnaidm|mtg13:47
Shrewsmordred: i don't think so?13:49
*** JasonCL has joined #zuul13:50
mordredShrews: cool13:54
mordredShrews: glad I could be of assistence then13:54
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Use nodeenv for npm and yarn in tox  https://review.openstack.org/56010414:05
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Clean up developer javascript instructions  https://review.openstack.org/56010614:05
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Remove docker instructions and build:docker helper command  https://review.openstack.org/56010514:05
mordredtristanC: sweet! with the multi-tenant dashboard job and the CORS patch I can see the errors you listed ... I think we're close to that patch working :)14:07
*** mugsie has quit IRC14:08
fungiclarkb: pabelanger: i don't think it's so much zuul-scheduler as a spof which leads to disruption, but rather the fact that it maintains its state in process memory which doesn't persist between restarts (granted, solving that isn't as simple as externalizing the state storage because you may want the new execution to create some different state than its predecessor so you're stuck having to define an api14:16
fungicontract around your state serialization)14:16
fungithe spof is even less of an issue if we get to the point where we have some intermediate message service buffering events while the scheduler is down so that it can request them once it's running again14:17
clarkbthats true, though people tend to notice via the side effects and not necessarily the state graphs themselves14:31
clarkb(jobs restarting and dashboard going away)14:31
clarkboh and missing gerrit events14:33
clarkbI think once we address those whether or not the scheduler remains a spof will be less user visiible14:33
*** JasonCL has quit IRC14:34
pabelangerright, I agree with the scheduler points. My comments last night were more I think we are at a point in time where we could start doing restart of nodepool on a per commit bases, if we were comfortable with that. However, I know in the past corvus (I think) expressed an issue with doing that since non infra-root contributors could approve a commit which might break something in openstack-infra, then have no14:36
pabelangerability to restore the service14:36
clarkbI think if we made the nodepool integration jobs voting (they aren't voting right now right?) I'd be a lot more comfortable with that14:37
dmsimardcould the scheduler dump it's state before starting ?14:38
pabelangerthey still are non-voting on zuul, IIRC14:38
dmsimardbefore restarting*14:38
pabelangerdib and glean, yes14:38
dmsimardlike doing a restart would do the equivalent of our current manual dump/restore14:38
pabelangerdmsimard: in fact, I think the scheduler support that today, we just don't use it?14:38
pabelangeror maybe did at one point in time14:38
corvusit can be done.  does someone want to do it?14:39
clarkbmy concern with putting a lot of effort into that is it doesn't really address the problems users do notice with restarts14:40
clarkball the jobs have to start over and we miss gerrit events and the dashboard returns an error in the interim14:40
*** JasonCL has joined #zuul14:40
clarkbit would reduce operator overhead for doing a graceful restart though14:40
corvusyes, i wouldn't put a lot of effort into it.  but it would be a good minor improvement14:41
pabelangeragree14:41
dmsimardwould just be a quality of operator life improvement14:42
dmsimard(there needs to be more of those)14:42
corvusi'm happy to discuss implementation with a volunteer14:42
tristanCwould be nice if the scheduler would start the gerrit connection early and store events until configuration is completed14:46
corvustristanC: it does14:46
corvusperceived downtime due to missing events should be as low as about 30 seconds (time to restart scheduler process)14:46
corvus(sometimes it takes a few seconds to stop cleanly)14:47
tristanCoh that may be correct, it's just that irc notices mention a 15 minutes downtime14:47
*** dkranz has joined #zuul14:48
corvustristanC: if you're talking about yesterday's openstack-infra restart, that's not representative.14:50
*** mugsie has joined #zuul14:54
*** mugsie has quit IRC14:54
*** mugsie has joined #zuul14:54
tristanCmordred: yes, can't wait to rebase the rest of my dashboard changes on top of angular 5 :)14:54
Shrewsfwiw, I would be very against auto restarting nodepool after every commit. Even making the non-voting jobs voting14:55
*** gouthamr has quit IRC14:56
ShrewsI'm at a chiro appt now, but happy to discuss that more when at a computer14:56
*** gouthamr has joined #zuul15:02
*** JasonCL has quit IRC15:03
*** mugsie has quit IRC15:04
*** mugsie has joined #zuul15:06
*** mugsie has quit IRC15:06
*** mugsie has joined #zuul15:06
*** JasonCL has joined #zuul15:06
*** mugsie has quit IRC15:08
*** mugsie has joined #zuul15:08
*** mugsie has quit IRC15:08
*** mugsie has joined #zuul15:08
pabelangerShrews: any specific reason why?15:14
mordredtristanC: ++15:27
pabelangertoabctl: I don't think our new quota handing logic in nodepool applies to volumes right now, does that sound right?15:27
pabelangertobiash: ^15:28
pabelangertoabctl: sorry15:28
toabctlnp :)15:28
mordredpabelanger: I believe you are correct- we're only doing nova quota calcs atm15:29
pabelangermordred: k, I'll see if I can update it, noticed we were still trying to launch nodes in vexxhost when we hit quota on volumes15:29
pabelangermordred: and on that note, might you have an idea how we could track leaked volumes in nodepool / shade? Seeing that scenario in vexxhost currently. mnaser is working on the openstack side to see why that might be15:30
mordredpabelanger: we'll need to add a get_block_storage_limits to shade - but that should be easy enough15:31
mordredpabelanger: as for the otherthing, nothing springs to mind if we mark them as terminate-on-delete when we do boot-from-volume - but I'll poke for a sec15:31
clarkbpabelanger: yes that was mentioned yesterday by tobiash as something that would need improving to support volumes better15:32
mordredpabelanger: oh - if the clouds are new enough, I think we could add a tag to the volume via the block_device_mapping_v2 structure15:33
pabelangermordred: k, lets see what mnaser says :)15:33
clarkbdoes nova add any metdata by default in that case (possibly something we could use to support older clouds too)15:34
mordredclarkb: I'm not sure- that would be ideal15:36
clarkbideally "this is the disk for instance with uuid foo"15:37
clarkbthen if nodepool doesn't see a uuid foo we can delete it15:37
clarkbor similar15:37
*** JasonCL has quit IRC15:38
*** JasonCL has joined #zuul15:39
clarkbpabelanger: is there a change to remove zuul-cloner yet?15:43
clarkbpabelanger: if not is that somethign I should just go ahead and push up?15:43
AJaegerclarkb: there's one up - but you break everyobdoy if you do15:44
pabelangerclarkb: not yet, wanted to make sure everybody was okay first15:44
pabelangerbut will do now15:44
AJaegerclarkb: https://review.openstack.org/51350615:44
clarkbAJaeger: I don't think it should break anyone15:44
* clarkb looks15:44
clarkbAJaeger: oh sorry, I meant remove zuul-cloner from zuul itself15:45
AJaegerclarkb: sorry, in a call and didn't follow discussion. But if we remove zuul-cloner from our images, we have breakage15:45
clarkbAJaeger: the change you link likely would be disruptive15:45
clarkbAJaeger: ya different items, but good to keep that in mind15:45
AJaegerclarkb: ok.15:45
*** JasonCL has quit IRC15:45
*** JasonCL has joined #zuul15:49
pabelangeryah, we still want to do that, but protected with zuul-cloner role in zuul-jobs. We've actually already removed zuul-cloner from DIB images15:53
tobiashpabelanger: right, currently there is no quota handling of volumes in nodepool15:54
tobiashWhich should be added also now due to boot from volume support15:55
tobiashBut it should be easy to add that15:57
tobiashThe quota handling code is pretty generic15:58
corvuspabelanger, clarkb, tobiash: i'd like to tag 301, zuul-cloner notwithstanding (i think we should remove it, but i don't think we need to block on it)15:59
clarkbcorvus: ya I don't think we need to block on it either15:59
clarkbnew users won't really know that it is a thing to worry about so shouldn't affect them (it doesn't work anyways)15:59
pabelangerclarkb: corvus: wfm, I can push it up shortly. debuging nodepool.o.o issue right now16:00
tobiashcorvus: fine for me16:04
corvusweird, when i run 'zuul --version' locally on master i get 3.0.1.dev2716:05
corvusbut zuul.o.o says dev5116:05
corvusoh, maybe that's just from when the tox env was created16:05
corvusmaybe that doesn't get updated16:05
corvusyep16:06
tobiashcorvus: I guess 560554 is for the next release then16:07
corvustobiash: yep16:07
tobiashI think it should go latest in the next release as without it you cannot run jobs defined in a repo named ansible16:09
pabelangerwhich section of reno would removal of zuul-cloner go under?16:09
tobiashI have it in my staging branch so this is not an issue for me16:10
tobiashpabelanger: upgrade notice maybe?16:10
corvuspabelanger: i'm not sure it needs one?16:10
pabelangertobiash: yah, that or other is what I am thinking16:10
pabelangercorvus: okay, that works too16:10
corvus(i can't think of how we'd expect someone to alter their behavior between 3.0.0 and 3.0.2 based on this)16:11
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Remove zuul-cloner command  https://review.openstack.org/56095816:11
clarkbcorvus: ++ it never worked on 3.x if you want a working version you are already explicitly using v216:12
corvus11a80ccebd5108bea1724e688c36ae281bc220b4 is what openstack-infra is running; i'll tag that as 3.0.116:12
pabelanger+116:13
tobiash++16:13
corvuspushed16:13
*** JasonCL has quit IRC16:19
corvusoh, i bet we don't rebuild the docs on release tags16:22
corvusthat means we're going to need to land a change before we see the release notes updated16:22
*** JasonCL has joined #zuul16:27
fungiwe could add a release pipeline docs job?16:27
fungi(for future sanity)16:27
corvus++16:27
corvusi'll get on that16:27
fungipresumably reenqueuing the master branch tip into the post pipeline after the tag is pushed will also get us that in the interim?16:28
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Publish docs in release pipeline  https://review.openstack.org/56096416:29
corvusfungi:  you're right.  clever.  :)16:29
corvusbut i went ahead and approved 560958, so there'll be a change landing shortly16:30
tobiashcorvus: added a question on 56096416:34
*** gouthamr has quit IRC16:38
corvustobiash: mordred and i answered.16:47
corvusi could go either way on whether that's desirable :)16:48
corvusmordred: if i'm following correctly, we have no actionable patches from you at the moment all the javascript stuff is either in error or based on outdated patchsets.16:49
tobiashcorvus: that makes me think about which version of the docs we want to publish16:53
corvustobiash: i'm pretty happy to publish CD master for the most part, but we can certainly also publish specific versions.16:54
tobiashLatest master or latest tag or both?16:54
clarkbopenstack does a project/latest/ which tracks master or latest release and then also project/$release16:54
clarkbs/or/and/16:54
*** dtruong_ has quit IRC16:56
fungiit's probably also fine to just consider that for now documentation is still under heavier churn while it catches up in places we realize we've missed, but that at some later point it'll make more sense to switch to just publishing when tagged (especially if we're tagging new point releases extremely frequently)16:56
*** dtruong has joined #zuul16:57
corvusShrews, clarkb: see comment on https://review.openstack.org/56004417:03
SpamapSI've always liked the paradigm of having a /latest and /{tag}17:03
clarkbcorvus: ya I think I used 30 seconds for the database query17:04
clarkbcorvus: maybe we use 30 seconds to be inline with the library default?17:04
clarkbcorvus: we can also make it set no timeout and have the underlying lib timeout for us instead17:05
corvusclarkb: i think that'd be my preference unless there's an overriding reason to go less17:05
corvusclarkb: that function won't ever timeout though17:05
clarkb30 seconds is probably a good value then17:05
corvusclarkb: that's RPCClient.submitJob, not gear.Client.submitJob17:05
corvusclarkb: RPCClient.submitJob not only calls gear.Client.submitJob, it *also* waits for the job to finish17:06
clarkbgotcha17:06
corvusi wrote a treatise on this in my review of the gear async zuul-web change17:06
*** electrofelix has quit IRC17:06
corvusi'm pretty sure we're confusing ourselves here, due to the appropriation of the rpcclient by zuul-web17:06
corvusthis change: https://review.openstack.org/56002617:07
corvusclarkb: can you +3 https://review.openstack.org/560090 ?17:10
*** hashar is now known as hasharAway17:11
clarkbcorvus: done17:12
*** leifmadsen has quit IRC17:13
*** gouthamr has joined #zuul17:14
*** mugsie has quit IRC17:14
*** mugsie has joined #zuul17:15
*** mugsie has quit IRC17:15
*** mugsie has joined #zuul17:15
openstackgerritMerged openstack-infra/zuul-sphinx master: Add build-sphinx check/gate jobs  https://review.openstack.org/56009017:17
*** jpena is now known as jpena|off17:17
*** leifmadsen has joined #zuul17:21
Shrewscorvus: clarkb: Ok. I need to familiarize myself with the async stuff in gear, but I'm going to complete the docs changes before doing that.17:22
ShrewsIf 30s is better, fine w/ me17:22
corvusShrews: zuul/executor/client.py is a good example of the pattern17:23
openstackgerritMerged openstack-infra/zuul master: zuul-changes: update for the new api url  https://review.openstack.org/55765617:23
mordredcorvus: yes. that is correct.17:23
mordredcorvus: although my goal is that by end of day that stack should be good to go17:23
corvusShrews: and thinking more about it, i say just drop the rpcclient from zuul-web and make a new client just for that.17:24
corvusmordred: ++17:24
mordredcorvus: fwiw - the angular5 patch now has a preview version working against the softwarefactory multi-tenant deploy too - which has shown a place where things were broken for multi-tenant, so yay17:24
corvusi am caught up on reviews -- but in order to do that, i have had to ignore the 126 changes which are failing tests, outdated, or marked WIP.  :)17:25
mordredcorvus: it has also made me very much want to figure out a $something where we have js layer tests that we run against a zuul either in zuul unit or functional tests somehow17:26
mordredcorvus: since there are currently some things only verified by looking at those draft publications - which isn't really sustainable long-term17:26
mordredcorvus: \o/17:26
corvusmordred: yeah, what can we do for that?  selenium, or is there some other js thing?17:26
mordredcorvus: yah - there's a bunch of good js things17:27
mordredcorvus: the main question is more how to wire it all up17:27
mordredcorvus: I'm kind of thinking about perhaps a unittest similar to the current test_web tests - but that the thing it does is trigger the js test suite17:28
mordredlike "does the js test suite pass against the zuul this unit test just spun up"17:28
corvusmordred: yeah, that's a promising approach17:29
mordredcorvus: but that's a bit handwavey - I wanna fix the multi-tenant issue in the angular5 patch first - and the nodeenv patch - but then I'll figure that out17:29
corvusas long as we're not testing that we wrote the same javascript twice.  ;)17:30
mordredcorvus: aw. but that's such a fun test17:30
Shrewscould a non-corvus persona review this rather simple nodepool change? https://review.openstack.org/55253817:30
ShrewsTIA17:30
clarkbShrews: I'll take a look17:30
mordredShrews: how non-corvus does the person need to be?17:31
*** corvus is now known as jeblair17:31
Shrewsmordred: very17:31
*** jeblair is now known as corvus17:31
Shrewsand a jeblair doesn't count17:31
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Use nodeenv for npm and yarn in tox  https://review.openstack.org/56010417:33
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Clean up developer javascript instructions  https://review.openstack.org/56010617:33
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Remove docker instructions and build:docker helper command  https://review.openstack.org/56010517:33
mordredcorvus: if those turn green ^^ they should be ready to go17:34
mordred(they were red before beause I removed a job that was still in use elsewhere :) )17:34
clarkboh I should review the nodeenv change too17:35
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Use nodeenv for npm and yarn in tox  https://review.openstack.org/56010417:39
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Remove zuul-tox-py35  https://review.openstack.org/56098317:39
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Clean up developer javascript instructions  https://review.openstack.org/56010617:39
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Remove docker instructions and build:docker helper command  https://review.openstack.org/56010517:39
mordredclarkb: yes please17:39
clarkbits unfortunate that setuptools environment markers aren't capable of checking things outside of some basic python stuff17:40
mordredyah17:41
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Add Gerrit docs to Zuul From Scratch  https://review.openstack.org/55860017:44
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Add static driver doc to Zuul From Scratch  https://review.openstack.org/55880217:50
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add example nodepool-launcher systemd service file  https://review.openstack.org/56099317:53
mrhillsman"If a job has an empty or no nodeset definition, it will still run and may be able to perform actions on the Zuul executor."17:56
mrhillsmanmay be able to perform actions on the Zuul executor...can i get a bit more on this part of that sentence17:57
clarkbmordred: I've +2'd it but left some thoughts. There definitely feels like maybe there is a trade off there17:57
clarkbmordred: particularly in spin up time costs. But for local usage that is a one time cost for the most part17:57
clarkbmrhillsman: your playbooks can run tasks on the localhost host (the executor's bwrap container for that job). You won't be able to read much data off of disk or even write arbitrary shell I think. So you're constarined in what you can do to the "safe" modules17:58
mrhillsmanthx17:58
clarkbmrhillsman: one example of how we use that setup for us is hitting the read the docs api to trigger a docs rebuild in read the docs iirc17:58
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Add sample systemd service files.  https://review.openstack.org/55883017:58
mrhillsmangot it17:59
Shrewscorvus: Re: your comment in 558830 ^ about the chmod, I have no idea if that is necessary, but is just grabbed from the instructions that were already merged18:00
pabelangersystemd files should be 0644, likely a warning message on boot if that was missing18:01
pabelangerIIRC18:01
openstackgerritMerged openstack-infra/nodepool master: Handle ZK session loss during node launch  https://review.openstack.org/55253818:03
clarkbShrews: in https://review.openstack.org/#/c/558830/4/doc/source/admin/zuul-from-scratch.rst shouldn't the systemctl commands be in the order of enable, start, status? instead of start status enable18:05
Shrewsclarkb: i dunno. i am systemd ignorant and just copying already merged text18:06
clarkbShrews: apparently enable/disable is just for autostarting on boot type stuff18:07
clarkbyou can explicitly start a disabled unit so it should be fine as is18:07
ShrewsIt's funny how this reorg has brought about many questions on already reviewed/merged instructions.  :)18:07
Shrewsok. i can change it if need be18:08
*** Wei_Liu1 has joined #zuul18:08
pabelangerI'm just looking at systemd files again and had questions around daemon / non-daemon things for systemd.  Our examples are not passing -d, which I believe the preference of corvus. But I believe clarkb or fungi was saying there is something around forking which might not work for type=simple?18:08
clarkbI think its fine. I'm guessing the intent there was to start it, check the status as good then enable it to come back on next boot18:08
pabelangerdoes our daemon logic in nodepool / zuul call fork() ?18:08
clarkbpabelanger: it does18:08
clarkbpabelanger: it does the proper unix daemonization process which involves a double fork18:09
*** Wei_Liu has quit IRC18:09
*** Wei_Liu1 is now known as Wei_Liu18:09
pabelangerokay, so then we need type=forking in our systemd service files I believe18:09
pabelangerhttps://www.freedesktop.org/software/systemd/man/systemd.service.html#Type=18:09
Shrewspabelanger: happy to make that change if you point me to the proper location18:09
clarkband probably set the pidfile too (based on that doc)18:09
clarkbthe alternative is to pass -d and let systemd do it for you18:10
pabelangerShrews: yah,I can point but I think fungi was the expert here :)18:10
clarkbhrm I should make lunch before this phone call18:10
openstackgerritMerged openstack-infra/zuul master: gerrit: recognize project-created event  https://review.openstack.org/56027418:11
pabelangerShrews: okay, lets comments on 56099318:11
Shrewspabelanger: thx!18:12
Shrewscorvus: looks like a RFC on 560993 to you as well18:13
*** Wei_Liu has quit IRC18:14
mordredclarkb: agree re: the tradeoffs ... that said, these days nodeenv is actually downloading/installing pre-built node, so you don't have to actually do a build. but yes, also, it should be a one-time cost (or at least no worse than thecost of rebuilding a virtualenv anyway)18:14
clarkbmordred: oh I didn't realize it was just a download now rather than a download and compile. That is nice18:15
*** openstackgerrit has quit IRC18:19
Shrewspabelanger: do the zuul service files need the same changes you mentioned for the np file?18:20
Shrewspabelanger: for https://review.openstack.org/55883018:20
pabelangerShrews: yah, we should sync the chance across all, once we figure out how it looks in 55883018:21
pabelangererr, 56099318:21
corvusShrews: i'm not systemd expert, but i can agree that we don't want "-d", so if systemd experts say that means type=forking then i guess that's what we should do :)18:28
Shrews"Computer! Make it so."18:28
clarkbI think it will work without type set to forking but systemd may have a harder time checking service status18:29
corvusShrews: the important thing is that when folks come up to us at conferences and ask us detailed questions about systemd files, we point at clarkb and pabelanger and run18:29
clarkbuh oh18:29
Shrewscorvus: so important18:29
tobiashcorvus: what's the reason to not use -d?18:30
tobiashI always used -d (with systemd earlier and now docker)18:31
corvusShrews, pabelanger, clarkb: i have rtfm now and agree that forking + pidfile is what we want :)18:31
corvustobiash: it currently comingles debug log settings as well18:31
corvustobiash: which may be what you want :)18:32
tobiashSo maybe I want to switch to forking without knowing that18:32
pabelangeryah, I used simple and -d for local testing, but plan on trying forking now :)18:32
*** openstackgerrit has joined #zuul18:33
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Add example nodepool-launcher systemd service file  https://review.openstack.org/56099318:33
tobiashI'm not sure if forking is going well inside a container18:34
corvustobiash: it's probably not what you want for that18:34
corvustobiash: i think we should separate "don't fork" and "debug log" command line options to make this easier18:34
Shrews   .. attr:: pidfile18:36
Shrews      :default: /var/run/zuul-schedurecr/zuul-scheduler.pid18:36
Shrewslol18:36
Shrewswonder how that passed review??  ;)18:36
tobiashSo with -d debug output to stdout is enabled regardless of the logging config?18:37
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Add sample systemd service files.  https://review.openstack.org/55883018:38
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Fix documented scheduler PID file default  https://review.openstack.org/56101018:39
clarkbShrews: I want to say the default may actually be /var/run/zuul/zuul-$service.pid18:41
* clarkb looks18:41
clarkb'/var/run/zuul/%s.pid' % self.app_name <- yup18:42
Shrewsclarkb: oh, so the docs are all wrong18:42
Shrewsclarkb: i'll fix 'em up good18:42
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Add sample systemd service files.  https://review.openstack.org/55883018:43
tobiashShrews: added a question on ^18:44
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Fix documented PID file defaults  https://review.openstack.org/56101018:44
Shrewstobiash: i don't think we should depend on folks keep the source repo around, IMO18:45
ShrewsI mean, they should be able to figure out they can do that, if they really want to18:45
tobiashGood point18:48
corvusShrews: ha!  that typo has my fingerprints all over it.  dvorak has 'crl' all right next to each other.  usually i just mash them all when writing the word schedlclcr and it works out18:50
Shrewslol18:51
corvusShrews: but one more comment on that18:52
openstackgerritMerged openstack-infra/zuul master: configloader: add variant-description  https://review.openstack.org/54974818:53
Shrewscorvus: gah18:53
Shrewscorvus: yup, you are correct18:54
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Fix documented PID file defaults  https://review.openstack.org/56101018:55
Shrewsseemed like such a simple fix on the surface18:55
* Shrews hits documentation iceberg18:56
* mordred hands Shrews an icepick18:56
Shrewsmordred: most kind hearted folks would throw a lifevest, but yeah, this icepick will help18:57
Shrews:-P18:58
tobiashIs today something special? Zuul seems to be much busier than normally. Had today a change that waited an hour for nodes around 10:00 utc18:59
clarkbShrews: https://review.openstack.org/558830 needs the same pidfile update as latest ps for 561010? (I'm not actually sure myself)18:59
Shrewsclarkb: yeah, fixing that now19:00
Shrewsthx19:00
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul master: Add sample systemd service files.  https://review.openstack.org/55883019:01
corvustobiash: yeah, problem with images in rax; pabelanger debugging in #openstack-infra19:02
corvustobiash: it's annoying, but it's also kinda fun -- this is what we mean when we say we're redundant at the cloud level.  we've lost 30% of our capacity, and the only user visible impact is the backlog.19:04
tobiashThat's pretty cool19:05
tobiashI'm looking forward to the point where we can say that also about the control plane19:06
corvusindeed :)19:07
openstackgerritMerged openstack-infra/nodepool master: launcher: handle ZK session loss during handler poll  https://review.openstack.org/55633519:07
corvusunfortunately, the backlog means our doc update isn't going to show up for a while.  i'd like to send out the release announcement after that lands (so i can link to the right anchor).  so that will probably be much later today, or even tomorrow.19:10
pabelangerhttp://grafana.openstack.org/dashboard/db/nodepool-rackspace for the fun, can see the time where we rolled back to working images :D19:12
*** sshnaidm|mtg is now known as sshnaidm|afk19:13
*** gouthamr has quit IRC19:20
*** JasonCL has quit IRC19:28
*** gouthamr has joined #zuul19:30
*** JasonCL_ has joined #zuul19:30
openstackgerritMerged openstack-infra/zuul master: Remove zuul-cloner command  https://review.openstack.org/56095819:31
openstackgerritMerged openstack-infra/zuul master: Publish docs in release pipeline  https://review.openstack.org/56096419:31
*** JasonCL_ has quit IRC19:35
mordredcorvus: woot. https://review.openstack.org/#/c/560104/ landed19:40
mordredcorvus: sigh. PASSED TESTS19:40
corvusmordred: you're getting into the tyops spirit19:40
mordredcorvus: dman stragiht19:40
openstackgerritMerged openstack-infra/zuul-sphinx master: Make the yaml parser aware of '!encrypted/' tags  https://review.openstack.org/55996319:44
corvusoh, that [nodenv]install_command thing is neat19:45
corvusmordred: we probably don't need those for nodepool / remote venvs, but i guess it doesn't hurt too much?19:46
mordredcorvus: yah - I wasn't 100% sure if we needed them or not19:48
mordred(although I agree, it's likely not a big hurt)19:48
*** gouthamr has quit IRC19:50
*** gouthamr has joined #zuul19:51
openstackgerritMerged openstack-infra/zuul-jobs master: role: Inject public keys in case of failure  https://review.openstack.org/53580319:57
clarkbhttps://review.openstack.org/#/c/559852/ appears to have hit the lose zk connection possibly due to cpu contention problem20:02
clarkbShrews: ^ does that look like a correct analysis to you? don't want to recheck it and get it in if we think it may be the cause of the failure (but unrelated tests failed too)20:02
clarkbwe might want to consider reducing the concurrency in the gate?20:03
Shrewsclarkb: looking20:03
*** snapiri has quit IRC20:04
Shrews2018-04-12 17:08:33,637 kazoo.client                     WARNING  Connection dropped: outstanding heartbeat ping not received20:05
Shrewsclarkb: seems most likely20:05
clarkbok I am going to recheck the change in that case and then see if there is a not crazy way to get testr and tox to work together on choosing a concurrency level20:06
Shrewsthat is odd though. i haven't seen failures quite like that yet20:07
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Don't store references to secret objects from jobs  https://review.openstack.org/55359620:11
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Perform late validation of secrets  https://review.openstack.org/55304120:11
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Perform late validation of nodesets  https://review.openstack.org/55308820:11
openstackgerritJames E. Blair proposed openstack-infra/zuul master: WIP: late bind pipelines  https://review.openstack.org/55361820:11
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Test base job secrets  https://review.openstack.org/56103020:11
*** snapiri has joined #zuul20:11
corvus(that's just a rebase on a new test which should show the series failing)20:12
*** JasonCL has joined #zuul20:16
*** JasonCL has quit IRC20:18
openstackgerritMerged openstack-infra/zuul master: Use nodeenv for npm and yarn in tox  https://review.openstack.org/56010420:20
openstackgerritMerged openstack-infra/zuul master: Clean up developer javascript instructions  https://review.openstack.org/56010620:20
openstackgerritMerged openstack-infra/zuul master: Fix documented PID file defaults  https://review.openstack.org/56101020:20
openstackgerritClark Boylan proposed openstack-infra/zuul master: Reduce test concurrency by 1 cpu  https://review.openstack.org/56103720:21
clarkbShrews: corvus ^ I think I figured out a non invasive way to support this20:21
corvusclarkb: what's the current failure rate due to that error?20:23
clarkbcorvus: let me check logstash20:23
openstackgerritMerged openstack-infra/zuul master: Make db queries asynchronous in zuul-web  https://review.openstack.org/55985220:27
clarkbusing the specific kazoo message above and searching against zuul-tox-py35 just this one time in last 7 days according to logstash20:27
clarkbI know shrews has run into it before though (whcih is why I pinged shrews earlier)20:27
corvusclarkb: which provider?20:27
clarkbthis job was inap20:28
corvusmaybe we still want to do it?  it might be worth several rechecks and comparing runtimes (especially if we hit multiple providers) to see what the tradeoff is20:29
clarkb++20:29
Shrewsclarkb: i have?  O.o20:29
clarkbShrews: I seem to recall you debugging an issue related to zk dying in the test runs20:30
clarkbwith pabelanger maybe?20:30
clarkb(where dying is connections are lost otherwise unhappy)20:30
Shrewsi've seen that before (rarely), but not the cpu contention stuff20:30
corvusi left a wip note on that change20:31
clarkboh I thoughti t had been attributed to cpu contention20:31
clarkbfwiw I think we hae noticed real slowdowns post meltdown20:32
corvus(conference talk idea ^)20:32
clarkbqemu + nova in particular. I wouldn't be surprised if that is also playing a part in this with the higher cost of context switches20:32
clarkbone of the known issues was nova had no way of exposing the pcid instruction to guests which was recently fixed. Hopefully we see that fix roll out to the clouds soonish20:33
clarkb(so we were worst case meltdown performance hit everywhere rather than best case)20:33
clarkbs/instruction/feature/20:33
*** dkranz has quit IRC20:35
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: Fix typo in build-sphinx-docs docstring  https://review.openstack.org/56104020:41
*** JasonCL has joined #zuul20:42
openstackgerritDoug Hellmann proposed openstack-infra/zuul-jobs master: document that the build-reno-releasenotes job accepts sphinx_python  https://review.openstack.org/56104120:43
*** gouthamr_ has joined #zuul20:43
openstackgerritDoug Hellmann proposed openstack-infra/zuul-jobs master: document that the build-reno-releasenotes job accepts sphinx_python  https://review.openstack.org/56104120:49
*** JasonCL has quit IRC20:51
*** JasonCL has joined #zuul20:51
*** JasonCL has quit IRC20:55
mrhillsmanquestion: looking at http://status.openlabtesting.org/stream.html?uuid=305a88df898f474694f4c3bd12870631&logfile=console.log20:56
mrhillsmanif you search for zun20:56
mrhillsmancan see that the depends-on syntax is working20:56
mrhillsmanHEAD is now at ebe01a5 [WIP] Support enabling Zun on devstack20:57
mrhillsmanbut the actual code from that does not appear to be being used20:57
clarkbmrhillsman: can you link to that change?20:58
mrhillsmansure20:58
mrhillsmanhttps://github.com/gophercloud/gophercloud/pull/927#issuecomment-38091719620:58
*** pwhalen has quit IRC20:58
mrhillsmani think the console is gone now :(20:59
SpamapSmrhillsman: do you not have a post job that sets the result and stores the log somewhere?20:59
mrhillsmanyeah, it is there20:59
clarkbmrhillsman: that seems to be a dummy change, not the update to enable zun20:59
mrhillsmanso the update is in the first comment depends-on there21:00
mrhillsmanhttps://github.com/theopenlab/openlab-zuul-jobs/pull/14221:00
*** JasonCL has joined #zuul21:01
*** JasonCL has joined #zuul21:02
*** pwhalen has joined #zuul21:02
*** pwhalen has joined #zuul21:02
clarkbmrhillsman: is openlab-zuul-jobs a trusted repo?21:02
clarkbor config repo? whatever the term is21:03
mrhillsmanyes, but let me confirm21:03
*** JasonCL has quit IRC21:03
mrhillsmanit is21:03
*** JasonCL has joined #zuul21:03
clarkbmrhillsman: the job config of trusted repos won't be speculatively applied21:04
clarkbmrhillsman: you have to merge them first21:04
mrhillsmanah ok21:04
mrhillsmani thought that "Already on master" shed some light on the why21:04
clarkbmrhillsman: I think the git checkouts will still checkout the right ref21:04
mrhillsmanwas wondering why it pulled in the change it appeared but then said that21:04
mrhillsmangot it, thx21:05
clarkbbut your job config in zuul itself won't be updated21:05
*** rlandy is now known as rlandy|afk21:05
mrhillsmancool, ty sir21:05
clarkbmrhillsman: and the reason for that is to prevent someone from pushing up a commit that exposes your secrets or otherwise updates how sensitive jobs run without being reviewed by a human first21:05
mrhillsmantotally understand21:06
*** gouthamr has quit IRC21:06
clarkbI should clarify I don't think they necessarily have to merge first they just have to get into a trusted pipeline21:06
mrhillsmanalso after reading through docs the last couple days, which i have more to do, now that i look at our main.yaml i think it needs some changing in general21:06
mrhillsmanwhat's a "trusted pipeline"? docs search returns empty21:07
mrhillsmanor what qualifies a pipeline as trusted is probably better question21:08
clarkbmrhillsman: https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/pipelines.yaml#n6921:08
corvusclarkb: i think config changes to trusted-projects always have to land before being used21:08
clarkbcorvus: ah ok21:08
mrhillsmanah ok, need to read post-review, pabelanger mentioned something of this to me not long ago21:09
mrhillsmanthx for clarity corvus21:09
clarkbso there are two levels of control here. The first being for trusted repos themselves and the second (post-review) for consuming secrets in general21:09
mrhillsmani think the docs say that21:09
mrhillsmantrusted-projects having to land first21:09
mrhillsmanbut again, i think we have it wrong21:10
mrhillsmanopenlab-zuul-jobs should be ok not being trusted21:10
mrhillsmanor we need to move some things out of it21:11
mrhillsmani'm leaning towards the latter21:11
mrhillsmanthx again for the clarity21:11
corvusmordred: i got an npm error which i don't understand: http://paste.openstack.org/show/719100/21:11
*** hongbin has joined #zuul21:12
pabelangermrhillsman: yah, that was related to how openlab as using secrets and untrusted jobs21:13
pabelangerwhich, would leak on proposed PRs21:13
mrhillsmanyep, i remember you saying that, still have more reading to do but experimenting and reading is helping :)21:14
mrhillsmani have a test environment setup so when i look at the live main.yaml it looks awkward based on my reading and definitely the change i mentioned should not be restricted to trusted-project constraints21:15
*** gouthamr has joined #zuul21:15
*** JasonCL has quit IRC21:16
corvusmordred: okay, apparently "rm -rf node_modules" then "npm run build" fixed that...21:24
corvusmordred: is that... erm, the only way to fix such errors?  it seems... nuclear.21:24
*** openstackstatus has quit IRC21:27
*** openstack has joined #zuul21:31
*** ChanServ sets mode: +o openstack21:31
*** hasharAway has quit IRC21:33
mordredcorvus: sorry - was debugging jaascript in a different window ...21:44
clarkbinitial data back on reducing concurrency of testr is it took 12 minutes 8 seconds on ovh-bhs1. http://logs.openstack.org/52/559852/4/gate/tox-py35/696a8da/job-output.txt http://logs.openstack.org/10/561010/3/gate/tox-py35/bef3fc5/job-output.txt http://logs.openstack.org/83/560983/1/check/tox-py35/c0c3e8f/job-output.txt http://logs.openstack.org/65/560265/1/check/tox-py35/cc666ea/job-output.txt are all zuul21:46
clarkbtox-py35 jobs that have run recetnly on the same cloud region and range from ~11-13 minutes in runtime21:46
mordredcorvus: in this particular case, the issue stems from the fact that we landed the patch to upgrade webpack from 2 to 4 , so the locally installed version of webpack did not know how to deal with the config files21:46
clarkbso I don't think this makes the jobs significantly slower ( at least not in that cloud ). I guess it doesn't tell us anything about reliability. I have rechecked it to continue to get more info21:46
mordredcorvus: you could also have run "yarn install" (which would have updated your installed depends to match the declared depends)21:46
mordredcorvus: (and also would not re-download all the things from node_modules) - but, it is always safe to just delete node_modules and start over21:47
clarkbmordred: does it not realize that it needed to upgrade webpack 4 before packing things?21:48
clarkbmordred: seems like that is something yarn should know how to do?21:48
clarkbor maybe its npm?21:48
*** JasonCL has joined #zuul21:52
*** gouthamr has quit IRC21:54
*** JasonCL has quit IRC21:56
mordredclarkb: it's two different actions - 'npm run build' is like 'python setup.py bdist_wheel' - and 'yarn install' is like 'pip install -r requirements.txt' - if you did the pip install, then did a git pull that pulled in a new entry in requirements, you'd need to run pip install again - python setup.py bdist_wheel would not install changed requirements for you21:57
mordredalso - webpack is actually the top-level command line tool - 'npm run build' actually just runs 'webpack --env=prod'21:58
mordred(but is able to resolve the webpack command from node_modules/.bin/webpack so you don't have to type that)21:58
corvusmordred: ok, 'yarn install' is the thing i was missing here, thanks21:59
corvusmordred: also, i know the feeling (debugging js in another window :)21:59
mordredcorvus: :)21:59
mordredcorvus: which js are you debugging?21:59
corvusmordred: i'm making the status page do terrible things :)22:00
corvus(i'm not having any current issues; i'm making progress)22:00
mordredcorvus: yay!22:02
*** hongbin has left #zuul22:02
*** harlowja has joined #zuul22:24
*** JasonCL has joined #zuul22:31
*** JasonCL has quit IRC22:35
*** JasonCL has joined #zuul22:58
*** JasonCL has quit IRC23:00
*** JasonCL has joined #zuul23:01
*** JasonCL has quit IRC23:03
*** JasonCL has joined #zuul23:06
*** JasonCL has quit IRC23:07
*** JasonCL has joined #zuul23:13
*** JasonCL has quit IRC23:15
*** gouthamr has joined #zuul23:21
*** JasonCL has joined #zuul23:33
*** JasonCL has quit IRC23:34
*** JasonCL has joined #zuul23:36
-openstackstatus- NOTICE: The Etherpad service at https://etherpad.openstack.org/ is being restarted to pick up the latest release version; browsers should see only a brief ~1min blip before reconnecting automatically to active pads23:41
*** JasonCL has quit IRC23:41
*** JasonCL has joined #zuul23:44
*** JasonCL has quit IRC23:49
*** JasonCL has joined #zuul23:50
*** JasonCL has quit IRC23:55

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