Monday, 2025-04-21

@jim:acmegating.comzuul-maint: how does this look for a release?  commit 2d94f706474acfa867f3ebc002a107860bc7147d (HEAD -> master, tag: 12.0.0, origin/master, gerrit/master)15:33
@jim:acmegating.comopendev is running that commit.  i think the notes in the upgrade section warrant the major version bump https://zuul-ci.org/docs/zuul/latest/releasenotes.html15:33
@clarkb:matrix.orgcorvus: I'll take a look once today's gerrit server swap is done15:35
@fungicide:matrix.orgthat seems to correspond to the current master branch state, 131 changes since 11.3.015:35
@fungicide:matrix.orgi agree the upgrade notes justify a 12.0.015:36
@fungicide:matrix.orglgtm!15:37
@jim:acmegating.comthx.  no rush.  :)15:38
@clarkb:matrix.orgcorvus: the hash and version both lgtm. Particularly since web status url is removed that is a potentially breaking change so 12.0.0 is a good idea17:07
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed on behalf of Joseph Kostreva: [zuul/zuul] 933138: Add zuul regex support to project definitions https://review.opendev.org/c/zuul/zuul/+/93313818:32
@clarkb:matrix.orgcorvus: I guess in the unrelated refactor that ^ missed a location where we had to force to a regex?18:53
@clarkb:matrix.orgor rather upadted things in such a way that this change's last update missed the type coercion18:54
@jim:acmegating.comClark: i think that was just an unavoidable conflict; i don't think anything was missed (unless i'm missing what you're looking at).  i think the latest ps is equivalent to the previous, but accounting for things being rearranged after the config object reuse stack19:02
@clarkb:matrix.orgack the diff doesn't show it super cleanly. But the more I look at it the less I'm concerned/confused19:06
@clarkb:matrix.orgits basically make sure we force the regex into the regex type19:06
@jim:acmegating.comyep19:33
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 941171: Ignore file matches on changes to include-vars and playbooks https://review.opendev.org/c/zuul/zuul/+/94117119:43
@jim:acmegating.comClark: the switch to using niz for zuul has uncovered a difference... in nodepool, the openstack driver sets private_ipv4 to public_ipv4 if there is no private_ipv4.  in niz, i passed through the values from the underlying driver without change.  the zuul tox-remote job notices this because it assumes private_ipv4 is always set.  do you think we should continue to take this opportunity to clean up the api and leave zuul as-is and fix the job, or should we make it backwards-compatible with nodepool?20:27
actually, i think i just came up with an obvious answer to that: how about we make the zuul.nodepool job variables backwards compatible, but add new zuul.node variables that change the api?
@jim:acmegating.com * Clark: the switch to using niz for zuul has uncovered a difference... in nodepool, the openstack driver sets private\_ipv4 to public\_ipv4 if there is no private\_ipv4.  in niz, i passed through the values from the underlying driver without change.  the zuul tox-remote job notices this because it assumes private\_ipv4 is always set.  do you think we should continue to take this opportunity to clean up the api and leave zuul as-is and fix the job, or should we make it backwards-compatible with nodepool?20:29
actually, i think i just came up with an obvious answer to that: how about we make the nodepool job variables backwards compatible, but add new node variables that change the api?
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 947768: Use private or public ip in nox-remote job https://review.opendev.org/c/zuul/zuul/+/94776820:31
@jim:acmegating.comthat's a quick fix for the job20:31
@clarkb:matrix.orgcorvus: I think the logic behind the nodepool behavior was to prefer private addresses if set because NAT often introduces problems and if you haev a public ip you may be traversing NAT. That said we can encode that same logic in the jobs too. But then you have to reteach everyone to avoid NAT...20:34
@clarkb:matrix.orgso basically by always ensuring private_ip is set we can easily tell people to use the private ip and not worry about that logic in different jobs.20:34
@jim:acmegating.commy problem with that is that nodepool is lying about what openstack returns; i don't think zuul should be in that business20:35
@jim:acmegating.comthere is the interface ip; that's the opposite right?  prefer public if it exists?20:36
@clarkb:matrix.orgya its a tradeoff and the tradeoff may work out differently for different groups20:36
@jim:acmegating.commaybe there should be a 6th ip address: the complement of interface-ip20:36
@clarkb:matrix.orgwithin openstack the lie was helpful particularly with setting up our own overlay networks for multinode testing of things like neutron. But I could see some deployments treating them as distinct20:36
@clarkb:matrix.orgyes interface ip is how to reach the node aiui20:37
@jim:acmegating.comi'd be fine adding the complement of interface ip... just need a name for it :)20:38
@clarkb:matrix.orgthe suggestion to have nodepool vars that are backward compatible then niz vars that aren't and I guess probably also deprecate the nodepool vars at some point makes sense to me20:38
@clarkb:matrix.orgoh that is an interesting idea too20:38
@clarkb:matrix.orginternal_ip ?20:38
@clarkb:matrix.orgor local_ip maybe20:38
@jim:acmegating.comwfm -- minor concern that it may be too misleading if it actually ends up being a public ip20:39
@clarkb:matrix.orgyup probably worth brainstorming a bit better if we can express what it is more accurately20:39
@jim:acmegating.comi think local is maybe slightly better than internal -- it's a little bit vague and doesn't scream "this is definitely rfc1918" at me :)  i think i'd have to look up the docs for it, which is no bad thing.  :)20:40
@clarkb:matrix.orgas a counter example we semi recently had opendev users complaining that their builds were failing and they didn't udnerstand why. Well turns out they assumed ipv6 was available in every cloud and used the ipv6 vars in their jobs. In that case we told them they have to check if ipv6 is available first20:43
@clarkb:matrix.orgso maybe being explicit and pushing people to understand the environment a bit better is a good thing?20:44
@jim:acmegating.comyeah, i do think that's best.  that's why i'd strongly push for having the actual public/private v4/v6 vars be their real values.  i'm more ambivalent about having helper values like interface_ip and local_ip.20:45
@clarkb:matrix.orgya I'd be fine with a secondary var that attempts to interpret things that people can switch to and make the explicit values consistent20:46
@jim:acmegating.com12.0.0 tagged, and release announcement sent21:10
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul-jobs] 947769: Add win_zuul_console to start-zuul-console https://review.opendev.org/c/zuul/zuul-jobs/+/94776921:27
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 947770: Adjust niz private_ipv4 behavior to match Nodepool https://review.opendev.org/c/zuul/zuul/+/94777021:39
@jim:acmegating.comClark: i'm sure that will fail tests, but it's on the punch list now.21:40
@clarkb:matrix.orgcool I left a couple of questjons on the win_zuul_console change21:41
-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 947768: Use private or public ip in nox-remote job https://review.opendev.org/c/zuul/zuul/+/94776822:31

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!