Tuesday, 2018-06-26

*** rlandy has quit IRC00:00
*** yolanda_ has joined #zuul00:06
*** yolanda__ has quit IRC00:09
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add min_avail_hdd governor for zuul-executor  https://review.openstack.org/57794800:09
pabelangertristanC: clarkb: fungi: corvus: tristanC: first attempt at HDD governor for executor^00:10
*** harlowja has quit IRC01:46
*** mordred has quit IRC01:49
*** mordred has joined #zuul02:07
*** tovin07 has joined #zuul02:08
*** tovin07 has quit IRC02:10
*** yolanda__ has joined #zuul03:15
*** yolanda_ has quit IRC03:18
*** yolanda__ has quit IRC03:23
*** yolanda__ has joined #zuul03:29
*** yolanda_ has joined #zuul03:34
*** yolanda__ has quit IRC03:36
*** yolanda__ has joined #zuul03:44
*** yolanda_ has quit IRC03:45
*** yolanda_ has joined #zuul04:03
*** yolanda__ has quit IRC04:06
*** yolanda has joined #zuul04:08
*** yolanda_ has quit IRC04:09
*** yolanda_ has joined #zuul04:10
*** yolanda has quit IRC04:13
*** nchakrab has joined #zuul04:30
*** nchakrab_ has joined #zuul04:48
*** nchakrab has quit IRC04:48
*** CrayZee has joined #zuul05:07
*** nchakrab has joined #zuul05:35
*** nchakra__ has joined #zuul05:37
*** nchakrab_ has quit IRC05:38
*** nchakrab has quit IRC05:40
*** Rohaan has joined #zuul05:50
*** snapiri- has joined #zuul05:53
*** CrayZee has quit IRC05:56
*** openstackgerrit has quit IRC06:04
*** nchakrab has joined #zuul06:09
*** nchakrab_ has joined #zuul06:12
*** nchakra__ has quit IRC06:12
*** nchakrab has quit IRC06:16
tristanCpabelanger: since we added more review.openstack.org projects to rdoproject zuul, it seems like the pipeline manager is queueing merge job, even when we don't include any configuration from those projects06:20
*** yolanda__ has joined #zuul06:21
tristanCthere is currently a 20 PS stack for nova that is starving our resources06:22
*** yolanda_ has quit IRC06:24
tristanCshouldn't the manager prepareItem returns early if the project is configured with include: [] ?06:24
*** nchakrab_ has quit IRC06:29
*** gtema has joined #zuul06:49
*** nchakrab has joined #zuul06:56
*** hashar has joined #zuul07:06
*** pcaruana has joined #zuul07:20
*** jpena|off is now known as jpena07:44
*** nchakrab has quit IRC07:56
*** nchakrab has joined #zuul07:58
*** nchakrab has quit IRC08:02
*** nchakrab has joined #zuul08:06
tobiashtristanC: I noticed that we occationally have zk connection losses (like http://paste.openstack.org/show/724289/)08:12
tobiashtristanC: I think you also had trouble with zk. Did an increased session timeout help?08:12
tristanCtobiash: iiuc, merger:cat job doesn't rely on zookeeper08:15
*** nchakrab has quit IRC08:21
tobiashtristanC: oh that was unrelated to your merger question ;)08:22
tobiashtristanC: I was asking because you started that zookeeper discussion some time ago08:23
*** nchakrab has joined #zuul08:23
tobiashtristanC: that zookeeper connection loss triggers mass deletion of our nodes every now and then08:23
tristanCtobiash: it used to do that for us too...08:25
*** nchakrab has quit IRC08:25
tristanCtobiash: that's why i'm still using https://review.openstack.org/#/q/status:open+project:openstack-infra/nodepool+branch:master+topic:zookeeper-retry08:25
*** nchakrab_ has joined #zuul08:25
tobiashtristanC: at least the session timeout config has been merged in zuul08:28
tobiashtristanC: what value do you use for the session timeout?08:28
tobiashtristanC: to your problem I'm not sure of we can delay that merger job because it might have some depends-on which depend on zuul.yaml changes08:29
tobiashtristanC: so I see two possibilities there, take out nova from the config or add more merger capacity08:30
*** electrofelix has joined #zuul08:35
tobiashtristanC: oh nevermind, I failed reading diffs... you removed the session timeout in favor of the retry mechanism?08:35
tristanCtobiash: i'm adding more merger, but it seems like the pipeline manager specificaly look for .zuul.yaml, then maybe there is another merge job running for depends-on08:41
tristanCtobiash: about zk-retry, the idea is to completely remove the manual connection loop state check and rather rely on kazoo to retry the action until they succeed08:42
tobiashtristanC: but that doesn't solve the lost session right?08:42
tristanCtobiash: right, if the retry takes too long, then the session still gets lost (it's a server side thing iiuc)08:43
tobiashtristanC: so how did you solve your expired sessions? Did you increase the session timeout?08:43
tristanCtobiash: hum, if i read kazoo doc corrently, the timeout is "The longest to wait for a Zookeeper connection.", (e.g. https://kazoo.readthedocs.io/en/latest/api/client.html )08:49
tobiashtristanC: internally that is mapped to a _session_timeout variable08:50
tristanCi think the only way to increase the timeout is to increase the server tickTime08:51
tristanCtobiash: our issue was that the tcp connection between nodepool and zookeeper got stalled, the get_children called raised a "ConnectionLost", and by the time kazoo reconnect, we lost the session08:52
tristanCand since we switched to using kazoo retry feature, then we no longer have connection loss or session loss issue08:53
tristanCand i didn't see any duplicate node request or zknode leak, but we only run one launcher and one builder08:54
*** openstackgerrit has joined #zuul09:04
openstackgerritTristan Cacqueray proposed openstack-infra/nodepool master: zk: use kazoo retry facilities  https://review.openstack.org/53553709:04
*** yolanda_ has joined #zuul09:50
*** yolanda__ has quit IRC09:53
*** Rohaan has quit IRC10:28
*** sshnaidm|afk is now known as sshnaidm10:30
*** jpena is now known as jpena|lunch11:03
*** nchakrab_ has quit IRC11:36
openstackgerritFabien Boucher proposed openstack-infra/zuul master: Add /etc/localtime to bubblewrap default ro bind  https://review.openstack.org/57807211:44
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Support paging when listing github installations  https://review.openstack.org/57807711:53
tobiashcorvus: looks like we're the first running into paging when enumerating github installations... ^11:54
tobiashclarkb: ^11:54
*** hashar has quit IRC12:13
*** hashar has joined #zuul12:14
*** hashar has joined #zuul12:14
*** jpena|lunch is now known as jpena12:14
*** rlandy has joined #zuul12:30
*** nchakrab has joined #zuul13:02
*** nchakrab_ has joined #zuul13:05
*** nchakrab has quit IRC13:08
*** Rohaan has joined #zuul13:18
*** nchakrab has joined #zuul13:22
openstackgerritArtem Goncharov proposed openstack-infra/nodepool master: retire shade in favor of openstacksdk  https://review.openstack.org/57282913:25
*** nchakrab_ has quit IRC13:25
*** frickler has quit IRC13:26
*** frickler has joined #zuul13:26
*** nchakrab_ has joined #zuul13:29
pabelangerThere are a few governor patches from tobiash and myself starting at: https://review.openstack.org/549275/ if people have some time today to review.  I know the HDD sensor could be helpful to RDO to stop launching jobs when we are close to HDD limits13:30
*** nchakra__ has joined #zuul13:31
*** nchakrab has quit IRC13:32
mordredgtema: heya- I keep meaning to comment on that ^^ and I keep getting distracted. I think we need to keep the nodepool-side flavor caching because we haven't started using the shade/openstacksdk caching layer yet13:34
*** nchakrab_ has quit IRC13:34
mordredpabelanger: all lgtm - I left +A off of the first two just in case corvus wants to look now that he's back from china, but he's +2'd the first one before, so I don't imagine issues13:34
pabelangerwfm13:35
fbohi, is there a strong requierement about the authentication to use the depends-on feature ? I mean I want to use depends-on on a gerrit instance but don't have any account.13:35
gtemamordred: but with a simple `cache: expiration_time:3600` in clouds.yaml it works prefectly (at least I checked manually listing images)13:37
fboI think that's the same if I need to depends-on on a pull request on github, zuul needs to have a github connection that require authentication.13:39
fboCould it be possible to use the git driver with a specific depends-on format ?13:40
*** snapiri- has quit IRC13:41
mordredgtema: yes, this is true. the issue is that today nodepool does the right thing out of the box, while someone would need to configure clouds.yaml. there is a long-languishing task in shade/sdk land to turn caching on by default- at least for some of the things - and it's that that we've been waiting for to remove the nodepool-side caching13:42
gtemamordred: sad, but ok - I will turn caching back13:43
mordredfbo: I don't think the git-driver has cross-source depends-on support yet- the biggest issue there is figuring out what url to give to it - for gerrit you need: git fetch https://git.openstack.org/openstack-infra/nodepool refs/changes/29/572829/313:43
mordredgtema: yeah - I agree. hopefully we'll finish the caching work in sdk and can do it13:43
mordredfbo: and then refs/changes/29/572829/3 is more specific than 572829 ... it's possible though that perhaps some of the things needed are available via unauthenticated REST13:44
gtemamordred: ok13:45
mordredfbo: I think corvus has had some thoughts around this use case before - probably good to chat with him when he gets up13:45
mordredfbo: but for now at least the answer is to add gerrit sources with accounts ... we recently added an account for OpenStack Zuul on the Open Daylight gerrit for this reason13:49
openstackgerritMerged openstack-infra/zuul-jobs master: log-inventory: add missing zuul_info_dir prep  https://review.openstack.org/57767413:59
*** elyezer has quit IRC14:00
fbomordred: ok, thanks for the clarification. I think using something like depends-on: git.openstack.org/openstack/nova:changes/1 could be enough and the git driver should have all it needs to fetch the right git ref.14:03
*** nchakra__ has quit IRC14:10
*** nchakrab has joined #zuul14:10
*** elyezer has joined #zuul14:12
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add min_avail_hdd governor for zuul-executor  https://review.openstack.org/57794814:21
pabelangermordred: sorry, pushed up a docs change^14:21
*** elyezer has quit IRC14:21
*** elyezer has joined #zuul14:23
*** nchakrab has quit IRC14:41
tobiashcorvus, clarkb: 575014 is in front of the multi-enqueue fix which would need a review too14:46
tobiashbut If you want I can unstack that14:46
clarkbtobiash: I will take a look14:47
fungifbo: except that git.openstack.org/openstack/nova:changes/1 isn't something we can generalize to git remotes without some inside knowledge15:29
fungifbo: depends-on: git.openstack.org/openstack/nova:changes/43/76543/21 is at least15:31
fungigerrit doesn't provide a changes/76543 ref, it only provides a sharded and patchset-specific changes/43/76543/21 ref15:32
pabelangerso, I am not sure if I have a bug in zuul or new feature, I am leaning towards new feature. Use case is, if you have a non-voting job and parent that fails, the child will be skipped. But zuul will report a -1 back to gerrit, because the skipped job didn't run. Which, in this case is fine, because we are trying to create some dynamic trigger jobs, without the node request to nodepool. The failing (non-voting)15:42
pabelangerjob has nodes: [], so only zuul-executor uses it.15:42
pabelangerhttps://review.rdoproject.org/r/14462/ is the use case in question15:42
*** pcaruana has quit IRC15:42
pabelangerbasically, propose a new job setting to allow for skipped jobs to not be considered a failure15:43
pabelangerdmsimard: fyi^15:43
dmsimardpabelanger: is that in reference to the rdoinfo dynamic triggers ?15:45
pabelangerdmsimard: yes15:45
dmsimardok so for people interested, we had discussed this a while back: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2017-05-08.log.html#t2017-05-08T15:52:5515:45
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add min_avail_hdd governor for zuul-executor  https://review.openstack.org/57794815:45
dmsimard(more than a year ago now, heh)15:45
pabelangertobiash: now with statsd testing for hdd sensor^15:46
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add min_avail_hdd governor for zuul-executor  https://review.openstack.org/57794815:47
*** Rohaan has quit IRC15:48
corvusfbo: the fundamental issue is more or less what fungi said -- we need to translate a url like "http://review.example.com/1234" to a gerrit git ref.  that's gerrit specific enough that you need the zuul gerrit driver to do it.  right now, that requires authentication.  i have a WIP patch to support the http API for the reporter interface.  if we also added HTTP support for the source interface, and then also15:53
corvusadded support for *unauthenticated* http, i think that would do what you want.15:53
corvuspabelanger, dmsimard: the option sounds sensible to me -- however, i wonder if it would be okay to say that if a non-voting parent fails, treat all the children as non-voting.  i think that's what you meant when you said it might be a bug.  if folks think that's an intuitive behavior, we could probably do that.15:57
pabelangercorvus: correct, that is what I was thinking could be a zuul bug. Assuming all were also okay with that statement15:58
corvusat the moment, i can't think of when you wouldn't want that.  but, i just woke up.15:59
dmsimardcorvus: the use case can be summarized as a parent job dynamically deciding which child jobs should be triggered (based on the results of the parent job) -- pabelanger's approach is something that gets us close to that without too much work I think15:59
corvusdmsimard: i understand16:00
dmsimardcorvus: ack, making sure we're on the same wavelength16:00
pabelangerokay, I'll see if I can figure out how to fix that today16:00
pabelangerthat would allow rdo to drop more dependency on jenkins :)16:01
corvusif we explore the "non-voting parent causes skipped to be non-voting" approach, i think it does cover this use case, but we need to think about other use cases -- does it inhibit something else?16:01
*** elyezer has quit IRC16:02
*** elyezer has joined #zuul16:02
pabelanger+116:04
*** harlowja has joined #zuul16:12
*** elyezer has quit IRC16:15
*** elyezer has joined #zuul16:19
clarkbcorvus: pabelanger i think you should only do that if the children are all non voting too16:26
*** hashar is now known as hasharAway16:26
*** elyezer has quit IRC16:30
pabelangeryah, in this case, the child are voting, the trick is once if the job is running does the results of pass / fail matter. If it is skipped, the result doesn't in that case. I understand it is a different model from today16:32
clarkbthe parent value implicitly matters if the child values do16:33
clarkbthat is the least surprising behavior to me16:33
pabelangerthe only reason the parent is non-voting in this case, is if the condition check to not run the child job is false, then we fail the job.  Making it non-voting doesn't case zuul to leave -1 on patchset16:34
pabelanger(condition check to run the child job is false)16:34
pabelangerthat is the only way I know today to have a child job skip16:35
clarkbmaybe that determination could be modeled in zuul directly and we can solve the actual usecase?16:35
clarkbwhat determines if the child job should run?16:35
pabelangerdmsimard: ^16:35
mordredclarkb: code/logic16:35
pabelangerI want to say some external check16:35
pabelangercurl URL16:36
mordredit's a use case that's come up from a few places - people want to run code more complex than a regex to determine which jobs should run on a patch16:36
dmsimardclarkb: "if grep foo; run job foo; elif grep bar; run job bar; fi"16:36
mordredansible does this inside of ansible-test - it examines the patch and applies some logic to determine which jobs should run16:36
*** elyezer has joined #zuul16:37
clarkbmy immediate reaction to that is run all the jobs and have any that shouldn't run exit 0 and short circuit16:38
mordredI don't think anyone has yet come up with a full suggestion on how zuul could provide direct support for that use case in a way that doesn't get pathological quickly16:38
clarkbrather than have a complex tree of voting and non voting things16:38
mordredclarkb: right - the issue there is in node allocation16:38
mordredclarkb: if you have some node types that are expensive16:38
mordredand you don't want to allocate them for a noop job if you don't have to16:38
pabelangerclarkb: right, we're are also trying not to use nodepool resources, since there is a $$$ cost to that16:39
clarkbthinking out loud more, maybe we need a new job type that is a branch selector explicitly16:39
dmsimardclarkb: what mordred said, we don't have the luxury of spinning nodes up just to exit 0 and return16:39
clarkbrather than hacking voting vs non voting16:39
clarkbthe reason I worry about using non voting in this way is it could very easily lead to +1 results on changes that should hae been -1'd16:40
clarkbbecause as a user if a voting job cannot run that is a failing condition not a successful one16:41
pabelangeragree, this was part of why I figured it was a new feature. Some sort of job attribute you express to say child result doesn't matter if parent failed16:42
clarkbpabelanger: I would avoid failed vs success entirely in this case16:43
pabelangerbut, also not tied to this approach, just something I tested on Friday16:43
clarkbsomething like set enqueue-children in zuul return16:43
pabelangerclarkb: yah, really just need a way from parent not to run a child job. success / fail is only way today16:44
corvusclarkb: er, back up a sec -- if the parent is non-voting, why would you care about the children?16:44
corvus(sorry, i was away for a second, and i'm still mentally back at 16:26)16:44
clarkbcorvus: if the children are voting is the case I worry about (which seems to be pabelanger's case) that implicitly means a failure to run the parent is a failure to run the chidlren which should be a -116:45
corvusclarkb: but why would you set the parent to non-voting in that case?16:45
clarkbbecause voting jobs failed (by not being able to run)16:45
corvusclarkb: oh wait -- you're saying there may be a difference between "parent says children should not run" and "parent barfed" ?16:45
clarkbcorvus: yes16:45
corvusthat is a good point :)16:45
corvusand that case isn't handled by the other suggestion of adding a new flag either.  it really is a different return value.  right?16:46
mordredyeah - it seems like there is a potentially new interface that could be designed here16:46
clarkbyes, the parent would have to set an attribute that zuul evaluates for the child determination16:47
mordredto allow a job to communicate to zuul something about what should happen with children16:47
mordredclarkb: jinx16:47
pabelangeryah, that would work great16:47
corvusthis lines up with the idea of continuing jobs too (keep the parent running while running children) mentioned in the container spec.  i anticipated that as being implemented via zuul_return.  so we could do that here too.16:48
mordred++16:48
mordredseems like between the RDO case and the ansible-test case, we might have 2 good and complex potential users to vet a design against16:48
*** CrayZee has joined #zuul16:49
pabelangercool16:50
corvusit's pretty easy to work with zuul_return data; the plumbing is already there16:51
*** CrayZee has quit IRC16:51
pabelangerany suggestion on attribute name zuul looks at for the child to run?16:54
openstackgerritClark Boylan proposed openstack-infra/zuul-jobs master: Dynamically determine overlay network mtu  https://review.openstack.org/57815316:55
clarkbdmsimard: ^ thta may interest you as you worked on that role a lot16:56
mordredthinking out loud- if we added a variable to the zuul. ansible variables that is the list of child jobs zuul expects to run after the current job based on its understanding of the world - then we could have the capability for someone to return a list in zuul_return that would be either the same list or a smaller list16:57
*** elyezer has quit IRC16:57
corvusmordred: i was just thinking along similar lines :)16:57
dmsimardclarkb: hm I thought we already did something like that16:57
mordredthen there could be a single rdo-selector or ansible-test-selector job with the full pile of dependencies - and it could do $logic and trim the list down16:57
clarkbdmsimard: we make it configurable but don't configure it as far as I can tell16:57
mordredpabelanger: does that seem like a potentially workable thing?16:57
pabelangermordred: yes, I believe so. And cliend jobs not listed show up as SKIPPED for results?16:58
corvusmordred: we may also want to handle the simple case of "run no child jobs"... though, i guess you could do that by just saying: "zuul.child_jobs = []" ?16:58
mordredcorvus: yah16:59
clarkbya devstack calculates a similar value but only for neutron, not the overlay itself16:59
clarkber not the infra overlay16:59
mordredcorvus: andif you don't return child_jobs at all, zuul will not modify its job graph16:59
corvus++16:59
dmsimardclarkb: I guess it's a regression because we used to do it in devstack-gate https://github.com/openstack-infra/devstack-gate/blob/b3da8a393c68cc62924ee2f752f442d5c85ea8ed/devstack-vm-gate.sh#L69-L7316:59
mordredcorvus, pabelanger: I thinkn we'd just not return them - kind of like we do when a job doesn't get run due to a path exclusion16:59
corvuspabelanger: i think with mordred's approach, child jobs won't show up at all?16:59
corvusright17:00
mordredyah17:00
dmsimardclarkb: I'm curious why this is coming up just now (packethost has been enabled for a while) though, I haven't kept up with the backlog17:00
clarkbdmsimard: we don't do it in d-g either, that is only for neutron17:00
dmsimardclarkb: oh, so not for the overlay bridge, got it17:00
clarkbdmsimard: I think its not really popped up much because we only do this on multinode tests and very few of those vote17:00
dmsimardclarkb: added a comment17:02
*** gtema has quit IRC17:02
pabelangermordred: corvus: ack, that would work17:03
clarkbdmsimard: I'm trying to find where we actually use that role outside of ozj tests (but I can depends on ozj and get those tests I think)17:04
clarkboh its in zuul-jobs itself17:05
dmsimardclarkb: the ozj tests would not exercise devstack on top of it, though, but perhaps you could add functional tests to make sure the MTU is as exepcted17:05
dmsimardclarkb: i.e, http://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/tests/multi-node-bridge.yaml17:05
clarkbdmsimard: testing both is probably a good idea. I'll work on some depends on17:05
dmsimard++17:05
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add min_avail_hdd governor for zuul-executor  https://review.openstack.org/57794817:07
pabelangerclarkb: mordred: tobiash: corvus: ^now with working statsd testing17:07
clarkbdmsimard: the ozj tests are run against zuul jobs too, so just need a devstack depends on17:09
*** elyezer has joined #zuul17:09
*** harlowja has quit IRC17:10
clarkbtobiash: https://review.openstack.org/#/c/578077/1 lgtm but I didn't approve it as there isn't a test and I'm not super familiar with the github api details17:23
tobiashclarkb: the paging of the next call isn't tested yet as well. I hope I have time to work on testing these two.17:25
tobiashBut I'm completely in fire fighting mode this week so far :/17:25
openstackgerritClark Boylan proposed openstack-infra/zuul-jobs master: Dynamically determine overlay network mtu  https://review.openstack.org/57815317:43
*** jpena is now known as jpena|off17:49
*** electrofelix has quit IRC17:52
mordredgundalow: conversation starting 1.25 hours ago about filtering of child/dependent jobs that RDO needs that I thnik likely applies to ansible-test too18:01
openstackgerritClark Boylan proposed openstack-infra/zuul-jobs master: Dynamically determine overlay network mtu  https://review.openstack.org/57815318:11
openstackgerritClark Boylan proposed openstack-infra/zuul-jobs master: Dynamically determine overlay network mtu  https://review.openstack.org/57815318:13
clarkbthis whole ip isn't in your path thing18:15
clarkbseems like a bug that asnible/centos should fix18:15
mordredclarkb: ++18:24
gundalowmordred: Thanks18:27
*** dmellado has quit IRC18:32
*** gouthamr has quit IRC18:32
*** bhavik1 has joined #zuul18:34
*** bhavik1 has quit IRC18:38
*** yolanda__ has joined #zuul19:04
*** yolanda_ has quit IRC19:07
*** yolanda_ has joined #zuul19:09
pabelangermordred: corvus: clarkb: do we pre-populate the inventory with zuul.child_jobs for the parent? Or just look for zuul.child_jobs in zuul_return?  If I parse before correctly, it was always add zuul.child_jobs to inventory file19:09
*** sshnaidm has quit IRC19:09
corvuspabelanger: yeah, i think that was the suggestion19:10
mordredpabelanger: yah - the idea is to pre-populate the inventory with the child_jobs19:10
corvusalways populate the inventory19:11
mordredbecause zuul will have already applied various rules to determine what should run - and we want to honor that too19:11
pabelangerokay, great. I think I have that step done, just writing unit test.19:12
*** yolanda__ has quit IRC19:12
*** yolanda__ has joined #zuul19:15
*** yolanda_ has quit IRC19:18
*** acozine1 has joined #zuul19:23
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add zuul.child_jobs in ansible inventory file  https://review.openstack.org/57818119:38
pabelangercorvus: mordred: ^is what I came up with for zuul.child_jobs. Now to work on zuul_return bits19:39
corvuspabelanger, mordred: nice.  do you think child_jobs should be just the first level of children, or all children?19:40
pabelangerfirst level would be fine for rdo, but believe getDependentJobsRecursively returns all? I am unsure about ansible, would defer to mordred19:42
mordredcorvus: I think either could be fine - but I was thinking just first level originally19:46
pabelangerokay, let me change19:48
*** hasharAway is now known as hashar19:50
*** sshnaidm has joined #zuul19:50
*** gouthamr has joined #zuul19:54
mordredpabelanger: and I was thinking that basically zuul would take the intersection of the lists - so it's not possible for a job to add child jobs - only to remove them (that's a follow up step - but just while I'm talking out loud)20:02
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Add zuul.child_jobs in ansible inventory file  https://review.openstack.org/57818120:04
pabelangermordred: yes, that's what I'm going to try and figure out now20:05
*** hashar has quit IRC20:10
*** hashar has joined #zuul20:11
corvusi think the github paging change could benefit from something like a betamax test if we ever get those going, but with what we have now, i think the code is covered about as well as it can be so i'll approve20:19
corvustobiash, clarkb, mordred: ^20:19
*** gouthamr has quit IRC20:19
tobiashcorvus: thanks20:20
corvusis /etc/localtime ever not present?20:20
corvus(on linux)20:20
corvusfungi, clarkb: ^ q re localtime20:22
clarkbI want to say systemd has a default behavior if it isnt there or maybe it is glibc20:22
*** gouthamr has joined #zuul20:22
fungiyeah, not sure honestly20:23
fungii can't say i've ever noticed it missing on a system outside bootstrapping/installation20:24
corvusokay, maybe we assume yes until someone complains :)20:24
corvuser, assume it's always there20:24
*** gouthamr_ has joined #zuul20:29
*** gouthamr has quit IRC20:29
*** gouthamr_ is now known as gouthamr20:29
*** acozine1 has quit IRC20:33
openstackgerritMerged openstack-infra/zuul master: Support paging when listing github installations  https://review.openstack.org/57807720:39
openstackgerritMerged openstack-infra/zuul master: Add /etc/localtime to bubblewrap default ro bind  https://review.openstack.org/57807220:48
openstackgerritMerged openstack-infra/zuul master: Improve test case test_unprotected_branches  https://review.openstack.org/57653620:51
openstackgerritMerged openstack-infra/zuul master: Move exclude unprotected branches check into tenant  https://review.openstack.org/57653720:54
openstackgerritMonty Taylor proposed openstack-infra/nodepool master: Consume Task and TaskManager from openstacksdk  https://review.openstack.org/41475920:56
corvusmnaser: in https://review.openstack.org/572588  why does enter cause the page refresh, but clicking the (X) in the box to clear it does not?20:56
corvusohhhh20:59
corvusif you type in the box and don't hit enter, it filters on the next auto refresh.  clicking the (X) must just be the opposite of that.  it clears the field, but still awaits the next refresh for the change to be visible20:59
corvus(i just happened to have clicked (X) right before a refresh and thought it was instantaneous)21:00
pabelangercorvus: mordred: I'm trying to see where we check zuul.child_jobs has been filters to remove a job, but believe I could do it in QueueItem.findJobsToRun(), does that make sense? Otherwise, happy to take a pointer on where21:00
corvuspabelanger: i think that's the right place21:00
pabelangerYay21:01
corvuspabelanger, mordred: i think we may have more trouble implementing mordred's vision of jobs not appearing than pabelanger's vision of jobs showing up as something like 'SKIPPED'21:02
clarkbhttps://review.openstack.org/#/c/578157/ shows my zuul-jobs change should be working (re mtu changes)21:02
corvuspabelanger, mordred: because the job graph is pretty static once it's created; nothing removes branches from it right now21:03
mordredcorvus: ah ... nod21:03
mordredwell - given the construct (job manipulating graph) I think it's not terrible if we show those as skipped21:04
mordredcorvus: re: 572588 - I believe we can make a bunch of things better and more immediately responsive21:04
corvuspabelanger, mordred: yeah, i think maybe the skipped approach is best.  surgery on the graph would be possible, but it'll be complex (especially since it needs to survive reconfigurations which can also alter the job graph)21:06
corvusi feel like skipped is pretty intuitive21:06
corvusmordred: re 588, yeah, i figured (mnaser said things would get better when we angularify that) i just wondered why adding was different from removing, but i see now it isn't, so it makes much more sense :)21:07
corvusmordred: i'm +2 on that and the main angular patch21:08
pabelangermordred: corvus: okay, I'll work up the skipped approach patch and see how that looks21:08
mordredcorvus: yay!21:08
corvuswe just need someone else to +3 those now :)  how hard could that be?21:08
mordredcorvus: tobiash said he could upgrade his vote to a +2 if needed21:08
corvuswe may need to take him up on that :)21:08
mordredcorvus: but yeah - the number of folks who are excited about reviewing a large javascript patch turn out to be ... small21:08
mordredclarkb: feel like +3ing two javascript patches?21:09
clarkbmordred: I can take a look as soon as I get these emails sent21:09
clarkblinks?21:09
mordredclarkb: https://review.openstack.org/#/c/551989/ and https://review.openstack.org/#/c/572588/21:09
mordredcorvus: I've lost the status etherpad ...21:09
corvusi think the intent is met though -- people who care and can poke at it have looked it over.  perhaps no one (or only one) understands it fully, but it seems like an improvement, doesn't seem to break things, and people seem okay iterating on smaller changes after it lands21:10
corvusmordred: /topic21:10
mordredhrm. now how do I see the entire topic ...21:10
corvusmordred: in your client, if you type '/topic' it doesn't show you the whole thing?21:11
mordredoh - I don't believe i've ever tried that21:11
mordredyes!21:11
mordredneat. I learned something today21:11
corvusw00t!21:11
corvusthough, also, you could buy more monitors until it fits.  displaying the entire topic is a legit business expense.21:12
*** yolanda_ has joined #zuul21:12
mordredcorvus: do I just gaff the extra monitors to the side of my laptop? that seems heavy21:13
corvusmordred: you have to balance them on both sides21:13
corvusgaff will hold21:14
*** yolanda__ has quit IRC21:14
clarkblenovo made a Wsomething thinkpad that had a pull out extra display iirc21:15
clarkbmordred: on that first one I am largely going to be reviewing for things not being obviously broken21:22
mordredclarkb: yes. this is all i think it is reasonable to do21:22
*** cmurphy_vacation is now known as cmurphy21:22
clarkbmordred: we added tslint but didn't remove .eslintrc?21:24
clarkbis that something we can cleanup later? or are we using both?21:25
*** gouthamr has quit IRC21:25
*** gouthamr has joined #zuul21:26
mordredclarkb: I *think* we might be using both - but I cna't remember - I'll poke at cleaning that up - but we can definitely do as a followup21:27
*** hashar has quit IRC21:45
clarkbmordred: so if I read this right angular is basically just mvc and then we farm out to jquery js to actual business logic21:47
mordredclarkb: yes. at least for now- the longer-term intent is to make the jquery in the status page go away21:48
mordredbut that's too much for one patch21:48
clarkbalso is there something that ties AppRoutingModule in https://review.openstack.org/#/c/551989/43/web/app-routing.module.ts to the NgModule above the export?21:48
clarkbis that just magic ts inference (or angular)21:48
mordredclarkb: https://review.openstack.org/#/c/551989/43/web/app.module.ts21:49
clarkbmordred: that adds approutingmodule to the NgModule there21:49
clarkbit just seems like the NgModule in the code I linked is dangling unused code?21:49
mordredand that's called from main.ts21:50
clarkbI'm sure it isn't because it is where the routes are defined sothere must be some implied connection21:50
mordredthat's a decorator21:50
clarkboh!21:50
mordreddecorating the declaration of AppRoutingModule21:50
mordredso _actually_ if you start at main.ts - you should be able to step through all the things one way or another from imports and direct references21:51
mordredthis makes is nicer I think for us - where we'd like to be able to trace through things- but it removed a bunch of magic that previous fans of angularjs liked21:52
clarkbya I mean it mostly made sense, it was just the specifics in how are these things tied together I was missing, I figured they were tied together21:52
clarkband decorator would explain it21:52
clarkbmordred: and you want me to +3? we are cool with tristanC's concerns (we can clean that up later I guess)21:53
*** myoung is now known as myoung|off21:56
mordredclarkb: yah - I think it'll be better to get the big thing in and get back to being able to make small patches21:56
mordredclarkb: tristanC is running with some local patches applied already anyway - so we will not be breaking him21:56
clarkbmordred: done22:02
mordredclarkb: thank you!22:07
*** yolanda__ has joined #zuul22:07
mordredit feels like that patch has been in work longer than just since march22:08
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Translate zuulStartStream into typescript  https://review.openstack.org/55861822:10
*** yolanda_ has quit IRC22:10
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Shift log streaming code into StreamComponent  https://review.openstack.org/55861922:10
clarkbcorvus: tristanC I'm a little confused by https://review.openstack.org/#/c/576016/2 shouldn't the old code have returned [] if include is not in conf which would have set project_include to current_include under the old code (same as new code)22:11
clarkboh is the problem that frozenSet([]) evaluates to a truthy value?22:12
openstackgerritMonty Taylor proposed openstack-infra/zuul master: WIP Make websocket streaming more event-driven  https://review.openstack.org/55864622:14
corvusclarkb: it's false.  i think the problem is that it needs to be distinguished from 'not set'22:15
corvusclarkb: old code was 'if user sets project include:[], ignore that and use project group include value'22:16
corvusclarkb: new code is 'use project include: if set (to any value including the empty list), otherwise use group include'22:17
clarkbgotcha22:17
clarkbthough it is set to current_include in either case?22:17
clarkbthat is what I'm tripping over if that evaluates to false it should be the same value in the end for both?22:18
clarkboh wait I get it now22:18
openstackgerritMerged openstack-infra/zuul master: configloader: skip merger:cat when no items are included  https://review.openstack.org/57601622:18
openstackgerritMerged openstack-infra/zuul master: Add a config_errors info to {tenant}/config-errors endpoint  https://review.openstack.org/55387322:18
openstackgerritMerged openstack-infra/zuul master: Refactor load sensors into drivers  https://review.openstack.org/54927522:18
clarkbthe difference is == [] vs is None22:18
clarkbbecause None was being mapped to [] which got current include, but now None is current include and [] is still []22:19
*** yolanda_ has joined #zuul22:21
*** yolanda__ has quit IRC22:24
*** threestrands has joined #zuul22:38
tristanCclarkb: mordred: i'll update the angular6 fixes that are needed for multi-tenant deployment.22:42
tristanCbeside the console log of routing event, it shouldn't affect zuul.openstack.org much22:42
*** rlandy has quit IRC22:49
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: fix status page flickering  https://review.openstack.org/57822622:50
tristanCoh actually this is affecting single tenant too ^ You can reproduce by clicking status, then job, then status then jobs repeatedely. Then un focus and focus again, you'll see a multiple status call happening at once.22:52
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: angular6 fix suggestion  https://review.openstack.org/57349422:55
openstackgerritMerged openstack-infra/zuul master: Upgrade from angularjs (v1) to angular (v6)  https://review.openstack.org/55198922:59
openstackgerritMerged openstack-infra/zuul master: Hide queue headers for empty queues when filtering  https://review.openstack.org/57258822:59
openstackgerritPaul Belanger proposed openstack-infra/zuul master: WIP: Support skip_child_jobs via zuul_return  https://review.openstack.org/57823023:35
pabelangerclarkb: corvus: mordred: ^first attempt to skip child jobs using zuul_return, there is still work to do to write a proper unit test, but I am not sure if I am on the right path. using zuul_return won't override the zuul.child_job ansible varaible, if I understand properly. So that is why I created skip_child_jobs.  I'll continue more on it tomorrow but want to get some code up tonight23:37
corvuspabelanger: the variables in zuul_return are independent of what's put in the inventory.  so it's fine to use the same name.23:39
corvus(i mean, if you zuul_return something, it gets passed to the child job, but *not* if it's something under the zuul hierarchy, so that's fine for this case)23:40
corvus(iow, should be fine to use zuul.child_jobs)23:40
pabelangerokay, thanks23:41
ianwtristanC: oh, is see what's going on, inventory_file isn't defined when ansible doesn't think you have an inventory23:58
ianwi wonder if it's more correct to ignore it, or copy in zuul's version.  i'll throw up a patch and the peanut gallery can decide :)23:59
tristanCianw: thanks!23:59

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