Monday, 2018-11-26

*** bhavikdbavishi has joined #zuul03:02
*** sshnaidm is now known as sshnaidm|afk04:07
*** chkumar has joined #zuul04:34
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769104:37
*** bjackman has joined #zuul05:22
*** chkumar is now known as chkumar|ruck05:27
*** chkumar has joined #zuul05:44
*** chkumar|ruck has quit IRC05:47
*** chkumar has quit IRC05:48
*** chkumar246 has joined #zuul06:03
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769106:04
*** bhavikdbavishi1 has joined #zuul06:17
*** bhavikdbavishi has quit IRC06:18
*** bhavikdbavishi1 is now known as bhavikdbavishi06:19
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769106:36
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769106:39
*** chkumar246 is now known as chkumar|ruck06:44
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769106:46
SpamapSSeeing how we're testing the markdownlint job by poking a recheck in sandbox makes me think we may actually want that to be a feature in Zuul06:46
SpamapSWould be cool if one could put a in a pipeline on zuul-jobs that basically says "hey, when this job runs, actually run that project's job, as a depends-on for this change"06:50
SpamapSs/a in a/a thing in a/06:51
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769106:58
*** bjackman has quit IRC06:59
*** quiquell|off is now known as quiquell07:11
*** bjackman has joined #zuul07:29
bjackmanOh BTW I subbed to Zuul-discuss but when I sent a mail I still got "Post by non-member to a members-only list" - if I just wait will it get approved?07:42
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul-jobs master: Add a markdownlint job and role  https://review.openstack.org/60769107:49
quiquellGood morning, is possible to call zuul's rpc listener with curl ?08:24
tobiashquiquell: zuul's rpc listener uses gearman so no curl08:32
quiquelltobiash: I see we have a ansible-role-gearman https://github.com/openstack/ansible-role-gearman08:32
quiquelltobiash: just want to call get_tenants to check that zuul is up08:32
tobiashquiquell: the list of tenants can be queried from zuul-web (which uses rpc listener)08:33
quiquelltobiash: And to do it command line ?08:33
quiquelltobiash: Humm ahh I can call zuul-web interface with curl :-) silly me08:34
tobiashyes :)08:34
quiquelltobiash: chanks btw, is this any good ? https://review.openstack.org/#/c/618484/08:34
quiquelltobiash: was not sure about it08:34
tobiashquiquell: I think it's better than displaying the loading..., but maybe we want finally an error message in the web ui in that case08:36
SpamapSquiquell: note that the zuul web UI does exactly that. :)08:38
quiquellSpamapS: yep, I was stubborn with gearman, just forgot about cool zuul API you have there,08:39
SpamapSAPI's, they're all the rage with the kids these days.08:39
quiquellSpamapS: I want to be a kid to forbot about my age that's why I always APIs08:39
quiquells/forbot/forget/g08:40
quiquellSpamapS: What's the best api endpoint to check scheduler is up and running ?08:40
quiquellSpamapS: api/tenants or sapi/status ?08:40
SpamapSprobably status08:42
SpamapSsince that one is tailored for white label vs. multi-tenant08:42
quiquellSpamapS: cool cool08:43
SpamapSactually /api/info might be better08:43
*** jpena|off is now known as jpena08:49
*** hashar has joined #zuul08:53
*** themroc has joined #zuul08:57
quiquellSpamapS: working thanks !! btw do you control how much do you hit gerrit ?09:07
*** kklimonda_ has joined #zuul09:17
*** TheJulia_ has joined #zuul09:17
*** spsurya_ has joined #zuul09:17
*** bhavikdbavishi has quit IRC09:21
*** mgagne_ has joined #zuul09:23
*** spsurya has quit IRC09:25
*** zigo has quit IRC09:25
*** samccann has quit IRC09:25
*** EmilienM has quit IRC09:25
*** mgagne has quit IRC09:25
*** TheJulia has quit IRC09:25
*** kklimonda has quit IRC09:25
*** spsurya_ is now known as spsurya09:25
*** kklimonda_ is now known as kklimonda09:25
*** TheJulia_ is now known as TheJulia09:25
*** chkumar|ruck has quit IRC09:29
*** chkumar246 has joined #zuul09:31
*** chkumar246 is now known as chkumar|ruck09:31
quiquellSpamapS: best way I found was status and check zuul_status inside it, it also tell you if tenant is not ready09:39
openstackgerritQuique Llorente proposed openstack-infra/zuul master: Do a proper wait for zuul at quickstart  https://review.openstack.org/61999309:45
bjackman(The reason my Zuul-discuss wasn't working turned out to be because there's a confirmation request, and it was going into my junk folder. I honestly thought spam filter false positives were a thing of the past!)09:45
quiquelltobiash, SpamapS: ^ imeplemented a proper wait for zuul for the quickstart09:45
quiquellSpamapS: also this to have the model before sql connection is ready https://review.openstack.org/#/c/618484/09:52
*** nilashishc has joined #zuul09:52
*** gtema has joined #zuul09:56
*** sshnaidm|afk is now known as sshnaidm10:07
*** zxiiro has joined #zuul10:12
bjackmanSo, the thing I was going to propose last week (where we only put a change into a pipeline once the whole Gerrit stack has been approved), it is not quite as simple as I thought10:26
bjackmanHaving looked a bit more at the Zuul code I realise that the idea of 1 "change" == 1 job is baked pretty deeply in, and for Gerrit 1 change == 1 commit10:27
bjackmanSo I think to get a situation where 1 job tests multiple commits I need to break one of those equivalences10:28
bjackmanDoes that sound correct?10:29
tobiashbjackman: yes, the pipelines are change centric so we might need a virtual change as a container for more changes10:34
bjackmantobiash, OK10:42
bjackmanOh BTW, is the word "item" a special piece of Zuul jargon?10:52
*** electrofelix has joined #zuul10:59
tobiashbjackman: you mean the item in a pipeline? I would be more precise and name it QueueItem ;)11:08
tobiashbjackman: a queue item contains the change and the buildset which holds the current state of the running and planned job executions of the queue item11:09
bjackmanOK yeah that's probably the thing I'm thinking of11:11
bjackmantobiash, E.g. the "item" passed to *Reporter.report11:11
tobiashbjackman: yes, that should be the queue item11:22
*** gtema has quit IRC11:25
*** bhavikdbavishi has joined #zuul11:32
*** dkehn has quit IRC11:39
*** rfolco has joined #zuul11:54
*** hashar has quit IRC12:10
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Propose to move submit-log-processor-jobs and submit-logstash-jobs in zuul-jobs  https://review.openstack.org/53784712:16
SpamapSquiquell: I use Github actually.12:28
quiquellSpamapS: what do you mean ?12:28
SpamapSYou asked if I control how much I hit gerrit.12:29
quiquellSpamapS: ahh ok, no problem was a red herring12:29
*** gtema has joined #zuul12:29
SpamapSbjackman: For your situation, you should juse use merge commits.12:29
SpamapSbjackman: You can have 1 change in gerrit be a merge from another branch that has multiple commits stacked.12:30
SpamapSThat's not how OpenStack does things, because merge commits can be a real PITA, but if you want that more atomic unit of many commits.. that's the way to go.12:30
SpamapSIt's actually not a bad way to test syncs from an upstream open source repo all at once.12:31
*** jpena is now known as jpena|lunch12:38
*** bhavikdbavishi has quit IRC12:41
tobiashSpamapS: grouping changes together would solve the circular dependencies use case too (I know that's a bad habit but in some cases there is no way around it)12:45
bjackmanSpamapS, won't the commits that show up in the merge commit show up in the needs_changes anyway?\12:47
tobiashI don't think so12:48
*** bjackman_ has joined #zuul12:53
bjackman_tobiash, SpamapS: Yeah that's interesting, Zuul consideres the merge commit as a single change12:54
bjackman_However Gerrit won't let it merge the merge commit if the commits that it merges haven't already got the requried approvals12:54
bjackman_So you'd still have to run each of those commits through the pipeline12:55
*** hashar has joined #zuul12:55
bjackman_Unless you play funny games with Gerrit's submittability predicates12:56
*** EmilienM has joined #zuul12:57
*** rlandy has joined #zuul12:57
*** bjackman has quit IRC13:03
*** bjackman_ has quit IRC13:04
*** bjackman has joined #zuul13:04
SpamapSno13:13
SpamapSYou don't vote on commits13:13
SpamapSyou vote on changes13:13
SpamapSThe problem is that you're doing ff merges13:13
SpamapSbjackman: git merge --no-ff should get the job done.13:13
bjackmanSpamapS, I used --no-ff13:14
SpamapSHm, that's super weird then.13:14
SpamapSBecause Gerrit's model just treats that as one "change"13:14
bjackmanSpamapS, the merged commits are showing up in the UI in the "Relation chain" bit13:14
SpamapSIt's possible zuul has assumptions around commit:change 1:1 ... but it shouldn't.13:15
bjackmanSpamapS, I have 3 changes in gerrit13:15
SpamapSbjackman: that's weird, but my experience on this is now 2 years old so it's possible there are just weird gerrit things that I don't understand.13:15
bjackmanSpamapS, Git log looks like this: https://paste.gnome.org/pf6aehdqj13:16
SpamapSdoh.. I forgot to go to sleep last night I was having so much fun automating stuff w/ zuul :-P13:16
bjackmanSpamapS, they all have Change-Ids13:16
SpamapSbjackman: yeah, I'd expect only one "Change" to matter.13:16
SpamapShaving lots of change-id's should be fine, because Gerrit is looking at refs on top of branches... and that is one ref, the merge commit, on top of one branch, master.13:17
bjackmanSpamapS, TBH I wouldn't want Gerrit to let me merge a merge commit without having the necessary approvals on the commits that it merges13:17
SpamapSit likely just picked them up as related and there may be a way to make your gerrit not apply rules to related changes like that. I dunno.13:18
bjackman(Sorry, on the changes corresponding to the commits that it merges)13:18
SpamapSbjackman: it's entirely possible I don't actually understand. ;)13:18
bjackmanSpamapS, Haha OK13:19
bjackmanI'm gona go ahead with my attempt to design a zuul "change" that encapsulates multiple Gerrit changes13:19
bjackman(Unfortunate that zuul and Gerrit will still be using the same word "change" though)13:20
*** hashar has quit IRC13:22
*** hashar has joined #zuul13:25
*** jpena|lunch is now known as jpena13:29
*** gouthamr has quit IRC13:34
openstackgerritFabien Boucher proposed openstack-infra/zuul-jobs master: Propose to move submit-log-processor-jobs and submit-logstash-jobs in zuul-jobs  https://review.openstack.org/53784713:37
*** gouthamr has joined #zuul13:40
*** dkehn has joined #zuul13:41
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Fix docstring on test_node_executor_zone test  https://review.openstack.org/62005613:49
pabelangerclarkb: follow up to your nodepool review the other day^13:50
*** dmellado has quit IRC13:51
*** bjackman has quit IRC13:52
*** dmellado has joined #zuul13:53
*** chkumar|ruck has quit IRC14:14
*** hashar has quit IRC14:23
*** hashar has joined #zuul14:30
*** nilashishc has quit IRC14:30
*** bhavikdbavishi has joined #zuul14:30
*** gtema has quit IRC14:37
* Shrews waves from the other side of a 2 week rest period14:42
* tobiash hands Shrews a welcome back cake14:47
*** bhavikdbavishi has quit IRC14:56
*** quiquell is now known as quiquell|off14:58
* corvus cuts a piece of cake15:05
tobiashcorvus, Shrews: I think the cache stack (ends at 619589) is ready for review15:12
tobiashit also includes cache driven stats updating :)15:12
Shrewstobiash: oh, i thought i +2'd at least a portion of that stack before i left. will look again shortly15:13
tobiashShrews: yes the first three still have your +2 :)15:13
Shrewsoh good15:14
*** chkumar|away has joined #zuul15:14
tobiashShrews, corvus: maybe we also should decide if we want a release note or not on 61626215:15
Shrewstobiash: corvus: my thinking on that release note was mainly for folks closely following the changes and noticed that schema changes usually result in headaches (i had clarkb specifically in mind  :) and thought it would be good to have something that said "yes, we considered this"15:19
Shrewsi mostly wanted it there in case we needed a restart while I was away, but now that i'm back, i can go either way on having it or not15:20
corvusShrews: yeah.... if we could find a way to do that without suggesting that people might be interested in using data in zookeeper, i'd be more keen.  also, i like the idea of reserving release notes for when action is required or suggested, so that there aren't too many of them, so people might read them :)15:22
tobiashShrews, corvus: so as there is no action required shall I just remove it?15:22
tobiashnow re-reading it the category 'features' is wring anyway15:23
tobiashs/wring/wrong15:23
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add resource metadata to nodes  https://review.openstack.org/61626215:23
tobiashremoved it ^15:24
*** dmsimard has quit IRC15:35
*** dmsimard has joined #zuul15:36
*** chkumar|away has quit IRC16:11
*** rlandy_ has joined #zuul16:25
*** rlandy has quit IRC16:27
*** themroc has quit IRC16:42
*** caphrim007_ has quit IRC16:42
*** hashar has quit IRC16:42
*** caphrim007_ has joined #zuul16:42
*** rlandy_ is now known as rlandy16:49
*** quiquell|off has quit IRC16:59
Shrewscorvus: GKE == Google K8S Engine?17:12
corvusShrews: yep17:12
Shrewsthat seems easier to use than minikube  :)17:13
Shrewshow long is the trial period?17:13
corvusShrews: well, up until they start charging you money.  :)  i just used it to verify their default behavior (since it was a question of what policies they implement)17:13
corvusShrews: $300 worth over a year i believe17:14
*** samccann has joined #zuul17:22
corvustobiash, Shrews: can you take a look at my comment on https://review.openstack.org/619025 ?17:46
Shrewscorvus: no, but only because it does not exist17:47
corvusoh, ha.  i guess gerrit is slow.  i have 75 items in my gertty sync queue.17:48
tobiashmust be a huge comment17:57
corvusShrews, tobiash: it's there now17:59
tobiashcorvus: yes, the reason was that the delayed event might change the already locked node18:03
Shrewscorvus: tobiash: hrm, good point on the version numbers. I was wondering if/when we'd ever need to use those. Might make sense here.18:04
tobiashyes, that could probably work18:04
openstackgerritMerged openstack-infra/nodepool master: Add resource metadata to nodes  https://review.openstack.org/61626218:05
tobiashcorvus, Shrews: maybe we should also check the lock attribute to be safe?18:10
*** jpena is now known as jpena|off18:13
*** manjeets has joined #zuul18:14
*** electrofelix has quit IRC18:16
corvustobiash: yes, good idea.  we probably shouldn't only rely on that though, so that we don't update with old data after we release the lock.18:19
openstackgerritMerged openstack-infra/nodepool master: Support node caching in the nodeIterator  https://review.openstack.org/60464818:19
pabelangercorvus: Shrews: if you don't mind adding https://review.openstack.org/618622/ to your review queue, that is required for zone support for zuul-executors: https://review.openstack.org/549197/ I believe it is in good shape to maybe land this week18:21
corvuspabelanger: will do18:25
tobiashhrm, need to rebase the whole stack to fix merge conflicts :/18:32
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Update node during lockNode  https://review.openstack.org/61645018:36
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Update node during lockNode  https://review.openstack.org/61645018:37
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add extra safety belt when reusing a node  https://review.openstack.org/61646518:39
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Cache node request zNodes  https://review.openstack.org/61880618:39
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Update node request during locking  https://review.openstack.org/61880718:39
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Update node request during locking  https://review.openstack.org/61880718:40
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add second level cache of nodes  https://review.openstack.org/61902518:43
*** bjackman has joined #zuul18:44
*** sshnaidm is now known as sshnaidm|afk18:48
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add second level cache of nodes  https://review.openstack.org/61902518:56
tobiashcorvus, Shrews: this updates the nodes in-place as suggested ^18:57
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add second level cache of nodes  https://review.openstack.org/61902519:04
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add second level cache to node requests  https://review.openstack.org/61906919:06
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Only setup zNode caches in launcher  https://review.openstack.org/61944019:06
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Asynchronously update node statistics  https://review.openstack.org/61958919:06
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Add second level cache to node requests  https://review.openstack.org/61906919:12
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Only setup zNode caches in launcher  https://review.openstack.org/61944019:13
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Asynchronously update node statistics  https://review.openstack.org/61958919:13
tobiashsorry for spamming, I tried to separate rebasing from updating due to comments19:14
fungiseparating rebase conflict resolution from other more substantial modifications is very much appreciated, so no need to apologize19:16
*** hashar has joined #zuul19:28
*** bjackman has quit IRC19:49
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Report tenant and project specific resource usage stats  https://review.openstack.org/61630620:04
Shrewspabelanger: can you walk me through what is supposed to happen with the use of executor-zone? Where is that attribute used?20:14
pabelangerShrews: sure, https://review.openstack.org/549197/ is the zuul change which will use it.  By itself, nodepool won't actually use that setting for anything20:15
Shrewspabelanger: ah, that's what i was looking for. thx20:15
pabelangernp!20:15
Shrewstopic was different20:15
pabelangerhopefully admin/components.rst will explain, if not we can add the missing info20:15
pabelangerah, we should make them the same20:15
pabelangerI can do that now20:15
Shrewspabelanger: You'll probably want to consider the case of someone upgrading and moving everything into zones. That would leave pre-existing, unassigned nodes laying around unused. Probably deserves an upgrade comment at the very least.20:23
pabelangerShrews: on the nodepool side?21:01
pabelangeryah, maybe we should add something about the version of zuul that will actually support it21:01
Shrewspabelanger: I'm not sure which would be the best place to document it. This is the first nodepool config option that specifically mentions affecting zuul functionality. Maybe both?21:03
pabelangeryah, I don't think we've specifically stated a min version of each before21:04
pabelangerwhat do we think the next version of nodepool is, 3.4.0?21:05
pabelangerand 3.4.0 for zuul?21:06
corvusShrews: i don't think we'll end up with unused node21:06
pabelangerif so, that lines up pretty well actuallyt21:06
corvusif a node doesn't have a zone, any executor can run jobs on it21:06
corvusi'm in favor of cross-documenting and having upgrade notes -- just wanted to point out that i don't think there's a big risk of wedging the upgrade21:07
Shrewscorvus: i don't think the proposed code does that. lemme check again21:08
corvusShrews: i haven't finished reviewing it; it may not :)21:08
Shrewscorvus: oh, i think it does, actually21:08
Shrewsbut will let pabelanger confirm. if so, that solves that21:09
corvuswell, it looks like the executor only registers "executor:execute:zone" if a zone is enabled21:10
Shrewsyeah. i didn't review it closely enough21:10
pabelangeryah, on the nodepool side, there isn't any extra logic, we just write the executor_zone into zk, so if that is setup and old zuul is used, should be a noop21:10
corvusShrews: so i think your concern is validated.  we either need an upgrade note that discusses the possibility of wedging if there are zoneless nodes and no zoneless executors.  or we need to have executors register both functions.21:11
corvuspabelanger: yeah, i think the risk is that zuul is upgraded and all executors have zones assigned and either nodepool is not upgraded, or existing ready nodes stick around and can't be used.21:12
pabelangerah, right21:12
pabelangerso maybe a note on nodepool side to purge ready nodes is a good idea21:13
pabelangeron upgrade21:13
Shrewscorvus: pabelanger: I'm starting to wonder if we should consider an arbitrary node.metadata attribute that can contain any data defined in the config (say in a pool.node_metadata config option). Then we could be out of the business of modifying the zk schema for functionality needed by any user of nodepool21:14
corvusi don't know whether it would be better to have executors register "executor:execute" and "executor:execute:zone", so that any executor is automatically able to run jobs for any zone-less nodes.  or whether we should just leave that up to the user to run extra zone-less executors.21:14
corvusShrews: i don't think this is necessarily zuul-specific.  it's basically a way to indicate the topology of a node so that the consumer knows "where" it is.21:15
pabelangermy first thought is to leave it up to the user to define a zone-less executor21:15
pabelangerbut, I can see the value in having one of your zoned executors also register executor:execute, if it is able to still reach all other providers21:16
corvusShrews: (still, nodepool is part of zuul, so if we need something for zuul, i think we should add it.  it's just that, in this case, i think we're adding a pretty generic piece of information in a generically useful way.  which is how i'd prefer to do things)21:16
Shrewscorvus: that's what i was (poorly) trying to say. generic stuff could go in the easily changed metadata attribute (without code changes in np).21:17
corvusShrews: but looking past that -- if you think adding zones as part of a generic metadata framework is better, i could see that.21:17
corvusShrews: yeah, i'm starting to grok21:17
Shrewsi can see more such requests for this type of data as we add more drivers21:18
corvuspabelanger: let's keep things simple for now and just put in the upgrade note, and leave it to the user to create zone-less executors if needed.  maybe we can add an option to also register zoneless-execute if folks want.21:19
pabelangerwfm21:20
corvusShrews: oh, i see the field is called "executor-zone" in nodepool.  that does make it sound a bit zuulish doesn't it? :)21:21
Shrewscorvus: yes  :)21:21
Shrewsthe genesis of my brain itch21:22
corvusi was imagining it was called 'zone'; i guess that's to disambiguate it from 'availability-zone'21:22
corvusShrews: i'm digging your idea.  i like the use of 'executor-zone' more in that context too.  so the config value would be 'provider.pool.metadata.executor-zone' and that sets node.metadata.executor-zone21:27
corvuspabelanger: what do you think about one more round on the nodepool side? ^21:27
pabelangercorvus: sure, I don't mind updating21:28
Shrewscorvus: exactly (while gesturing hand wavily)21:29
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Add release note for executor-zone setting  https://review.openstack.org/62016421:31
pabelangerokay, that is the release note, but obviously things have changed a little21:31
pabelangerneed to step away for food shortly, but can update the patches for new metadata structure21:31
corvusShrews: you want to leave a -1 for that?21:34
Shrewsi can, sure21:35
Shrewsi think i captured the discussion in my review comment21:42
corvusShrews: i left a followup comment21:50
Shrewscorvus: oh, yeah21:52
Shrewscorvus: my brain is obviously still ramping up21:52
corvusShrews: i know the feeling.  and now it's time to ramp down for the day :)21:52
*** jlvillal has joined #zuul22:00
pabelangercorvus: Shrews: also left comment22:05
ianwpabelanger: mind an eye on the f27 cleanup in nodepool @ https://review.openstack.org/#/c/618416/ and then then the mirroring change @ https://review.openstack.org/614375 if you have a minute?22:26
ianwoh, i think they're backwards, but that's the two changes22:27
openstackgerritMerged openstack-infra/zuul master: Do a proper wait for zuul at quickstart  https://review.openstack.org/61999322:28
ianwi wonder what "waiting" means in the zuul job queue graph -> http://grafana.openstack.org/d/T6vSHcSik/zuul-status?panelId=18&fullscreen&orgId=122:54
ianwi guess this is not the same a "queued"22:54
ianwstats.gauges.zuul.geard.queue.waiting22:55
corvusianw: yeah, it's all gearman jobs.22:56
corvusianw: it's not as interesting as the individual executor queue or merger queue graphs22:56
corvusianw: (which break out the overall queue by function)22:56
hasharhello! I know I am inactive, but if you plan to upgrade Gerrit from 2.13  Zuul might have a ton of corner case bugs.   I have a few hotfix on our old Zuul 2.5,  will eventually check whether Zuul 3 is affected :)22:57
corvushashar: thanks!  i know i've seen some post 2.13 changes go by, and we just got a 2.16 patch (to support the new change url syntax)22:58
hasharcorvus: hopefully I will have some time to write a quick report for the gotchas I found22:58
ianwcorvus: hrm, you mean http://grafana.openstack.org/d/T6vSHcSik/zuul-status?panelId=24&fullscreen&orgId=1 ?22:58
corvushashar: great, thanks!22:58
corvusianw: yes and http://grafana.openstack.org/d/T6vSHcSik/zuul-status?panelId=31&fullscreen&orgId=122:59
hasharcorvus: then next, I will try to setup a quick Zuul v3 poc for Wikimedia .Not sure whether we will retain Zuul though :-\22:59
corvushashar: have you seen https://zuul-ci.org/start22:59
corvushashar: that may help you get a v3 POC up quickly23:00
hasharcorvus: I have tried docker compose up from the example directory and got something running :)23:01
hasharah yeah that is the tutorial I have been following.  Congratulations for that documentation23:01
ianwcorvus: hrm, but the queued jobs is currently zero?  do we only really track the backlog in the outstanding node requests?23:02
corvushogepodge: \o/23:02
openstackgerritMerged openstack-infra/zuul master: Add config parameters for WinRM timeouts  https://review.openstack.org/61963023:02
corvusianw: yes and yes.  those metrics really represent zuul health.  for example: if executor queue is >0 for a sustained time, add more executors.23:02
ianwok, cool23:03
openstackgerritMerged openstack-infra/zuul master: Setup model before connection  https://review.openstack.org/61848423:05
openstackgerritMerged openstack-infra/zuul master: Include executor variables in initial setup call  https://review.openstack.org/60103623:06
openstackgerritMerged openstack-infra/zuul master: python3: Can't have unbuffered non-binary I/O  https://review.openstack.org/60103723:09
*** hashar has quit IRC23:26
*** rlandy has quit IRC23:30

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