| jrosser | morning | 07:36 |
|---|---|---|
| noonedeadpunk | o/ | 07:41 |
| kleini | good morning. Is openstack.osa.db_setup documented somewhere? As it seems to be a role, is it useful to utilize include_role like in the os_* roles? | 07:48 |
| jrosser | i'm not sure i quite follow - are you wanting to use that role somewhere outside an osa service role? | 07:50 |
| jrosser | currently its a role in the openstack-ansible-plugins collection to factor out code that would otherwise be the same in all the service roles | 07:51 |
| kleini | I am working on the openstack-ansible-ops/grafana deployment and noonedeadpunk mentioned to use db_setup there instead of mysql_db und mysql_user module | 07:52 |
| jrosser | ah ok | 07:52 |
| kleini | grafana/grafana collection just needs a release: https://github.com/grafana/grafana-ansible-collection/pull/365 | 07:54 |
| jrosser | well, its not really documented at all as its an internal role for OSA | 07:54 |
| noonedeadpunk | I'd take example from smth like glance I guessL: https://opendev.org/openstack/openstack-ansible-os_glance/src/branch/master/tasks/main.yml#L46-L66 | 07:54 |
| jrosser | the best thing to do is look how it is used in the other os_ roles | 07:54 |
| jrosser | but it really is simple, just a wrapper around community.mysql.mysql_db and community.mysql.mysql_user | 07:55 |
| kleini | okay, let's try and we will see | 07:55 |
| opendevreview | Merged openstack/openstack-ansible-plugins master: Update collection version for 2025.2 https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/950176 | 09:50 |
| kleini | where do I get a usable ansible_python_interpreter from? I see them defined in openstack-ansible/playbooks/defaults/source_install.yml. Those variables don't seem to be available within openstack-ansible-ops. | 09:54 |
| noonedeadpunk | I think this is now also imported | 10:05 |
| noonedeadpunk | https://opendev.org/openstack/openstack-ansible-plugins/src/branch/master/playbooks/glance.yml#L45-L54 | 10:05 |
| kleini | I am still on 2023.1, so install_defaults is not available. have to find another solution | 10:20 |
| noonedeadpunk | yeah, it's not on 2023.1 :( | 10:26 |
| noonedeadpunk | it was added only on 2024.2 | 10:27 |
| kleini | I have a workaround on my staging system. | 10:28 |
| kleini | https://paste.qa.open-xchange.com/hawuyewawi.md works | 10:55 |
| noonedeadpunk | kleini: um, is that your internal paste service | 10:56 |
| noonedeadpunk | as I think it resolves to rfc 1918 network | 10:57 |
| kleini | ups | 11:55 |
| kleini | https://paste.opendev.org/show/baoKB3VbTj7qeu3phyu6/ | 11:55 |
| opendevreview | Marcus Klein proposed openstack/openstack-ansible-ops master: upgraded grafana.grafana collection does not need ansible fact vars anymore https://review.opendev.org/c/openstack/openstack-ansible-ops/+/950411 | 13:00 |
| opendevreview | Marcus Klein proposed openstack/openstack-ansible-ops master: grafana.grafana works without ansible fact vars https://review.opendev.org/c/openstack/openstack-ansible-ops/+/950411 | 13:02 |
| opendevreview | OpenStack Release Bot proposed openstack/openstack-ansible stable/2025.1: Update .gitreview for stable/2025.1 https://review.opendev.org/c/openstack/openstack-ansible/+/950417 | 13:25 |
| opendevreview | OpenStack Release Bot proposed openstack/openstack-ansible stable/2025.1: Update TOX_CONSTRAINTS_FILE for stable/2025.1 https://review.opendev.org/c/openstack/openstack-ansible/+/950418 | 13:25 |
| opendevreview | OpenStack Release Bot proposed openstack/openstack-ansible master: Update master for stable/2025.1 https://review.opendev.org/c/openstack/openstack-ansible/+/950419 | 13:25 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/2025.1: [doc] Update doc for the stable branch https://review.opendev.org/c/openstack/openstack-ansible/+/950428 | 14:22 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start development of 2025.2 (Flamingo) https://review.opendev.org/c/openstack/openstack-ansible/+/950261 | 14:47 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start development of 2025.2 (Flamingo) https://review.opendev.org/c/openstack/openstack-ansible/+/950261 | 14:48 |
| opendevreview | Merged openstack/openstack-ansible master: Update master for stable/2025.1 https://review.opendev.org/c/openstack/openstack-ansible/+/950419 | 14:51 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start development of 2025.2 (Flamingo) https://review.opendev.org/c/openstack/openstack-ansible/+/950261 | 14:58 |
| noonedeadpunk | #startmeeting openstack_ansible_meeting | 15:00 |
| opendevmeet | Meeting started Tue May 20 15:00:42 2025 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'openstack_ansible_meeting' | 15:00 |
| noonedeadpunk | #topic rollcall | 15:00 |
| noonedeadpunk | o/ | 15:00 |
| jrosser | o/ hello | 15:01 |
| noonedeadpunk | #topic office hours | 15:02 |
| noonedeadpunk | so I have good and bad news kinda | 15:03 |
| noonedeadpunk | good one, is that we've branched 2025.1 | 15:03 |
| noonedeadpunk | And we're pretty much in time for the release in 2 weeks | 15:03 |
| noonedeadpunk | despite most things were not done at last minute, we still having a release with no time to spare | 15:04 |
| noonedeadpunk | And I wanted to say with way lower amount of stress as well | 15:04 |
| noonedeadpunk | if not... EL10 situation | 15:04 |
| jrosser | i think we just have to let that go for a while | 15:05 |
| jrosser | seems like something that will eventually come (CI nodes) | 15:05 |
| noonedeadpunk | and here bad news are coming. As python 3.11 is the minimal requirement, I did include drop of all EL9 related jobs to | 15:05 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/openstack-ansible/+/950261 | 15:05 |
| jrosser | i did a patch also to drop jammy | 15:05 |
| noonedeadpunk | I actually decided it to squash with this one | 15:06 |
| noonedeadpunk | as it would be conflicting anyway | 15:06 |
| jrosser | no problem, yes | 15:06 |
| noonedeadpunk | I did not do any deep clean-up for EL though | 15:06 |
| noonedeadpunk | IT was more of docs/matrix/jobs thing | 15:06 |
| noonedeadpunk | and I wanna start looking locally at el10 support asap | 15:07 |
| opendevreview | Merged openstack/openstack-ansible stable/2025.1: Update .gitreview for stable/2025.1 https://review.opendev.org/c/openstack/openstack-ansible/+/950417 | 15:07 |
| noonedeadpunk | nasty part, that we will have to backport it for upgrade reasons... | 15:07 |
| noonedeadpunk | and I really don't like this specific part of it | 15:08 |
| noonedeadpunk | But, well... we have what we have I guess... | 15:08 |
| jrosser | we certainly do | 15:08 |
| noonedeadpunk | also I left rocky 9 molecule jobs | 15:08 |
| noonedeadpunk | as where they are used, they should not hurt just for sanity checks of the codepath | 15:09 |
| jrosser | i am not sure how much i like having to backport a ton of stuff either | 15:10 |
| jrosser | it is currently so much work to keep up with the EOL / unmaintained fall out that i just don't know if it is a good idea | 15:10 |
| noonedeadpunk | it can be not _that_ bad if it's the next thing we land | 15:10 |
| noonedeadpunk | as more or less clean backports can be done with a single button in gerrit | 15:10 |
| noonedeadpunk | but then we're dropping an upgrade path, which is also not good | 15:11 |
| noonedeadpunk | and I think it's me to blame, as I didn't manage to work on support in time, totally missed that we can't do this next cycle | 15:12 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start development of 2025.2 (Flamingo) https://review.opendev.org/c/openstack/openstack-ansible/+/950261 | 15:13 |
| jrosser | thats not entirely fair - to land support for a whole OS with major changes that maybe you don't even use for deployments | 15:13 |
| jrosser | imho we really need more hands on the rh derived stuff in total | 15:13 |
| jrosser | the debian and ubuntu OS upgrades are almost a no-op in comparison | 15:14 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Start development of 2025.2 (Flamingo) https://review.opendev.org/c/openstack/openstack-ansible/+/950261 | 15:14 |
| noonedeadpunk | well, I don't use, but it come really handy for me couple of times in arguments | 15:14 |
| noonedeadpunk | where it was - "we want EL, as we trust in it" - "well, maybe let;s start with deb, and if it won't work - we can always seamingly migrate to EL?" - "lgtm" kind of conversatrions | 15:15 |
| noonedeadpunk | we do OS upgrades through re-install anyway btw, so if not mentioning amount of changes required in code/packages/etc - for operators upgradfe process is the same | 15:16 |
| noonedeadpunk | but I totally get what you're saying | 15:16 |
| noonedeadpunk | and I agree with it | 15:16 |
| noonedeadpunk | just from the "product" prespective better to have such upgrade release... | 15:16 |
| NeilHanlon | ah! | 15:17 |
| jrosser | yes thats very true | 15:17 |
| * NeilHanlon got distracted by prometheus | 15:17 | |
| NeilHanlon | sorry :D | 15:17 |
| jrosser | easy to happen :) | 15:17 |
| noonedeadpunk | we're discussing dropping Rocky support :D | 15:18 |
| NeilHanlon | sry reading back :D | 15:18 |
| noonedeadpunk | so you haven't missed anything important :p | 15:18 |
| NeilHanlon | hah | 15:18 |
| NeilHanlon | no it's OK, i mean.. I get it | 15:18 |
| jrosser | seems maybe the immediate issue is getting more horsepower on the CI node issue | 15:18 |
| noonedeadpunk | But in seriosness, I wanna start doing patches this week | 15:19 |
| jrosser | as anyone can do local dev with a cloud image and make patches | 15:19 |
| jrosser | but we can't test/merge anything right now sensibly | 15:19 |
| NeilHanlon | and I agree w/ jrosser about it not being really all on your plate noonedeadpunk especially when it's _not_ something you deploy actively | 15:19 |
| NeilHanlon | but passing blame around isn't probably productive :D | 15:19 |
| NeilHanlon | the immediate need is to fix for our current users and make sure we can keep pushing code we are confident in because it's passing CI | 15:20 |
| noonedeadpunk | I'd actually vote on landing EL10 even without testing.... Just openly stating that everywhere to manage expectations | 15:20 |
| noonedeadpunk | as I believe that CI might be solved sooner then later | 15:21 |
| NeilHanlon | another possible interesting thing re: major version upgrades is Oracle recently did this: https://github.com/openela/leapp-repository | 15:21 |
| noonedeadpunk | we can add jobs as NV to find issues and them set as voting | 15:21 |
| NeilHanlon | but that's tangential at this point as it's just more work we'd need to do to maintain actors for doing openstack upgrades atop rocky and i prefer not doing that anyways | 15:22 |
| noonedeadpunk | right, I prefer not upgrading ubuntu either, whenever I can | 15:22 |
| noonedeadpunk | jsut re-install is way more trivial if you have all internal things automated anyway | 15:22 |
| noonedeadpunk | (and take less time) | 15:23 |
| jrosser | i think i miswrote earlier about OS upgrades, i really meant introducing jobs for a new ubuntu/debian tends to be very trivial | 15:23 |
| NeilHanlon | right, that's sorta the whole reason we use ansible ! | 15:23 |
| noonedeadpunk | jrosser: yeash, that's true | 15:23 |
| NeilHanlon | jrosser: yeah I think that also threw me off but i still wanted to mention it's technically more possible now | 15:23 |
| noonedeadpunk | apparmor issues were not trivial this time around though | 15:24 |
| jrosser | anyway :) if you want to make some patches regardless that is OK | 15:24 |
| noonedeadpunk | so yeah, I will check on what it would take to add EL10 support with local aio | 15:25 |
| NeilHanlon | have we poked mnasiadka about the python3.11 stuff btw? | 15:25 |
| noonedeadpunk | and we'll see if/how/when to land them | 15:25 |
| jrosser | i was thinking to look at the usgi script thing (maybe even later today) | 15:25 |
| NeilHanlon | we were chatting about NFV sig stuff this morning.. | 15:25 |
| jrosser | as i see that some services are migrating with no backward compatibility | 15:25 |
| NeilHanlon | i'm almost at the point where like.. i'll just go rebuild all the things we need to make python3.11 work | 15:25 |
| mnasiadka | What python3.11 stuff? :) | 15:25 |
| noonedeadpunk | I now for fact that python3-libvirt is required by nova, and it's shipped only for 3.9 | 15:26 |
| * NeilHanlon signing myself up for more work as always | 15:26 | |
| mnasiadka | Ah, you tried the same thing as me | 15:26 |
| noonedeadpunk | mnasiadka: I learned that with EL8 I think | 15:26 |
| opendevreview | Merged openstack/openstack-ansible stable/2025.1: Update TOX_CONSTRAINTS_FILE for stable/2025.1 https://review.opendev.org/c/openstack/openstack-ansible/+/950418 | 15:26 |
| noonedeadpunk | under very alike circumstances | 15:26 |
| noonedeadpunk | (or maybe it was 7? who knows) | 15:26 |
| NeilHanlon | Enterprise Linux: the pain that keeps on giving | 15:27 |
| NeilHanlon | why do i do this to myself? lol | 15:27 |
| noonedeadpunk | and I have memories of libselinux bindings for python as well, but there were some ways around... | 15:27 |
| noonedeadpunk | NeilHanlon: great question, lol "D | 15:27 |
| noonedeadpunk | but I'm really impressed how ppl continue shooting themselves in the leg | 15:28 |
| noonedeadpunk | by building against cnetos for EL, and things like that | 15:28 |
| noonedeadpunk | dropping cpu flags for still used hardware... | 15:28 |
| noonedeadpunk | doh | 15:28 |
| noonedeadpunk | anyway | 15:29 |
| NeilHanlon | psh isn't everyone replacing their servers every 3 years to fit more pci lanes to inference AI or something? | 15:29 |
| mnasiadka | Should we all stop supporting EL?:) | 15:29 |
| NeilHanlon | mnasiadka: in protest? :P | 15:29 |
| noonedeadpunk | NeilHanlon: and also efficiency per watt, and save costs on cooling, sure | 15:29 |
| NeilHanlon | nah i mean, we all know it's been a weird situation the past few years and hasn't gotten really any clearer esp. with the CI situation and not really having any idea what's up with that all | 15:30 |
| noonedeadpunk | mnasiadka: frankly? I'd internally love to do that, but I kinda realize that it's not gonna end well | 15:30 |
| noonedeadpunk | internally, in terms of very personal opinion | 15:31 |
| noonedeadpunk | as when trying to sell openstack, more then half are not ready to consider anything except EL | 15:32 |
| noonedeadpunk | or at the very least they require the ability of rollback to EL | 15:33 |
| NeilHanlon | i just had that conversation with a colleague in the rocky project on our testing team | 15:33 |
| NeilHanlon | his boss wants him to investigate openstack and talk to Canonical and he is firmly planted he'd get it from RH instead | 15:33 |
| NeilHanlon | i'm always trying to abduct more people into our cult :P | 15:34 |
| noonedeadpunk | right :) | 15:34 |
| noonedeadpunk | I especially like cases of moving from VMware due to screwed policies to RH OpenStack | 15:35 |
| jrosser | mnasiadka: while you are around - did i understand right that you were looking at the rh-10-ish nodpool images? | 15:35 |
| noonedeadpunk | Just as if IBM is any better then Broadcom at global scale of screwing up customers | 15:35 |
| mnasiadka | Yes, I’m trying to help tonyb in CS10 work | 15:36 |
| noonedeadpunk | I can try to help if there's a need | 15:37 |
| noonedeadpunk | but I did not have time yet to double check the state after asking in #opendev | 15:38 |
| NeilHanlon | noonedeadpunk: yeah i chose not to mention that to that colleague :P | 15:38 |
| NeilHanlon | mnasiadka: and, sorry i fell off, but did you end up working on Rocky 9 nodepool images, too? | 15:39 |
| mnasiadka | @NeilHanlon: yup, that’s done ;) | 15:39 |
| NeilHanlon | mnasiadka: add another beer to my tab for you | 15:40 |
| NeilHanlon | ok, so.. | 15:45 |
| NeilHanlon | short term, we drop rocky jobs and backport to the N-1(-1,-1?) releases so we can land changes | 15:46 |
| NeilHanlon | at the same time, we maybe work on landing el10? I volunteer DavidGomez to help. :) | 15:46 |
| NeilHanlon | noonedeadpunk: does that seem like a reasonable next steps? | 15:47 |
| DavidGomez | of course, happy to help | 15:47 |
| noonedeadpunk | NeilHanlon: we don't need to backport jobs removal | 15:48 |
| noonedeadpunk | we'd need to backport EL10 patches | 15:48 |
| NeilHanlon | ah.. | 15:49 |
| noonedeadpunk | ideally | 15:49 |
| NeilHanlon | i had that reversed in my head | 15:49 |
| NeilHanlon | well, more experience for DavidGomez! lol | 15:49 |
| noonedeadpunk | lol, I won't refuse help, sure :) | 15:49 |
| NeilHanlon | sorry david, you can get me back at the next onsite :P | 15:49 |
| noonedeadpunk | but also adding rocky 10 image to nodepool would be amazing | 15:50 |
| DavidGomez | haha not at all, sounds like a good learning opportunity | 15:51 |
| noonedeadpunk | ok, cool, sounds like a plan then | 15:52 |
| noonedeadpunk | #endmeeting | 15:53 |
| opendevmeet | Meeting ended Tue May 20 15:53:51 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:53 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2025/openstack_ansible_meeting.2025-05-20-15.00.html | 15:53 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2025/openstack_ansible_meeting.2025-05-20-15.00.txt | 15:53 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2025/openstack_ansible_meeting.2025-05-20-15.00.log.html | 15:53 |
| NeilHanlon | thanks noonedeadpunk for running the meeting as always! | 15:54 |
| NeilHanlon | 🫡 | 15:54 |
| noonedeadpunk | thanks for coming! | 15:54 |
| * NeilHanlon goes back to being distracted by prometheus | 15:54 | |
| NeilHanlon | whoever designed all this was a sadist, btw | 15:54 |
| DavidGomez | later all! | 15:55 |
| NeilHanlon | thanks for hanging DavidGomez :) | 15:55 |
| mnasiadka | @noonedeadpunk: rocky10 is next on my list after cs10 (but first it needs to be released…) | 15:55 |
| opendevreview | Jonathan Rosser proposed openstack/ansible-role-uwsgi master: Add ability to specify uwsgi module https://review.opendev.org/c/openstack/ansible-role-uwsgi/+/950437 | 15:57 |
| NeilHanlon | Rocky 10 is pretty close | 15:59 |
| NeilHanlon | we did an initial compose run last night to see how many packages we needed to re-sign (the system is weird) and it was really clean | 16:00 |
| opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_glance master: Switch from wsgi script to wsgi module https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/950438 | 16:00 |
| jrosser | noonedeadpunk: if you think these wsgi module changes are broadly correct i can push more tomorrow | 16:14 |
| noonedeadpunk | jrosser: I think you'll need to drop this? https://opendev.org/openstack/openstack-ansible-os_glance/src/branch/master/vars/main.yml#L59 | 17:05 |
| noonedeadpunk | as well | 17:05 |
| jrosser | oh that is a bit horrible | 17:09 |
| opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_glance master: Switch from wsgi script to wsgi module https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/950438 | 21:04 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!