15:02:38 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:02:38 <opendevmeet> Meeting started Tue Jun 21 15:02:38 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:38 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:38 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:02:50 <noonedeadpunk> #topic roll call
15:02:58 <noonedeadpunk> hey o/ sorry for being late
15:03:50 <NeilHanlon> o/
15:03:58 <mgariepy> hello
15:04:28 <jrosser_> o/ hello
15:05:20 <noonedeadpunk> #topic office hours
15:05:40 <noonedeadpunk> so. We almost branched Yoga for integrated repo and branched all repos
15:06:22 <noonedeadpunk> except it failing in CI :)
15:06:43 <noonedeadpunk> After we branch we have to drop centos 8
15:07:25 <noonedeadpunk> and Rocky 8 as well as a result mostly because py36 being unsupported by Zed and no python-libvirt bindings for py38
15:07:38 <noonedeadpunk> NeilHanlon: any info about Rocky 9 ?
15:07:38 <jrosser_> NeilHanlon: ^
15:07:41 <jrosser_> :)
15:10:56 <noonedeadpunk> ok, next to that I wonder how you feel about publishing config_template collection on galaxy?
15:11:28 <noonedeadpunk> should we drop symlinks created for compatability as module for that?
15:12:06 <noonedeadpunk> releases team suggested to tag it as 2.0.0 regardless of publishing
15:12:19 <noonedeadpunk> because we dropped py27 support basically
15:12:21 <jrosser_> that would be good
15:12:30 <jrosser_> then its very easily consumable
15:12:40 <NeilHanlon> jrosser_: we have a release candidate! I should have an image available soon-ish and am going to put in a few commits for dib, too
15:12:57 <noonedeadpunk> NeilHanlon: these are very good news!
15:13:18 <jrosser_> fun upgrade path
15:13:24 <noonedeadpunk> then I believe we should backport Rocky 9 support to Y...
15:13:38 <noonedeadpunk> should be quite straightforward?
15:13:54 <noonedeadpunk> given no huge surprises there....
15:13:55 <NeilHanlon> i can help with the python-libvirt bindings for python3.8, if that would help. but also just as happy to move towards 9 and revisit 8 if I have time
15:14:08 <jrosser_> should be - i expect maybe a few places we specifically check for centos-9 or named vars files
15:14:11 <jrosser_> but that can be fixed
15:14:33 <NeilHanlon> totally, i kept a list of the places I had to touch last time so hopefully I'll catch them before review ;)
15:14:51 <jrosser_> i expect it to be much much less work than the original rocky or centos-9
15:14:58 <noonedeadpunk> I believe we could be more carefull now as well
15:16:12 <noonedeadpunk> I guess moving towards 9 might be more perspecitve path. And libvirt thing is just first I recalled but there were likely more
15:16:31 <NeilHanlon> undoubtedly
15:16:34 <jrosser_> if we backport 9 to Y we can drop 8 from master
15:16:37 <jrosser_> that would be nice
15:17:13 <jrosser_> then a bunch more logic / ternary / when: can get removed
15:17:15 <NeilHanlon> that sounds like a reasonable plan. it'd be nice to only support 9 which ideally has less issues than 8 with dependencies
15:17:22 <noonedeadpunk> I bet devstack and projects already dropped 8 for master
15:17:53 <noonedeadpunk> ok, great that Rocky 9 is coming!
15:18:35 <noonedeadpunk> I want to return back to config template. jrosser_ "that would be good" was it about publishing or removing legacy ?:)
15:19:02 <noonedeadpunk> I think for publishing we just need to add this job https://review.opendev.org/c/openstack/ansible-config_template/+/846391/6/zuul.d/project.yaml
15:19:10 <jrosser_> oh well all of it really :)
15:19:48 <noonedeadpunk> I'm not sure how tripleo consumes it actually....
15:20:02 <noonedeadpunk> Won't be surprised if with python setup.py install ....
15:20:23 <noonedeadpunk> But I can recall pushing smth there to switch to collection
15:20:25 <jrosser_> i think that got undone
15:20:41 <jrosser_> when the setup.py modules stuff all went odd
15:21:20 <noonedeadpunk> Ok, i abandoned it https://review.opendev.org/c/openstack/tripleo-ansible/+/820140
15:22:13 <noonedeadpunk> arxcruz|rover: do you recall how you install/consume config_template collection now?
15:22:45 <noonedeadpunk> do you checkout to some specific tag at least?
15:22:52 <arxcruz|rover> not really
15:24:47 <noonedeadpunk> well.. I can propose patch to CI and witness how it fails...
15:37:45 <opendevreview> Dmitriy Rabotyagov proposed openstack/ansible-config_template master: Remove possibility to install as plugin  https://review.opendev.org/c/openstack/ansible-config_template/+/847045
15:38:00 <noonedeadpunk> here we go
15:39:35 <noonedeadpunk> I kind of wonder if we should publish it in galaxy first and then tripleo case would be solved
15:39:45 <noonedeadpunk> as we have that https://opendev.org/openstack/openstack-ansible-os_tempest/src/branch/master/meta/main.yml#L44-L45
15:39:57 <noonedeadpunk> which kind of should pull collection in if it's absent?
15:43:24 <noonedeadpunk> We also have interesting bug that I spoilered during the day regarding zun and etcd
15:43:35 <noonedeadpunk> #link https://bugs.launchpad.net/openstack-ansible/+bug/1979208
15:44:13 <noonedeadpunk> the issue there is for some reason we have etcd installation inside zun role while we also have etcd in playbooks and even have env.d file for it
15:44:24 <noonedeadpunk> So likely this needs some love and refactoring
15:44:41 <noonedeadpunk> will try to look into that
15:45:45 <noonedeadpunk> I beleive that's it for today from myself
15:46:03 <noonedeadpunk> and thanks everybody for working on Y!
15:46:31 <noonedeadpunk> I know last week was tough on amount of things we worked on
15:47:06 <jrosser_> i don't remeber why we have a separate etcd
15:47:23 <noonedeadpunk> we'll figure that out :)
15:47:45 <noonedeadpunk> maybe it's really necessity as in if they can't share the one
15:47:56 <noonedeadpunk> *as in case
15:48:11 <noonedeadpunk> *in case
15:50:31 <noonedeadpunk> like trove is good example why you might want to have another rabbitmq cluster
15:50:45 <noonedeadpunk> maybe here it's the same.
15:54:51 <noonedeadpunk> #endmeeting