| opendevreview | OpenStack Proposal Bot proposed openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/962557 | 02:24 |
|---|---|---|
| opendevreview | Tony Breeds proposed opendev/system-config master: Update ansible-devel job to run on a newer bridge https://review.opendev.org/c/opendev/system-config/+/930538 | 02:49 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Update pip3 role to work on Ubuntu Noble https://review.opendev.org/c/opendev/system-config/+/934937 | 02:49 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Add ara and tzdata as installed requirements for the ansible-devel job https://review.opendev.org/c/opendev/system-config/+/934917 | 02:49 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Install ARA master in the ansible-devel job https://review.opendev.org/c/opendev/system-config/+/924012 | 02:49 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Add some debugging commands to the post job https://review.opendev.org/c/opendev/system-config/+/925667 | 02:49 |
| tonyb | apart from wiki.openstack.org, do we have any servers that we manage that are not listed in system-config:inventory/base/hosts.yaml ? | 06:36 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Update ansible-testing to run on the next version of bridge https://review.opendev.org/c/opendev/system-config/+/930538 | 07:29 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Update pip3 role to work on Ubuntu Noble https://review.opendev.org/c/opendev/system-config/+/934937 | 07:29 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Add ara and tzdata as installed requirements for the ansible-devel job https://review.opendev.org/c/opendev/system-config/+/934917 | 07:29 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Install ARA master in the ansible-devel job https://review.opendev.org/c/opendev/system-config/+/924012 | 07:29 |
| opendevreview | Tony Breeds proposed opendev/system-config master: Add some debugging commands to the post job https://review.opendev.org/c/opendev/system-config/+/925667 | 07:29 |
| fungi | tonyb: not to my knowledge, no. the only ones i could think might be missing are listed there after all, so just wiki i think | 11:13 |
| clarkb | I guess its worth noting we got through the PrePTG agenda yesterday and are not using the 1500-1700 block of time today | 15:10 |
| clarkb | in case anyone ends up looking for us on meetpad | 15:10 |
| clarkb | github is having issues this morning if anyone runs into problems that may be why | 15:49 |
| fungi | out to lunch, bbiab | 16:33 |
| clarkb | corvus: I've just cleaned up the old nodepool images in vexxhost ca-ymq-1. Looking at sjc1 it doesn't appear we ever configured it to boot nodes | 16:51 |
| clarkb | (and as a consequence has no images either) | 16:51 |
| corvus | sounds about right -- or at least, was so far in the past nodepool cleaned up our early attempts | 16:52 |
| clarkb | do we recall if that was inetntional? THere are nodepool iamges that can be cleaned up but I didn't want to do that until I have a better understanding of the current sitaution there | 16:52 |
| clarkb | I've dug up the old nodepool config and max servers as 0 in sjc1 so that explains why zuul launcher isn't booting there | 16:53 |
| clarkb | corvus: do you think I should go ahead and clean up the nodepool images anyway? I guess there isn't any reason to keep them | 16:53 |
| corvus | oh i thought you were saying there were no images in sjc1 because we never used it | 17:02 |
| corvus | but you're saying there are images despite us never using it | 17:03 |
| corvus | anyway, i think you can delete the old nodepool images from sjc1 | 17:03 |
| corvus | i don't recall why we stopped using it with nodepool a long time ago | 17:03 |
| corvus | clarkb: https://review.opendev.org/731508 | 17:06 |
| clarkb | corvus: ya sorry there are no nodes but there are images | 17:26 |
| clarkb | I will proceed with cleaning up those images now | 17:26 |
| clarkb | vexxhost images are cleaned up for the most part. There is one image in sjc1 that I cannot delete and i think there were four in ca-ymq-1 | 17:41 |
| clarkb | that means rax classic is the last region needing cleanup. I suspect this one will be the most problematic (due to its continuous use for over a decade) and as a result will defer that for now | 17:45 |
| fungi | okay back | 18:00 |
| fungi | yeah, i think we were asked to use ca-ymq-1 for nodepool nodes and not sjc1 | 18:01 |
| fungi | though it was okay to put control plane hosting in sjc1 | 18:01 |
| clarkb | yup that is/was the situation | 18:02 |
| clarkb | but nodepool was still uploading images (zuul-launcher is not) | 18:02 |
| fungi | right, so i agree it should be safe to blow all those away | 18:10 |
| clarkb | I've got a school thing in about half an hour and I'm going to use that as motiviation to get out on the bike. I'll be back in a bit | 19:56 |
| fungi | have fun! | 19:56 |
| clayg | zigo: yooo!! I'm confused! (as usual) Missing sub-modules when building w/ setuptools · Issue #1071 · eventlet/eventlet https://github.com/eventlet/eventlet/issues/1071 would love it if you could set me straight brother! 🫶 | 20:49 |
| clarkb | clayg: I don't know any of the answers, but `python setup.py $command` is deprecated and going away. You should probably be using the python build command: https://pypi.org/project/build/ instead | 22:23 |
| clarkb | regardless of the pyproject.toml contents i would stop using any setup.py commands as step 0 in debugging if they don't produce the expected results any longer | 22:24 |
| fungi | though it's possible that running `pyproject-build` instead of `setup.py sdist` is still going to have the observed problem with the packaged modules not getting included due to overriding setuptools module search routine | 22:27 |
| clarkb | right I don't know if this will fix the problem, more of ensuring the foundation is in place and correct before doing additional debugging | 22:28 |
| fungi | https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html indicates that packages is for explicitly listing all the ones that should be included, and doesn't indicate it's recursive so probably what clayg has proposed is a viable solution | 22:31 |
| fungi | however, it looks like [tool.setuptools.packages.find] can be used to fine-tune the discovery mechanism rather than overriding it completely | 22:32 |
| fungi | it also mentions py-modules but doesn't really say how it's used, making me suspect it's deprecated/discouraged | 22:40 |
| fungi | even though it's not called out as being discouraged or obsolete like some other settins listed there | 22:40 |
| clarkb | fungi: note that it looks like setuptools is no longer even used anymore? | 22:41 |
| clarkb | I guess for me what I would so is stop using python setup.py sdist and/or setuptools entirely and let build make a hatch built tool | 22:42 |
| fungi | ah, yeah it does look like hatch/hatchling is what eventlet is using now | 22:42 |
| clarkb | fi you're backporting fixes you don't need to backport the entire build system just the fixed code | 22:43 |
| fungi | so running pyproject-build probably will entirely bypass setuptools | 22:43 |
| clarkb | and in that case I would expect setuptools to keep working as is | 22:43 |
| fungi | so yes, i do think your suggestion (not invoking setuptools, using a pep 517 compliant "build frontend") is the actual solution | 22:46 |
| fungi | oh, though clayg points that out in his issue, so obviously not a viable solution in his case since he wants to continue using setuptools instead | 22:49 |
| fungi | the equivalent version handling would be to add the setuptools-scm plugin | 22:49 |
| fungi | but really it needs a different pyproject.toml to support setuptools instead of hatch | 22:50 |
| clarkb | right I think my confusion is why you need to use new pyproject.toml with new security patches | 22:51 |
| clarkb | if you just want to update setuptools to latest then I would use the new build system. If you just want security patches I would expect those to backport onto the old setuptools based system | 22:51 |
| fungi | it looks to me like the current debian packages aren't relying on setuptools either? https://setuptools.pypa.io/en/latest/userguide/miscellaneous.html | 22:52 |
| fungi | er, wrong paste | 22:52 |
| fungi | https://salsa.debian.org/openstack-team/third-party/python-eventlet/-/blob/debian/flamingo/debian/rules?ref_type=heads#L13 | 22:52 |
| fungi | --buildsystem=pybuild | 22:52 |
| clarkb | so its possible the work zigo did was a dead end and never worked as expected | 23:02 |
| clarkb | ? | 23:02 |
| fungi | or was later superseded | 23:02 |
| fungi | anyway, i commented on the issue with some links | 23:02 |
| clarkb | I just responded to the openstack discuss list with some quick details on how we stuff many keys into one nova key object and that makes thinsg magically work | 23:05 |
| clarkb | pretty sure that when ianw first generated an ed25519 key nova wouldn't accept it as the first key but was happy with it later in the list | 23:05 |
| fungi | yeah, it's sort of an abuse of the feature, but seems to be a still-viable workaround | 23:05 |
| clarkb | well I would argue at this point if the api is not capable of recognizing valid keys otherwise then its definitely grown into a proper feature itself | 23:06 |
| fungi | accidental feature | 23:06 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!