15:00:18 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:00:18 <opendevmeet> Meeting started Tue Jan 14 15:00:18 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:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:18 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:00:22 <noonedeadpunk> #topic rollcall
15:00:23 <noonedeadpunk> o/
15:04:56 <damiandabrowski> hi!
15:05:58 <noonedeadpunk> #topic office hours
15:06:11 <noonedeadpunk> so, it seems all current patches for molecule has been landed
15:06:24 <noonedeadpunk> #link https://review.opendev.org/q/topic:%22osa/molecule%22
15:06:57 <noonedeadpunk> meaning, that only plugins repo left on the old functional tests. And we can deprecate the repo once it's done
15:07:21 <noonedeadpunk> afaik there were some complications with running lxc inside of docker :D
15:07:49 <noonedeadpunk> jrosser was working on that, so not sure if there are more updates
15:08:13 <jrosser> oh i am looking at the just now
15:08:25 <jrosser> (keep getting distracted so slooow progress)
15:09:09 <jrosser> but i basically have lxc containers being created in docker now and am just trying to port how things work in the test repo inventory to molecule, so that lxc_containers_create will work
15:09:13 <noonedeadpunk> btw, damiandabrowski, presence of molecule should help out while creating change for the pki role for support of vault "driver"
15:09:42 <noonedeadpunk> but I guess you'd need to create a new scenario for that path
15:10:08 <noonedeadpunk> jrosser: ok, amazing, sounds like really good progress
15:10:22 <damiandabrowski> awesome!
15:10:26 <noonedeadpunk> and we will be able to finally drop tests repo after so many years
15:10:40 <noonedeadpunk> (drop -> deprecate)
15:10:47 <damiandabrowski> just to let everyone know: I plan to start work on adding hashicorp vault support to ansible-role-pki in like 2 weeks
15:12:52 <noonedeadpunk> next thing - httpd role
15:12:54 <noonedeadpunk> #link https://review.opendev.org/q/topic:%22osa/httpd_role%22
15:13:42 <noonedeadpunk> while repo still not officially reconginzed by TC (https://review.opendev.org/c/openstack/governance/+/935694)
15:14:04 <noonedeadpunk> it has all required votes to land
15:19:15 <noonedeadpunk> then I've seen a review on https://review.opendev.org/c/openstack/openstack-ansible/+/938275
15:20:21 <noonedeadpunk> I'm not 100% sure, but it somehow feels being a chicken-egg rather then anything else
15:23:56 <jrosser> that seems so
15:24:14 <noonedeadpunk> though I do see same issue with skyline
15:28:25 <noonedeadpunk> so I'm thinking if it would makse to disable upgrade jobs and try to land requirements
15:28:37 <noonedeadpunk> as I ws not able to replicate issue running upgrade job locally
15:28:51 <jrosser> that sounds sensible
15:30:02 <noonedeadpunk> ok, will try to edit the patch and propose a follow-up with re-enabling upgrade jobs
15:31:18 <noonedeadpunk> btw, on weekends I was working on some "healthchecks" and come up with a playbook (well, playbook and an include task for it, so more of a role) for testing network connectivity
15:31:29 <noonedeadpunk> which I aimed to run after setup-hosts
15:32:08 <noonedeadpunk> so it discovers hosts/networks from inventory and runs pings and iperf between hosts[0] and hosts[1:]
15:32:27 <jrosser> MTU check would be another good thing to test
15:32:35 <noonedeadpunk> good point
15:32:47 <noonedeadpunk> will add that.
15:33:05 <noonedeadpunk> and I was also thinking if it's worth adding to plugins/healtchecks or ops repo?
15:33:14 <noonedeadpunk> or nobody cares about stuff like that ?:D
15:33:46 <jrosser> well we have something similar already
15:34:33 <jrosser> but i expect that not all deployments have the same interfaces to test between
15:34:53 <noonedeadpunk> well, it's getting data from openstack_inventory
15:35:23 <noonedeadpunk> So if there's a `container_networks` defined - it would work nicely
15:35:43 <jrosser> we also do 'negative testing' to ensure that the different networks are not accidentally routed together
15:36:16 <noonedeadpunk> that would be an interesting one
15:36:23 <jrosser> but on the subject of networking
15:36:24 <noonedeadpunk> and tricky given they could be just firewalled
15:36:55 <jrosser> removal of linuxbridge will bring for us some giant migration need
15:37:40 <noonedeadpunk> I was just leveraging systemd_networkd for network setup so realized that would need some kind of test to ensure that all vlans are actually reachable in expected places
15:38:05 <jrosser> yes this would be interesting to see
15:38:18 <noonedeadpunk> negative testing should be also doable though, except when we're talking about networks that are not defined in osa, but present on hosts
15:38:37 <noonedeadpunk> as then it would know nothing about them
15:39:57 <noonedeadpunk> ok, I can try to push smth (at my free time) and will be totally fine if it's rejected or abandoned
15:42:31 <noonedeadpunk> and next probably worth starting looking into CentOS 10....
15:43:30 <noonedeadpunk> oh, btw
15:43:44 <noonedeadpunk> there was an interesting ML regarding rabbitmq quorum queues
15:44:19 <noonedeadpunk> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/XRS3IQFHWX6LHYMUI4XIFPDLYIQGPYHD/
15:44:36 <noonedeadpunk> and sounds like we need to do some improvements/health checks there
15:53:42 <opendevreview> Merged openstack/openstack-ansible master: Fix inventory adjustment for legacy container naming  https://review.opendev.org/c/openstack/openstack-ansible/+/939110
15:57:50 <NeilHanlon> o/ better late than never? 🙃
15:58:05 <noonedeadpunk> sure thing!
15:59:59 <noonedeadpunk> #endmeeting