| noonedeadpunk | fwiw, https://review.opendev.org/c/openstack/openstack-ansible/+/972469 has a nasty consequences for upgrades | 08:11 |
|---|---|---|
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Move from setup.cfg to pyproject.toml https://review.opendev.org/c/openstack/openstack-ansible/+/972481 | 08:11 |
| opendevreview | Merged openstack/openstack-ansible-ops master: Remove obsolete flavors generation script https://review.opendev.org/c/openstack/openstack-ansible-ops/+/971799 | 10:15 |
| jrosser | looking at this, are we actually testing `dir` type specifically https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/972592 | 10:17 |
| jrosser | well, maybe thats what the _infra_ jobs are defaulting to | 10:18 |
| opendevreview | Ivan Anfimov proposed openstack/openstack-ansible-os_magnum stable/2025.2: Do not remove policy.yaml file https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/974824 | 10:36 |
| opendevreview | Dmitriy Chubinidze proposed openstack/openstack-ansible-os_horizon master: Added new configuration option horizon_swift_panel_full_listing https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/974465 | 10:36 |
| noonedeadpunk | jrosser: so our default is dir indeed. the thing is, that we don't really need to have a base container, if we're using dir | 11:08 |
| noonedeadpunk | the task was added as part of the merge: https://opendev.org/openstack/openstack-ansible-lxc_hosts/commit/7fc5e9950ea9e8b379295837fede70f864502439 | 11:10 |
| noonedeadpunk | as you see - "Create base container" used to be in specific backends only | 11:10 |
| noonedeadpunk | so it was genaralized. But why not to have this task to execute conditionally? | 11:10 |
| jrosser | oh i was just unsure if the test scenarios actually covered `dir` to make sure we'd not broken it with this change somehow | 11:35 |
| jrosser | not so much a question about the change itself | 11:36 |
| noonedeadpunk | ah, got it | 12:09 |
| noonedeadpunk | I think we should be having separate chekcs? | 12:09 |
| noonedeadpunk | ie https://zuul.opendev.org/t/openstack/build/42af1200c46b4f0c816450d5c6910192 | 12:09 |
| noonedeadpunk | https://zuul.opendev.org/t/openstack/build/c307e6e94f33478bae602e59048f199b | 12:09 |
| noonedeadpunk | https://zuul.opendev.org/t/openstack/build/7fc62a58b549457ca91ca775f9af1659 | 12:09 |
| noonedeadpunk | and then dir is the default one, yes | 12:10 |
| noonedeadpunk | https://opendev.org/openstack/openstack-ansible-lxc_hosts/src/branch/master/defaults/main.yml#L83 | 12:11 |
| noonedeadpunk | we don't override it except specific scenarios | 12:11 |
| opendevreview | Merged openstack/openstack-ansible-os_magnum master: Remove outdate parameter send_cluster_metrics https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/970711 | 12:16 |
| opendevreview | Merged openstack/openstack-ansible-os_magnum master: Do not remove policy.yaml file https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/967183 | 12:16 |
| opendevreview | Merged openstack/openstack-ansible-lxc_hosts master: Remove outdate URL for qgroup limits used for file system quotas https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/972791 | 12:17 |
| opendevreview | Merged openstack/openstack-ansible master: Update URL in bindep.txt https://review.opendev.org/c/openstack/openstack-ansible/+/972806 | 14:49 |
| * jrosser expects a bunch of auto-generated patches..... ^^ | 14:54 | |
| noonedeadpunk | huh.... | 14:55 |
| jrosser | indeed | 14:55 |
| noonedeadpunk | I'd expect them to appear by now | 14:56 |
| noonedeadpunk | it wasn't in promote... | 14:56 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ansible-config_template master: Updated from OpenStack Ansible Integrated repository https://review.opendev.org/c/openstack/ansible-config_template/+/974877 | 14:57 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ansible-hardening master: Updated from OpenStack Ansible Integrated repository https://review.opendev.org/c/openstack/ansible-hardening/+/974879 | 14:57 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ansible-role-python_venv_build master: Updated from OpenStack Ansible Integrated repository https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/974880 | 14:57 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ansible-role-systemd_mount master: Updated from OpenStack Ansible Integrated repository https://review.opendev.org/c/openstack/ansible-role-systemd_mount/+/974881 | 14:57 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ansible-role-systemd_networkd master: Updated from OpenStack Ansible Integrated repository https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/974882 | 14:57 |
| opendevreview | OpenStack Proposal Bot proposed openstack/ansible-role-systemd_service master: Updated from OpenStack Ansible Integrated repository https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/974883 | 14:57 |
| jrosser | ahha there we go | 14:58 |
| noonedeadpunk | #startmeeting openstack_ansible_meeting | 15:04 |
| opendevmeet | Meeting started Tue Jan 27 15:04:43 2026 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:04 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:04 |
| opendevmeet | The meeting name has been set to 'openstack_ansible_meeting' | 15:04 |
| noonedeadpunk | #topic rollcall | 15:04 |
| noonedeadpunk | o/ | 15:04 |
| noonedeadpunk | sorry for being late | 15:04 |
| damiandabrowski | hi! | 15:05 |
| noonedeadpunk | #topic office hours | 15:10 |
| noonedeadpunk | ok, I think one of big questions I have now - is what objections/comments do we have to the vault patch? | 15:11 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/ansible-role-pki/+/948881 | 15:11 |
| jrosser | o/ hello | 15:11 |
| noonedeadpunk | I think it had most of requested changes | 15:15 |
| noonedeadpunk | so it would be nice if we could do another round of review and see where we are | 15:15 |
| jrosser | its still difficult to review (i mean not because its bad, theres just complexity and vault is not necessarily obvious) | 15:16 |
| noonedeadpunk | yeah, that's true | 15:16 |
| jrosser | but if you are to be using it internally then thats a +ve vs something thats speculative | 15:17 |
| jrosser | a bit like how we are running mcapi here so are able to maintain all that stuff better than if we were not | 15:17 |
| jrosser | so i guess thats what i;m interested in, if you have this rolled out and working or will do that once it merges | 15:17 |
| noonedeadpunk | so we already have the vault, we just workaround a lot, just because it needs changes to pretty much everything... | 15:18 |
| noonedeadpunk | but I think damiandabrowski tested the full set in sandbox | 15:18 |
| noonedeadpunk | so yes, we intended to use it once it becomes available, basically with upgrade to 2026.1 | 15:19 |
| jrosser | if you're able to test it as it merges (if we get on with it) then there will be some good confidence its ok | 15:19 |
| damiandabrowski | that's right I tested it on my AIO environment some time ago, if it makes it any easier I to review, I can set up another AIO and give you an access | 15:20 |
| jrosser | heh -ETIME | 15:20 |
| noonedeadpunk | I think we will convert our dev envs to it once it merges, yes | 15:20 |
| jrosser | i think it's just good confidence to know that you're using it and fixes will get made once/if nececessary | 15:20 |
| jrosser | tbh i think that is the best way to move forward | 15:21 |
| jrosser | take another pass at the review as far as is possible without running it | 15:21 |
| noonedeadpunk | I have some level on confidence in molcule :D | 15:21 |
| jrosser | and let it go in | 15:21 |
| jrosser | yeah true | 15:21 |
| noonedeadpunk | it feels like the most imporant things are covered in tests | 15:22 |
| jrosser | did we decide if to have a top level test scenario that deploys vault | 15:23 |
| jrosser | or perhaps we can be happy that if the molecule tests for PKI have good coverage, we don't need to | 15:23 |
| noonedeadpunk | I feel like we are having too many jobs right now | 15:24 |
| damiandabrowski | https://review.opendev.org/c/openstack/openstack-ansible/+/948889/comment/bf25225a_76df5807/ | 15:24 |
| noonedeadpunk | I'd really like to look through them and validate if we need all existing ones | 15:24 |
| noonedeadpunk | but maybe we can add one vault job for ubuntu just in case | 15:25 |
| damiandabrowski | there was a proposal here to run only a single vault job in our baseline, and run more vault scnearios for PKI role only | 15:25 |
| noonedeadpunk | yeah | 15:25 |
| noonedeadpunk | but this was not updated ;) | 15:26 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/openstack-ansible/+/948889/2/zuul.d/project-templates.yaml | 15:26 |
| noonedeadpunk | hm, I'd expect more patches to be pushed actually for https://review.opendev.org/q/topic:%22openstack/openstack-ansible-sync/sync-files%22 | 15:29 |
| noonedeadpunk | it feels there's somewhere an issue in role selection logic | 15:30 |
| damiandabrowski | yeah, I'll fix it. Didn't focus on this because https://review.opendev.org/c/openstack/openstack-ansible/+/948889/13 doesn't run any jobs | 15:30 |
| noonedeadpunk | *target repo | 15:30 |
| damiandabrowski | but now I wonder, why? | 15:30 |
| noonedeadpunk | I think there was smth with dependencies? | 15:31 |
| noonedeadpunk | like one was abandoned or smth? | 15:31 |
| damiandabrowski | it complains that several changes "are needed" but I'm not sure what exactly does it mean | 15:31 |
| damiandabrowski | hmm, you may be right...I'll make sure there's no dependency to abandoned patch | 15:31 |
| noonedeadpunk | let's maybe cross the bridge when we come to it? | 15:32 |
| noonedeadpunk | I think it will be easier to untangle when we land things | 15:32 |
| damiandabrowski | okay, makes sense | 15:32 |
| noonedeadpunk | there is one thing, which brakes upgrades: | 15:33 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/openstack-ansible/+/972469 | 15:34 |
| noonedeadpunk | it would be actually nice to have that fix in, as 2025.2 is detected as 2025.1 tag | 15:34 |
| noonedeadpunk | so venvs are not rebuilt | 15:34 |
| noonedeadpunk | or well, they kinda are, but also their naming is not mathing the tag | 15:34 |
| noonedeadpunk | and then pretty much we'd need to agree on what's needed for the 32.1.0 tag | 15:35 |
| noonedeadpunk | there are actually plenty of stuff lying around all over repos... | 15:37 |
| jrosser | yes theres a lot of outstanding patches to deal with | 15:37 |
| jrosser | some of which i'm unsure about | 15:38 |
| noonedeadpunk | feel free to bring them in for a chat once you see them? | 15:39 |
| noonedeadpunk | or just -1 :D | 15:39 |
| noonedeadpunk | (-2) | 15:39 |
| jrosser | sure, i need to ask about more of them here really | 15:41 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Move from setup.cfg to pyproject.toml https://review.opendev.org/c/openstack/openstack-ansible/+/972481 | 15:43 |
| noonedeadpunk | I have not yet started looking at freezer/watcher roles | 15:44 |
| noonedeadpunk | though, it was discovered that we have not properly re-retired monasca ones | 15:44 |
| noonedeadpunk | #link https://review.opendev.org/c/openstack/project-config/+/974773 | 15:44 |
| noonedeadpunk | I mentally burried it, but on paper it was "revived" | 15:45 |
| noonedeadpunk | I am trying to "fix" some freezer parts first, before moving to role part | 15:46 |
| jrosser | were you going for scheduled cinder backups? | 15:46 |
| noonedeadpunk | yup | 15:46 |
| jrosser | excellent i would be interested in that | 15:46 |
| jrosser | it is so bad from a user POV that cinder backup currently cant schedule | 15:47 |
| noonedeadpunk | that's pretty much the goal we have | 15:47 |
| noonedeadpunk | there's been quite some patches merged in last 2 weeks to have that said. | 15:47 |
| noonedeadpunk | but yeah | 15:47 |
| jrosser | kind of way off topic but did manila virtio-fs ever get to be real? | 15:48 |
| noonedeadpunk | I think it should be in now? | 15:48 |
| noonedeadpunk | though you'd need hugepages enabled I think | 15:49 |
| jrosser | hmmm i totally took my eye off of that | 15:49 |
| jrosser | ewwww | 15:49 |
| noonedeadpunk | and also no hotplug | 15:50 |
| noonedeadpunk | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/WEB3XJYWWSW672N4UAX3VFJSQEE6V7RA/ | 15:51 |
| damiandabrowski | when it comes to Manila, it looks like client-side support is still missing | 15:52 |
| damiandabrowski | https://review.opendev.org/q/topic:%22bp/manila_shares_attachments_v3%22 | 15:52 |
| damiandabrowski | and it looks quite abandoned :/ | 15:52 |
| noonedeadpunk | well... | 15:53 |
| noonedeadpunk | I'd say client side overall looks abandoned today | 15:53 |
| noonedeadpunk | on this positive note.... | 15:57 |
| noonedeadpunk | #endmeeting | 15:57 |
| opendevmeet | Meeting ended Tue Jan 27 15:57:35 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:57 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2026/openstack_ansible_meeting.2026-01-27-15.04.html | 15:57 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2026/openstack_ansible_meeting.2026-01-27-15.04.txt | 15:57 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2026/openstack_ansible_meeting.2026-01-27-15.04.log.html | 15:57 |
| opendevreview | Merged openstack/openstack-ansible-os_magnum stable/2025.2: Don't use ansible_host in magnum.conf template https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/974425 | 21:38 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!