Friday, 2024-09-27

*** elodilles_pto is now known as elodilles07:00
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Move SELinux context to variable  https://review.opendev.org/c/openstack/ci-log-processing/+/93068007:36
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Move SELinux context to variable  https://review.opendev.org/c/openstack/ci-log-processing/+/93068009:26
opendevreviewMerged openstack/ci-log-processing master: Move SELinux context to variable  https://review.opendev.org/c/openstack/ci-log-processing/+/93068010:17
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Do not create download directory with recurse  https://review.opendev.org/c/openstack/ci-log-processing/+/93069311:19
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Do not create download directory with recurse  https://review.opendev.org/c/openstack/ci-log-processing/+/93069311:33
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Do not create download dir with recurse; check if dir already exists  https://review.opendev.org/c/openstack/ci-log-processing/+/93069311:34
opendevreviewdaniel.pawlik proposed openstack/ci-log-processing master: Do not create download dir with recurse; check if dir already exists  https://review.opendev.org/c/openstack/ci-log-processing/+/93069312:05
opendevreviewMerged openstack/ci-log-processing master: Do not create download dir with recurse; check if dir already exists  https://review.opendev.org/c/openstack/ci-log-processing/+/93069312:32
opendevreviewJeremy Stanley proposed openstack/project-config master: Temporarily remove release docs semaphores  https://review.opendev.org/c/openstack/project-config/+/93070914:27
opendevreviewJeremy Stanley proposed openstack/project-config master: Revert "Temporarily remove release docs semaphores"  https://review.opendev.org/c/openstack/project-config/+/93071014:27
fricklergmann: https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926153 should be good to go now?15:37
clarkbfollowing up on https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/930590 netifaces and yappi were identified as two problematic packages for arm since they don't have wheels for arm.16:01
clarkbyappi I think is solvable workin with upstream to update their github actions to use the new ubuntu arm github runners16:01
clarkbnetifaces however is no longer maintained and hasn't been for years. Do we know what if any plans there are for dealing with unmaintained netifaces in openstack?16:01
fungii thought there had been work done to remove it16:06
fungimy isp is trying to route all my packets through the eye of a hurricane right now though (quite literally), so my network connectivity for investigating that isn't the greatest at this point in time16:07
fungimosh does surprisingly well with 50% packet loss, but the rest of the protocols i rely on are less useful right now16:08
fungihound (codesearch) is surprisingly terrible in console-based browsers16:11
fungigitea's search feature does work under elinks, and i'm seeing quite a few netifaces imports16:15
fungithough gitea's "fuzzy" searching has gotten more fuzzy than just case insensitivity now, it matched to a comment about "iscsi netspaces"16:18
fungitkajinam brought the topic to the openstack-discuss ml in april of last year16:23
fungiunfortunately, hyperkitty's thread view also doesn't work well in console-based browsers16:24
tkajinamlooks like swift added their own implementation to replace netifaces... probably we can borrow that and add something to oslo.utils16:29
tkajinamhttps://review.opendev.org/c/openstack/swift/+/87322216:29
fungithough it did allow me to find https://bugs.launchpad.net/neutron/+bug/2015844 with a reference to https://review.opendev.org/c/openstack/neutron/+/88098016:29
tkajinamyeah neutron used netifaces only in windows os which was deprecated and removed16:30
tkajinambut there are still a few projects, including netifaces, for other purposes16:30
fungithanks tkajinam! so yes, it looks like there's some momentum to stop depending on netifaces, but it's moving slowly16:30
tkajinamsorry I meant "including oslo.utils"16:31
tkajinamyeah16:31
tkajinamsome projects reacted to that mail but the other did not16:31
clarkbtkajinam: ok thats a neat idea. Then the next thing is making that work with arm well but one step at a time16:32
fungioslo.utils.netutils seems to use it for netifaces.gateways()16:32
tkajinamyup16:33
tkajinamI'm not following the whole thread but is it blocking something ? (probably py 3.13 support ?)16:33
clarkbin the meantime that takes us back to the question of whether or not we need the arm64 wheel mirrors. I wonder if we address the others like yappi if we can accept some costs for packages like netifaces until it is removed16:33
fungitkajinam: lack of aarch64 wheels16:34
tkajinamok16:34
clarkbtkajinam: mnaser has requested we build an ubuntu noble python3.12 wheel cache. When I spun up the ubuntu noble test node stuff I intentionally avoided adding a wheel cache because many things do build arm wheels now16:34
clarkband more generally have wheels published as the python package ecosystem has imrpvoed over time so I was hoping we wouldn't need that extra infrastructure16:34
clarkbmy motivation there is that we have to clean it up later16:34
clarkbhttps://mirror.dfw.rax.opendev.org/wheel/ which isn't happening as you can see a number of old distros we don't support still hanging around16:35
clarkbbut also that wheel cache/mirror has masked real packaging problems in the past like when upsteram pulls packages but we still have wheels for them16:35
clarkbthen things only work in CI and not on your laptop which I really would like to avoid16:35
clarkb(because it is another thing that ultimately opendev is asked to debug when it occurs)16:35
tkajinamyeah that sounds fair16:36
clarkbif we think we can address netifaces quickly in the new cycle then maybe we can still avoid building the wheel cache? since python3.12 isn't really a major issue for the ucrrent release?16:36
clarkbmnaser: ^ thoughts on that? I don't know how big of an impact it currenlty has for you. Is it just slowness or is it too slow to the point of not being workable16:37
clarkbI think we are close to being able to do this without the wheel cache and the start of a cycle seems like a good time to push against the issues and address them. But at the same time I don't want to act like a barrier as we do have a known fix so trying to balance being able to incentivize improvements against just making it work16:38
tkajinamWe anyway have to get rid of netifaces at some point because it's abandoned... I'll take a look next week to see how huge effort it may be16:38
clarkbtkajinam: thanks!16:38
tkajinammy small concern here is that it is used by multiple charm-* repositories and I'm unsure if I can cover these all16:38
mnaserclarkb: the thing is at the moment at 1 hour timeout I can’t build a Nova/neutron image :(16:39
clarkbmnaser: maybe lets do a quick test with a 3 hour timeout (the max) and see if we can do it in 1.25 hours vs in 3 or not at all?16:39
mnaserAlright I can try that. I was thinking of investing time to figure out how to make Zuul use buildx across two nodes16:40
clarkbpart of my concern here is that dep has been unmaintained for 3 years and we're talking about removing it now because the wheel cache doesn't exist. If we just papered over that by buildign the wheels it could be another three years before openstack moved on addressing the dep issue16:40
clarkbso I think spending at least a little time identifying these problems and determining if there are reasonable solutions is good for overall health16:41
mnaserBoot an amd64 and arm64 together for the same job, add arm64 as a remote buildx builder and then go through our normal flow :P16:41
gmannfrickler: yes, this is good to go, I removd -W https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92615316:41
mnaserclarkb: I mean, for me I’m a little too late to this, I could look into yanking it but I doubt I could get that backported at all :)16:41
clarkbthat would be cool. I think one of the issues is that currently zuul will try to run all of the support stuff in a single provider which may require zuul itself to chagne not just the jobs16:41
fungimainly because our providers are all single-arch, and also i think there are some inbuilt assumptions in nodepool that would make supporting a multu-architecture provider challenging too16:45
clarkbI think multiarchitecture provider would work if we can select arch by flavor16:46
clarkbif there is a different mechanism to detect arch we would need some chagnes to nodepool to select and boot them properly16:46
fungijust trying to think through how we'd do the image uploads, but i guess those are separate labels anyway so would "just work"?16:48
clarkbfungi: yes and in fact we have to configure each of the builders with all of the images too iirc. We just don't upload arm to x86 and vice versa16:48
clarkbotherwise the builders will try to clean up images they don't know about16:48
fungigood point16:48
clarkbwe don't upload or build them on the wrong platform16:48
fungiso really, if we did have providers with both x86_64 and aarch64 flavors, we could probably make it work with no need to make changes in software16:49
clarkbyup16:49
fungiand then the blocker is really just the lack of any such provider16:50
opendevreviewMerged openstack/openstack-zuul-jobs master: Prepare the job template for 2025.1 testing runtime  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92615317:04
opendevreviewJeremy Stanley proposed openstack/ptgbot master: Un-pin irc library  https://review.opendev.org/c/openstack/ptgbot/+/93078121:06

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