15:02:26 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:02:26 <opendevmeet> Meeting started Tue Apr 12 15:02:26 2022 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:26 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:02:31 <noonedeadpunk> #topic rollcall
15:02:37 <jrosser> o/ hello
15:02:40 <noonedeadpunk> hey everyone o/
15:03:15 <damiandabrowski[m]> hey! (on a phone for next 20min)
15:03:50 <mgariepy> hey
15:04:24 <noonedeadpunk> #topic office hours
15:05:31 <noonedeadpunk> So PTG results. I had sent email tomorrow, but seems I mixed up a bit emails it should go from, so I guess it haven't landed on ML and waits for moderation....
15:06:12 <noonedeadpunk> s/tomorow/today lol
15:06:43 <noonedeadpunk> I also started looking at CentOS distro jobs... And they are broken is so stupid/nasty ways....
15:07:25 <noonedeadpunk> I would actually say - rhel'ish way
15:08:16 <noonedeadpunk> I think that intention to drop them were quite reasonable....
15:08:27 <jrosser> so related - Z will not support python3.6.....
15:08:46 <jrosser> which i think means that Y *has* to be centos8->9 transition release?
15:08:58 <noonedeadpunk> yup....
15:09:03 <jrosser> /o\
15:09:22 <noonedeadpunk> well, iirc centos 8 has py3.8
15:09:31 <noonedeadpunk> but as usual without libs built
15:10:03 <noonedeadpunk> as we run ansible in 3.8 venv right now
15:11:16 <noonedeadpunk> https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/bootstrap-ansible.sh#L76
15:11:54 <jrosser> hrrm
15:12:07 <noonedeadpunk> I wonder if we even use that for service venv
15:12:49 <jrosser> it would be possible - though i expect ceph and libvirt bindings are going to be troublesome
15:13:00 <noonedeadpunk> nah, we don't now
15:13:15 <jrosser> i don't expect it to go well tbh
15:13:17 <noonedeadpunk> yeah, exactly
15:13:26 <jrosser> i think we tried this right at the start for centos8
15:13:53 <noonedeadpunk> I just can recalled we tried indeed:) but as you said - they don't ship bindings for $reason
15:14:24 <jrosser> @NeilHanlon whats the position on python versions for Rocky?
15:14:37 <jrosser> eg Zed needing > 3.6
15:17:05 <noonedeadpunk> Btw I will propose patches for switching to Y toorrow first thing in the morning
15:17:14 <jrosser> cool
15:22:10 <noonedeadpunk> I also have a proposal of adding damiandabrowski[m] to core reviewers team. If nobody against, I will send ML so everybody could vote.
15:22:31 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-repo_server master: Add facility to store repo contents on a remote mount  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/837587
15:22:40 <noonedeadpunk> If there're any other proposals or nominations - I'm all ears :)
15:24:09 <noonedeadpunk> s/adding/nominating
15:24:52 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-repo_server master: Remove all code for lsync, rsync and ssh  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/837588
15:25:51 <damiandabrowski[m]> thank You! I'd be grateful for joining the core team (and now when I'm done with distro upgrades, I'll have much more time to contribute)
15:26:45 <damiandabrowski[m]> btw. let me copy-paste my message from previous week as it didn't get much attention
15:27:00 <noonedeadpunk> I guess we need also to patch systemd_mount role to install gluster_client?
15:27:10 <mgariepy> congrats damiandabrowski[m] !
15:27:11 <damiandabrowski[m]> Will You be able to have a look at my tempest changes and leave initial review? https://review.opendev.org/q/topic:tempest-damian-2021-12
15:27:14 <damiandabrowski[m]> There is a huge relation chain but I don't think we can avoid it as all of these changes focus on the same files :/ However, they are pretty straightforward so I hope all of them will be merged.
15:27:18 <damiandabrowski[m]> So my idea is to: gather initial reviews from You -> (make corrections) -> rebase all of them -> merge all. What do You think?
15:27:29 <damiandabrowski[m]> thanks! :D
15:27:32 <noonedeadpunk> sounds like a plan:)
15:29:08 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible master: Use glusterfs as a backend for synchronising repo server contents  https://review.opendev.org/c/openstack/openstack-ansible/+/837589
15:29:23 <jrosser> ^ this is basically working locally though i expect upgrades to break
15:30:56 <jrosser> maybe we discussed this enough already earlier but adding systemd_mount into repo_server as the hook into external shared storage seems neat
15:31:54 <damiandabrowski[m]> nice, i didn't expect gluster changes to land that fast :D
15:32:40 <noonedeadpunk> These are ususally lest words before huge issues
15:32:45 <noonedeadpunk> *last
15:32:50 <noonedeadpunk> :D
15:33:02 <jrosser> yeah indeed
15:33:48 <noonedeadpunk> jrosser: what I mean is that systemd_mount should be capable of mounting gluster on their own
15:34:06 <noonedeadpunk> so it should likely include client part when type is gluster
15:34:09 <jrosser> oh yes, it does and it works
15:34:59 <jrosser> the glusterfs role i made has bools for installing the client / server parts but i don't yet know what to connect those to
15:35:16 <noonedeadpunk> eventually we have there logic already https://opendev.org/openstack/ansible-role-systemd_mount/src/branch/master/vars/main.yml#L25-L37
15:35:44 <noonedeadpunk> So it could be independant relatively
15:36:41 <damiandabrowski[m]> btw. noonedeadpunk i received Your 'Zed PTG results' email so it actually has landed properly on ML ;)
15:36:51 <noonedeadpunk> oh, ok
15:36:54 <jrosser> only ugly bit is needing the fuse device for lxc
15:37:03 <noonedeadpunk> I haven't recieved it :/
15:37:13 <noonedeadpunk> yeah.....
15:37:53 <jrosser> and that has to happen in-line in the code rather than in the lxc base image to cover upgrades
15:39:44 <noonedeadpunk> Just in case I already landed some ugly stuff there https://opendev.org/openstack/ansible-role-systemd_mount/src/branch/master/tasks/systemd_install.yml#L16-L47 but yeah, it's not container-specific, but distro specific
15:40:06 <noonedeadpunk> so I agree that in role there shouldn't be lxc crap preferably...
15:41:03 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-repo_server master: Add facility to store repo contents on a remote mount  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/837587
15:41:09 <noonedeadpunk> so dunno what to do better here
15:42:35 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-plugins master: Add role for creating simple glusterfs clients/servers  https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/837582
15:44:44 <noonedeadpunk> I think we can start from that for sure and then re-arrange code if decide to do so.
15:44:46 <jrosser> do we have a priority order for doing the things from https://etherpad.opendev.org/p/osa-Z-ptg
15:46:35 <noonedeadpunk> very good question. I think ssl and keystone rbac should go first ?
15:46:57 <noonedeadpunk> ubuntu 22.04/centos 9 is based on time on hands?
15:47:22 <noonedeadpunk> as basically centos 9 likely rely on gluster (which thankfully landed)
15:47:48 <jrosser> yeah, thats removed the need to lsyncd and EPEL in the repo server, which is ++
15:48:00 <mgariepy> we will be able to remove lsyncd ;)
15:48:37 <noonedeadpunk> nice to see how everybody loves lsyncd :p
15:48:56 <damiandabrowski[m]> if nobody took it yet, I can work on 'cover octavia with PKI role' when I'm done with tempest changes
15:49:03 <mgariepy> lsyncd is not fun ;) but the good part about it is that stuff can be regenerated :) haha
15:50:08 <jrosser> damiandabrowski[m]: that would be good to get some insight into the workings of the PKI role
15:50:25 <jrosser> and also i think there is some careful handling needed for upgrades
15:51:23 <damiandabrowski[m]> ack
15:53:21 <jrosser> the bigger piece of SSL work is doing the backends for all the services
15:55:02 <noonedeadpunk> yup, but also good one. As somewhere we're inventing bycicle to achieve that goal
15:55:36 <noonedeadpunk> which would be really awesome to land things and get them supported
15:56:05 <noonedeadpunk> (they are quite historical to have that said)
16:00:12 <noonedeadpunk> #endmeeting