15:00:22 #startmeeting openstack_ansible_meeting 15:00:22 Meeting started Tue Feb 6 15:00:22 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:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 The meeting name has been set to 'openstack_ansible_meeting' 15:00:27 #topic rollcall 15:00:28 o/ 15:03:04 o/ hello 15:04:17 #topic office hours 15:04:39 So, I've started reviewing some patches from https://etherpad.opendev.org/p/osa-capi 15:04:55 and most things looks jsut nice except maybe some small nits 15:05:05 yeah, thankyou for taking a look 15:05:32 this needs some attention really https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/900527 15:05:38 i am not happy with that tbh 15:07:01 So... Maybe with just moving all playbooks to the plugins repo will eliminate a need for such role, as then we can continue using tasks include.... 15:07:10 ie local ones 15:07:18 as they will be local to playbooks 15:07:35 But ofc depends on what exactly you don't like ofc 15:07:45 perhaps though the pointt of that patch was i need to do the same thing in the ops repo collection 15:07:55 Also potentially I didn't get the problem you was solving good enough 15:07:55 so adjacent to playbook is unhelpful 15:08:42 o/ hi folks 15:08:45 ok, yeah. And the reason you don't like this patch is...? 15:08:55 \o/ 15:09:09 line 172 here https://review.opendev.org/c/openstack/openstack-ansible-ops/+/901450/12 15:09:48 sorry here https://review.opendev.org/c/openstack/openstack-ansible-ops/+/901450/12/mcapi_vexxhost/playbooks/k8s_install.yml#172 15:10:12 what i don't like is that the only way to make it "work" is to run it under roles: 15:10:17 and doing that with import_role? 15:10:23 ugh 15:10:29 ok, I don't like that either then 15:10:31 then the vars defined in defaults/main.yml just are not visible 15:10:33 right 15:10:37 how does ceph_ansible handles it? 15:10:41 so we need some other way to do this 15:11:00 probably with set_fact as a guess 15:11:22 https://github.com/ceph/ceph-ansible/tree/main/roles/ceph-defaults 15:11:27 no, not really I guess 15:11:45 oh i was thinking of https://github.com/ceph/ceph-ansible/tree/main/roles/ceph-facts/tasks 15:12:18 But I saw ceph-defaults being included/respected as well actually 15:12:35 interesting they are using import_role 15:12:52 the empty tasks file is maybe worth a try 15:12:55 we have them in roles :( https://opendev.org/openstack/openstack-ansible/src/branch/master/playbooks/ceph-install.yml#L93-L99 15:13:32 anyway - i really had some difficulty to make that work 15:13:42 but tbh i think that i am missing some obvious thing 15:14:55 Hm, I really don't understand how it works actually.... 15:15:32 as - should included vars in role work the same way then? 15:15:40 ie - being available outside of the role scope? 15:16:03 yeah, that worth to have a closer look obviously 15:16:11 right its a very good question 15:16:24 and one that obviously is important for ceph-ansible too 15:18:01 and potentially it depends on import vs include 15:18:29 i will write a test after the meeting 15:19:26 btw tempest fix https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/907886 seems to be working now - https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/907758 is happy 15:20:12 there're bunch of improvments that should be done for openstack_resources role, first of which to move service_setup role under it 15:20:35 I wonder if it's possible to do some kind of collection mapping magic to avoid patching all roles... 15:20:51 why do we need to do that btw? 15:21:04 well..... 15:21:40 amount of skipped tasks potentially have smth to do with that: https://opendev.org/openstack/openstack-ansible-plugins/src/branch/master/roles/openstack_resources/tasks/identity.yml#L16-L37 15:23:13 as role is included 2 times when we'd need to iterate properly over list of domains, since in service_setup context there's only 1 domain is possible 15:23:30 so for each domain, role is fully included for no good reason more or less 15:23:43 just to keep compatibility of formats.... 15:23:46 But dunno 15:23:52 maybe we don't need that at all 15:28:49 I was having some thought after looking through bunch of bugs lately. 15:29:21 If there's any will among you folks to do a bug triage/sorting day and spend it on closing/reviving bugs? 15:29:55 like it feels that 90% of them are not valid, but there're 10% that really worth paying attention to 15:30:40 and could be missed/still valid today (like https://bugs.launchpad.net/openstack-ansible/+bug/1896589) 15:30:57 as it's pretty embarassing to have that bug for 4 years.... 15:31:35 I know that it's not best time investment and might be hard to justify... 15:31:42 So no is also a good answer 15:33:05 Like if I'd sort bugs by update date - it's getting to 2020 after ~30-40 of them 15:37:20 * noonedeadpunk just found another valid one 15:37:44 would be good to have a bug squash at some point 15:38:00 maybe if it's just sorting out the ancient/invalid and leaving the actual ones 15:38:42 damiandabrowski: mgariepy wanna take part in that ^ :) 15:38:50 *it was a question 15:39:32 Like take couple of hours (or half of the day) for bug fighting day 15:39:58 and close what's not relevant / triage set priority for what is valid 15:46:36 that would be good - otherwise we just fight all the rubbish ones and waste time 15:55:39 yes sure when ? 15:59:26 Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_nova master: Always distribute qemu config file https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/908160 15:59:47 let's agree on some date/time:) 16:00:16 the closer to end of week - the calmer days in terms of meetings/distracting factors. 16:00:23 that's for me at least :D 16:00:55 I can send out a poll after the meeting actually 16:01:06 ok 16:01:26 awesome 16:01:31 #endmeeting