opendevreview | Ian Wienand proposed zuul/zuul-jobs master: promote-docker-image: some notes on manual replication https://review.opendev.org/c/zuul/zuul-jobs/+/872237 | 00:13 |
---|---|---|
opendevreview | Clark Boylan proposed opendev/system-config master: Switch Gerrit test Verified label function to NoOp https://review.opendev.org/c/opendev/system-config/+/872238 | 00:23 |
clarkb | I've done some digging into the gerrit source since my emails upstram didn't get any bites. I think that we may actually need to do the explicit NoOP | 00:23 |
clarkb | I'm about to put the meeting ageand together. Let me know if there is anything I should add/remove (I'm adding the git udpates and removing gitea 1.18, linaro cloud, and pruning backups). ianw let me know if I should keep linaro on there but I Think things are running ? | 00:27 |
ianw | yeah i think it's going ok. we might like to discuss how much we'd like to manage the underlying system | 00:28 |
clarkb | oh good idea. I'll keep it on the agenda then | 00:28 |
opendevreview | Ian Wienand proposed openstack/project-config master: Remove manila-tempest-dsvm-hdfs https://review.opendev.org/c/openstack/project-config/+/872239 | 00:34 |
opendevreview | Ian Wienand proposed openstack/project-config master: Remove manila-tempest-dsvm-hdfs https://review.opendev.org/c/openstack/project-config/+/872239 | 00:44 |
clarkb | ok agenda is updated. I'll give it a few minutes before sending out | 00:53 |
clarkb | and sent | 01:03 |
*** rlandy|bbl is now known as rlandy | 01:36 | |
*** rlandy is now known as rlandy|out | 01:39 | |
*** dasm is now known as dasm|off | 01:44 | |
*** yadnesh|away is now known as yadnesh | 04:41 | |
opendevreview | Ian Wienand proposed zuul/zuul-jobs master: build-docker-image: fix change prefix https://review.opendev.org/c/zuul/zuul-jobs/+/872258 | 06:20 |
*** yadnesh is now known as yadnesh|afk | 07:57 | |
*** jpena|off is now known as jpena | 08:02 | |
*** ysandeep__ is now known as ysandeep|lunch | 09:03 | |
opendevreview | Andreas Jaeger proposed zuul/zuul-jobs master: promote-docker-image: some notes on manual replication https://review.opendev.org/c/zuul/zuul-jobs/+/872237 | 09:04 |
opendevreview | Merged opendev/infra-manual master: General updates for the Test Environment chapter https://review.opendev.org/c/opendev/infra-manual/+/872201 | 09:11 |
*** yadnesh|afk is now known as yadnesh | 09:25 | |
*** ysandeep|lunch is now known as ysandeep | 10:50 | |
*** rlandy|out is now known as rlandy | 11:15 | |
opendevreview | Rodolfo Alonso proposed openstack/project-config master: Add github sqlalchemy/sqlalchemy to the project list https://review.opendev.org/c/openstack/project-config/+/872275 | 11:28 |
opendevreview | Rodolfo Alonso proposed openstack/project-config master: Add github sqlalchemy/sqlalchemy to the project list https://review.opendev.org/c/openstack/project-config/+/872275 | 11:28 |
*** dviroel|out is now known as dviroel|rover | 11:29 | |
*** ysandeep is now known as ysandeep|brb | 11:49 | |
*** tkajinam is now known as Guest3003 | 12:02 | |
*** ysandeep|brb is now known as ysandeep | 12:23 | |
opendevreview | Vishal Manchanda proposed openstack/project-config master: Step 1: End Project Gating, Retire xstatic-font-awesome https://review.opendev.org/c/openstack/project-config/+/871703 | 12:48 |
fungi | pip 23.0 is out today: https://pip.pypa.io/en/stable/news/#v23-0 | 13:19 |
rpittau | hello everyone! The ironic project has hit a little bump on the road, our CI is dependent from the virtualpdu project (now in x, but before was in openstack) which is unfortunately not very Python 3 friendly, and we can't move to jammy because of that. | 13:24 |
rpittau | We've prepared a couple of patches to fix that, and contacted the project cores, but we got no answer so far after a couple of weeks. | 13:24 |
rpittau | We're ready to fork or even adopt virtualpdu under the ironic umbrella and maintain it, just wanted to see what the procedure would be in case we go down that road, thanks! | 13:24 |
fungi | rpittau: if the current maintainers can't be reached for permission to take over maintenance, you'd need to fork it. If you wanted to fork into the openstack namespace as a deliverable of ironic, submit a project creation change like usual and make https://opendev.org/x/virtualpdu the upstream import url | 13:43 |
fungi | if you want to release it on pypi, you'll probably want a new name for it though, since pypi doesn't have namespacing | 13:43 |
rpittau | thanks fungi | 13:45 |
fungi | rpittau: if you can get permission to take it over, then ideally have one of them add you to the group(s) for it gerrit. you can optionally work with us to move it into the openstack namespace once you're a maintainer | 13:47 |
fungi | s/for it gerrit/for it in gerrit/ | 13:47 |
rpittau | fungi: that would probably be preferable, need to talk to the rest of the ironic cores | 13:47 |
fungi | avoiding forking would be preferable, but someone would need to be able to get in touch with the current maintainers for that | 13:48 |
rpittau | I'll give another try | 13:49 |
rpittau | the huge problem we have now is that we can't move all ofthe CI jobs to jammy, so we need to find a workaround quickly | 13:49 |
rpittau | JayF, dtantsur, TheJulia FYI ^^ | 13:56 |
fungi | how specifically is it breaking on jammy? maybe there's another short-term workaround | 13:59 |
dtantsur | fungi: jammy has no python 2, I assume | 14:01 |
dtantsur | as a short term workaround, we can prepare a container based on whatever ubuntu version it supports | 14:02 |
dtantsur | but ideally we shouldn't rely on a dead project | 14:02 |
fungi | oh, it was never made to work with python3? | 14:02 |
rpittau | focal is supported, the problem starts with jammy and python 3.10, I think | 14:02 |
fungi | wow | 14:02 |
rpittau | the higher version supported is python 3.5 | 14:02 |
rpittau | officially | 14:02 |
dtantsur | ahh, sorry. but yeah, the situation is similar. | 14:03 |
fungi | rpittau: dtantsur: not great as a long-term solution obviously, but maybe https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa can help temporarily? | 14:04 |
fungi | they oldest python they have for jammy is 3.7 but perhaps that's old enough | 14:05 |
rpittau | it might work, if that works with python 3.8 we can probably steal some more time | 14:07 |
fungi | packages from thereshould be installable alongside the default python provided in jammy, so you can invoke python3.7 or whatever directly to install virtualpdu (i assume you're running it as an application and interacting with it that way, not importing it into ironic code) | 14:08 |
rpittau | yep, correct | 14:09 |
fungi | mgagne: do you happen to be in touch with the (former?) inap people who worked on virtualpdu? looking through the virtualpdu-core group in gerrit i see a lot of internap addresses | 14:14 |
*** dasm|off is now known as dasm | 14:28 | |
*** ysandeep is now known as ysandeep|out | 14:33 | |
Clark[m] | I think jammy does have python2 | 14:36 |
Clark[m] | https://packages.ubuntu.com/jammy/python2 is your shorter term workaround | 14:37 |
fungi | ahh, yeah | 14:38 |
rpittau | Clark[m]: thanks, I'll keep that as the very last option, trying to make it work with python 3.8 now | 14:41 |
Clark[m] | Where is python 3.8 coming from? Chances are distro python 2.7 for a project that never really did python 3 is going to be your best bet | 14:42 |
rpittau | according to the setup.cfg virtualpdu should support up to python 3.4 | 14:43 |
rpittau | but it was tested with python 3.5 | 14:43 |
clarkb | right but ppa python 3.8 on jammy is going to be less reliable than installing python2 out of a local mirror. Also python2 on jammy isn't going anywhere but I'm not sure what that PPAs rule for python versions that eol is | 14:50 |
rpittau | errr this is really a mess.... it does not work with py 3.8 and 3.7 (just tried) and also we can't use python 2 cause libvirt-python needs python >= 3.5 :/ | 15:05 |
fungi | how was it working on focal? older libvirt-python? | 15:05 |
rpittau | yeah | 15:05 |
fungi | i guess you could cap libvirt-python in the virtualpdu python version | 15:06 |
rpittau | I'm thinking that | 15:06 |
fungi | i guess the pip version being used with python2 doesn't support the requires_python metadata | 15:07 |
fungi | or libvirt-python doesn't set it correctly | 15:08 |
*** dviroel|rover is now known as dviroel|rover|lunch | 15:08 | |
clarkb | jammy pip should do that | 15:08 |
clarkb | its the python3 pip installing to python2 I would expect | 15:08 |
fungi | depends on whether you invoke python2 -m pip or something | 15:08 |
clarkb | but ya looking at pypi they don't seem to set requires python | 15:08 |
fungi | i suppose we're lucky libvirt started publishing their python bindings to pypi at all | 15:09 |
clarkb | I think you need libvirt-python<6 | 15:09 |
rpittau | yep | 15:10 |
rpittau | doing it now | 15:10 |
rpittau | and of course libvirt bindings don't work | 15:11 |
rpittau | yep, it fails building libvirt-python | 15:14 |
clarkb | hrm I wonder if that older library isn't new enough to talk to jammy's libvirt then? | 15:14 |
fungi | oh, right, i think they need to ~match | 15:17 |
rpittau | yeah | 15:17 |
fungi | yeah, that's quite the mess | 15:17 |
rpittau | \o/ | 15:18 |
clarkb | I think the python lib needs to be >= to the libvirt install. Newer python lib is fine. Not that that helps in this case | 15:18 |
rpittau | forgot how strict libvirt is, but it makes sense | 15:19 |
fungi | so, yeah, python docker container is starting to sound like the easiest alternative to forking at this point | 15:19 |
rpittau | unless we find another solution I guess we go for a container as a temp workaround | 15:20 |
rpittau | but in the long term we really need to be able to fix virtualpdu for py3 | 15:20 |
fungi | you could "fork" it in your job by checking out the git repo, applying a patch/fetching a gerrit change to make it work with python3.10, and then install from that local path | 15:21 |
fungi | we do that as an ugly workaround for some of our services in opendev when we need to deploy fixes which haven't merged upstream due to unresponsive maintainers | 15:22 |
rpittau | I also thought about that, but it requires a lot of patching | 15:22 |
rpittau | I'd rather fork it entirely and be done with that | 15:22 |
rpittau | I'll try bumping the mail and see if cores reply | 15:23 |
clarkb | git am, or patch make it easy especially if you're rwriting the fixes anway | 15:23 |
clarkb | but ya its been useful for sorting out gerrit patches in particular before we push them upstream | 15:24 |
JayF | The patches already exist for py3 compatability, right? | 15:26 |
JayF | We just have nobody empowered to land them | 15:26 |
rpittau | JayF: not entirely | 15:26 |
JayF | ack | 15:27 |
rpittau | JayF: I was trying to get the entire project in shape, removing old project config and setting up correct CI jobs | 15:28 |
rpittau | it takes some effort | 15:28 |
JayF | yeah I'd imagine so | 15:28 |
JayF | my prefererence is, lets just say I'll be thinking of names lol | 15:28 |
rpittau | :D | 15:28 |
JayF | with the hope that the existing group will return an email | 15:29 |
rpittau | fungi, clarkb, in the meantime do you think could it be possible to move forward with the patches impacting the project config? https://review.opendev.org/c/openstack/project-config/+/869979 and https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/870519 | 15:47 |
clarkb | I think that is ok. I didn't approve in case fungi had an objection | 15:48 |
rpittau | great, thanks! | 15:48 |
fungi | yeah, i approved it | 15:52 |
fungi | i'll recheck and approve the second once the first applies | 15:52 |
rpittau | thanks both :) | 15:54 |
fungi | oh, somehow we've broken the manila-tempest-dsvm-hdfs definition somewhere | 15:54 |
fungi | that's preventing us from merging further job configuration changes in project-config | 15:55 |
clarkb | fungi: I think I saw ianw pushing changes to fix that. | 15:55 |
clarkb | I didn't realize that was why/me looks for them | 15:55 |
clarkb | https://review.opendev.org/c/openstack/project-config/+/872239 | 15:55 |
clarkb | I've approved ^ which should allow the other change to land once it merges | 15:57 |
fungi | double-approved | 15:57 |
fungi | a few other project-config changes seem to have hit the same error | 15:57 |
opendevreview | Merged openstack/project-config master: Remove manila-tempest-dsvm-hdfs https://review.opendev.org/c/openstack/project-config/+/872239 | 16:03 |
*** dviroel|rover|lunch is now known as dviroel|rover | 16:14 | |
fungi | rpittau: one of the virtualpdu core reviewers just left a +1 on 869979 | 16:23 |
rpittau | w00t | 16:23 |
rpittau | awesome | 16:24 |
*** jpena is now known as jpena|off | 16:25 | |
rpittau | mmm he approved also the change in the virtualpdu project itself, although it's not complete, hopefully we'll have a quicker turnaround next iteration | 16:25 |
opendevreview | Merged openstack/project-config master: Reduce virtualpdu tests https://review.opendev.org/c/openstack/project-config/+/869979 | 16:29 |
*** yadnesh is now known as yadnesh|away | 16:35 | |
rpittau | fungi, clarkb, JayF, sorry to bother you again! We just got an answer from 2 cores of virtualpdu and one of them gave us his blessing to take over virtualpdu, how do we formalize this? | 16:39 |
fungi | rpittau: if they can go to https://review.opendev.org/admin/groups/q/filter:virtualpdu while logged in and add one of you as members to the two groups listed there, that's the first step | 16:41 |
rpittau | fungi: cool, thanks | 16:41 |
clarkb | ya the best thing is if we don't have to intervene at all and our users can do a graceful handover | 16:41 |
fungi | once you have control of group membership, if you want to move it officially into openstack then you'll want a governance change and project config changes to rename the repository, and add an item to our weekly meeting agenda here so we can discuss scheduling a rename maintenance window: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames | 16:42 |
rpittau | ok, I guess we'll have to discuss about that with the rest of the ironic community | 16:43 |
fungi | yep, one step at a time. but at least now you'll have access to fix up your dependency even if it's not technically in openstack | 16:45 |
fungi | and you have a path to adopting it officially in openstack if the team decides that's the way you want to go | 16:45 |
rpittau | that's the most important thing right now :) | 16:45 |
fungi | without needing to fork | 16:46 |
JayF | rpittau: I'd say we basically decided as a community to take it over if possible | 16:54 |
JayF | rpittau: so you have my blessing, at least, to move forward. If you want me to poke at any of the project-config or governance changes lmk | 16:54 |
opendevreview | Jeremy Stanley proposed opendev/system-config master: Separate mailman default hostname https://review.opendev.org/c/opendev/system-config/+/867986 | 16:56 |
opendevreview | Jeremy Stanley proposed opendev/system-config master: Use magic domain guessing in Mailman 3 https://review.opendev.org/c/opendev/system-config/+/867987 | 16:56 |
opendevreview | Jeremy Stanley proposed opendev/system-config master: DNM force mm3 failure to hold the node https://review.opendev.org/c/opendev/system-config/+/855292 | 16:56 |
*** marios is now known as marios|out | 17:01 | |
opendevreview | Jeremy Stanley proposed opendev/system-config master: DNM: Unhide task output https://review.opendev.org/c/opendev/system-config/+/872338 | 17:31 |
fungi | clarkb: trying to add a container restart into the mm3 deployment process, what's the best way to pause task execution until it's up? just add another task polling the api? | 18:38 |
clarkb | fungi: "yes" there are some tasks that already do that in the mm3 role after the initial deployment. I've seen that the api can be up before django is full initialized. THough after the initial install I uspect that checking the api endpoint is probably sufficient | 18:40 |
fungi | thanks, i'll see if that's sufficient | 18:43 |
opendevreview | Jeremy Stanley proposed opendev/system-config master: Use magic domain guessing in Mailman 3 https://review.opendev.org/c/opendev/system-config/+/867987 | 18:43 |
clarkb | I think the issue is that the api doesn't rely on django being there at all | 18:48 |
fungi | clarkb: also as far as adding sites in django i was pointed to https://docs.djangoproject.com/en/4.1/ref/contrib/sites/ | 18:49 |
clarkb | skimming that there doesn't seem to be an easy mode create a site. But that at least documents the expectations | 18:50 |
clarkb | oh apparently we could manage our own db migrations though? | 18:51 |
clarkb | that seems wrong (migrations should manage schemas and necessary data transformations not the data itself) | 18:51 |
fungi | i think https://docs.djangoproject.com/en/4.1/ref/contrib/sites/#enabling-the-sites-framework explains how to create sites? it's a bit opaque though | 18:53 |
clarkb | ya it basically says create a custom db migration to inject your data | 18:53 |
clarkb | which to me is the absolute wrong way to use db migrations | 18:54 |
fungi | hmm, so db migrations as a way to run inserts? | 18:54 |
clarkb | yup at least that is how I'm reading that section | 18:54 |
fungi | reading some additional articles about django, i think i see why | 18:56 |
fungi | each django "site" has a dedicated set of database tables, and the migrations are being used to create the tables | 18:57 |
fungi | looks like django-admin makemigrations has a --scriptable option which might be handy | 19:01 |
*** dasm is now known as dasm|off | 19:33 | |
ianw | clarkb: i'm not sure i realised https://hub.docker.com/_/openjdk was deprecated? | 19:39 |
clarkb | ianw: its like half deprecated | 19:39 |
clarkb | which is why I think it wasn't really clear | 19:39 |
clarkb | but ya the bits we are using need to not be used anymore | 19:40 |
opendevreview | Jeremy Stanley proposed opendev/system-config master: DNM force mm3 failure to hold the node https://review.opendev.org/c/opendev/system-config/+/855292 | 19:50 |
opendevreview | Jeremy Stanley proposed opendev/system-config master: Feature our cloud donors on opendev.org https://review.opendev.org/c/opendev/system-config/+/869091 | 19:55 |
*** dviroel|rover is now known as dviroel|uot | 21:00 | |
fungi | ianw: clarkb: looks like the debian container images may have updated git now, based on the failure i'm seeing for system-config-build-image-gitea here: https://zuul.opendev.org/t/openstack/build/6f39eb72a9464fa790c43428589201f4 | 21:25 |
fungi | "The following packages will be DOWNGRADED: git git-man" | 21:25 |
fungi | are we clear to approve 872209 now? | 21:26 |
clarkb | fungi: I think that error is what zuul hit too and the leaf image (eg zuul) is installing git to he patched version and then apt is angry with our local package. However, the base image we pull from hasn't updated yet at last check | 21:27 |
clarkb | fungi: and ya I think landing 872209 is a good idea as is https://review.opendev.org/c/opendev/system-config/+/872212 | 21:27 |
fungi | done and done | 21:28 |
fungi | taking a quick break to cook dinner, but can check in on the deployment afterward | 21:28 |
clarkb | I'm going to need to do a school run in not too long. THe next thing on my todo list was picking up zuul sqla debugging again. But not sure i have time to page all that in before I need to pop out | 21:33 |
opendevreview | Ade Lee proposed openstack/project-config master: Add base openstack FIPS job https://review.opendev.org/c/openstack/project-config/+/872222 | 22:20 |
opendevreview | Ade Lee proposed zuul/zuul-jobs master: Add ubuntu to enable-fips role https://review.opendev.org/c/zuul/zuul-jobs/+/866881 | 22:24 |
opendevreview | Merged opendev/system-config master: Revert "Update git in gitea images" https://review.opendev.org/c/opendev/system-config/+/872209 | 22:48 |
opendevreview | Merged opendev/system-config master: Flip Gerrit image to install distro git https://review.opendev.org/c/opendev/system-config/+/872212 | 22:55 |
fungi | gitea seems to still be working | 23:08 |
*** rlandy is now known as rlandy|out | 23:10 | |
clarkb | and fetching the image and checking dpkg shows what I expect | 23:11 |
ianw | clarkb: just sent a response to the gerrit label function default message, after looking a bit ... | 23:24 |
ianw | it feels perhaps not exactly a bug, but certainly very difficult to use | 23:25 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!