15:00:16 #startmeeting openstack_ansible_meeting 15:00:16 Meeting started Tue Jan 30 15:00:16 2024 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'openstack_ansible_meeting' 15:00:24 #topic rollcall 15:00:26 o/ 15:00:36 hi! 15:04:11 Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_tempest master: Fix condition of excludelist file removal https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/907180 15:05:06 Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_tempest master: Fix condition of excludelist file removal https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/907180 15:05:08 #topic office hours 15:05:31 So we got couple of roles, like ironic and magnum due to this small nit ^ 15:05:41 *broken 15:05:46 *failing CI 15:05:55 * noonedeadpunk needs to get himself together 15:06:32 So I don't actually have many updates for the previous week 15:07:03 I'd eventually need to go through bug reports, as while most of them got some first reply, I'm not sure they all were properly triaged 15:07:12 Hopefully to have some time on Friday for that 15:07:35 I guess main 2 things that are in progress - openstack_resources and capi driver for magnum 15:07:58 I was not able to work on openstack_resources to implement suggested improvements for image management. 15:08:17 It also might be worth doing that in follow-up, not sure 15:09:57 for magnum capi I see some quite good progress, but apparently work is still in progress. Likely very close to the finish line 15:13:58 o/ hello 15:14:05 yes for cluster api it is very close 15:14:26 working in my AIO locally, just need to allow some more time for the cluster to create in the CI node i think 15:14:35 but there are a *ton* of dependant patches 15:14:56 some of which are good to go, some of which might need some discussion about the best approach 15:16:37 despite beeing super short on time this season, I'm ready to check through things when they're ready :) 15:16:53 I can recall there were some "volunteers" to test it out as well 15:18:16 yeah, that would be good 15:18:29 getting the AIO going is a little subtle though so i need to document that 15:19:22 some of the dependancies are generally moving stuff out of openstack-ansible repo into plugins collection 15:19:31 those are low-hanging fruit 15:21:25 actually moving to things to plugins, I was wondering what's up with https://review.opendev.org/q/topic:%22osa/collectify%22 ? 15:21:55 Like I was thinking it can be trivial to move all playbooks to plugins while get some benefits (potentially) 15:22:26 And that should not take dramatical time to move 15:22:45 yeah so some of those things actually are needed for the capi work 15:23:02 but i have done "whatever it takes" so interested in feedback 15:23:14 but I can recall not all of these worked like expected? 15:24:37 I just though of creating playbooks like openstack.osa.nova, openstack.osa.glance, etc and move content from integrated repo 15:24:40 right - particularly the one to set vars for source installs i think 15:24:55 while leaving just import_playbook: openstack.osa.glance for compatability 15:25:12 in the integrated 15:25:37 oh 15:25:49 another thing we might want to land "early" 15:26:02 I had couple of patches to the inventory script... 15:26:05 yeah 15:26:19 factoring out playbooks/common-* would be a really good start 15:27:03 so this might be useful for your capi hussle I assume: https://review.opendev.org/c/openstack/openstack-ansible/+/905433/2 15:27:20 as I can recall you said before about inconsistent hostnames/inventory names for containers 15:28:05 and this https://review.opendev.org/c/openstack/openstack-ansible/+/905438/2 should let us get rid of ANSIBLE_TRANSFORM_INVALID_GROUP_CHARS 15:28:33 basically making `-` and `_` interchangable 15:28:54 which I dunno if good or terribly bad idea frankly speaking 15:29:48 but that means we should be able to jsut rename groups in env.d to be only underscores, and hopefully not breaking anybody during upgrade.... 15:30:31 but that might be actually good to leave for the next cycle even.... 15:30:48 as I can see how playbooks might be using or relying on current group names 15:33:37 it does sound like we should try to land a bunch of this stuff as soon as possible 15:33:48 it’s all quite big and don’t want to leave it too late 15:34:38 yes capi would benefit from the underscores change 15:35:00 as there’s a bit of a break/fix cycle keeps happening with external collections there 15:38:28 With that we should still keep internal logic of converting hostnames for older deployments... 15:38:55 as basically only new containers will be generated this way - inventory won't (or should not) be altered otherwise 16:00:58 #endmeeting