15:01:58 <noonedeadpunk> #startmeeting openstack_ansible_meeting 15:01:59 <opendevmeet> Meeting started Tue Feb 8 15:01:58 2022 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:59 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:59 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting' 15:02:08 <noonedeadpunk> #topic rollcall 15:02:22 <noonedeadpunk> o/ 15:03:58 <damiandabrowski[m]> hey guys! sorry I wasn't very active lately, performing distribution upgrades in several regions during Q1 15:04:18 <damiandabrowski[m]> but i'll try to contribute as much as I can ;) things should get better in Q2 15:05:21 <noonedeadpunk> hopefully :) 15:05:30 <noonedeadpunk> so 15:05:37 <noonedeadpunk> #topic bug triage 15:06:00 <noonedeadpunk> #link https://bugs.launchpad.net/openstack-ansible/+bug/1960175 15:06:16 <noonedeadpunk> Obviously our doc is broken. 15:06:24 <noonedeadpunk> Question is - how we want to fix that? 15:06:51 <noonedeadpunk> We can just update the doc and say you should use like cluster_network: "{{ (container_networks['storage_address']['address'] ~ '/' ~ container_networks['storage_address']['netmask']) | ansible.netcommon.ipaddr('network/prefix') }}" 15:07:01 <noonedeadpunk> which is kind of... meh... 15:08:24 <noonedeadpunk> well, for monitor address we can jsut avoid monitor_address_block and replace with monitor_address 15:08:35 <jrosser> o/ hello 15:08:39 <noonedeadpunk> but for cluster_network we still need network 15:10:19 <damiandabrowski[m]> hmm, isn't this bug report about https://bugs.launchpad.net/openstack-ansible/+bug/1960175 15:10:20 <noonedeadpunk> so I was thinking if we should add cidr_networks as var somehow... or just add network to container_network stanza? 15:10:52 <noonedeadpunk> damiandabrowski[m]: yeah, I literally mentioned it 6 messages before :p 15:10:53 <damiandabrowski[m]> https://review.opendev.org/c/openstack/openstack-ansible/+/823796 15:10:56 <damiandabrowski[m]> sorry, wrong link 15:11:59 <jrosser> cidr_networks can get complex 15:12:04 <jrosser> look at the L3 pods example 15:12:16 <NeilHanlon> 👋hey folks, am around. and thank you again jrosser if i didn't say it yesterday for your time looking at rocky with me 15:12:39 <jrosser> NeilHanlon: hi there - i amended your patch with the ansible path btw 15:12:48 <NeilHanlon> oh, thank you :) 15:15:58 <jrosser> noonedeadpunk: does this help with finding the ceph ip? https://github.com/openstack/openstack-ansible/blob/master/playbooks/common-tasks/dynamic-address-fact.yml 15:16:36 <jrosser> though it wants the cidr though i guess, so not really 15:16:57 <noonedeadpunk> damiandabrowski[m]: huh 15:17:12 <noonedeadpunk> should we jsut backport it then and ask user to test out? 15:18:20 <jrosser> seems we should have backport that patch anyway? 15:19:53 <damiandabrowski[m]> yeah, i think we should 15:22:22 <noonedeadpunk> jrosser: yes, indeed we need cidr there... 15:22:37 <noonedeadpunk> and I agree that making cidr_networks will likely be tricky 15:23:34 <jrosser> i'm not sure i see value in bringing it into accessible vars really 15:23:44 <noonedeadpunk> but considering we have cidr_networks in docs that makes me think there was there one day 15:24:01 <noonedeadpunk> but agree. we have container networks defined there 15:24:10 <noonedeadpunk> so maybe jsut try to add cidr as an element? 15:24:21 <jrosser> yes, or maybe the ceph user_variables example was just always wrong 15:24:49 <noonedeadpunk> I can't reject such possibility :) 15:25:21 <jrosser> this also ignores that i think the ceph AIO networks are really all scrambled up too 15:25:59 <noonedeadpunk> oh yes, storage network just not used in aio 15:26:18 <noonedeadpunk> but that's different topic :) 15:26:21 <jrosser> indeed 15:26:32 <noonedeadpunk> (we should fix it yeah) 15:26:36 <jrosser> next bug? :) 15:26:53 <noonedeadpunk> I don't think we have anything new 15:27:04 <noonedeadpunk> #topic office hours 15:27:46 <noonedeadpunk> So there's already a PTG schedule for April available 15:28:46 <noonedeadpunk> #link https://ethercalc.openstack.org/7yxdas7suqnd 15:29:03 <noonedeadpunk> I took kind of responsibility to fill same time slots as for previous PTG 15:29:33 <noonedeadpunk> would be great if you could check it and provide some feedback if that is fine or we should re-arrange and do proper voting 15:30:18 <noonedeadpunk> So 2H slots 15-17 UTC on Tuesday and Wednesday 15:30:32 <damiandabrowski[m]> it's ok for me 15:30:45 <noonedeadpunk> (april 5 and april 6) 15:32:06 <jrosser> yes ok for me 15:32:07 <noonedeadpunk> we almost done with centos-8 removal 15:32:34 <noonedeadpunk> and there big work done with Rocky?:) 15:33:29 <jrosser> i think that NeilHanlon patch is very very close for metal deploys 15:33:55 <jrosser> and i think that the selinux trouble and probably also the lxc python lib problems will go away with it now using the system python on the targets 15:34:32 <noonedeadpunk> sounds good enough 15:34:47 <jrosser> really we wait on the dib patch to merge and getting nodes available 15:35:25 <noonedeadpunk> regarding ubuntu 22.04 support. I think I'd try to release without it if we will be ready with other things 15:35:28 <jrosser> and i think also we have to clean up these zuul job repos as that has causes confusion 15:35:35 <noonedeadpunk> oh yes 15:36:15 <noonedeadpunk> I;m not sure what it will take to land all keyston-related system scope and project tokens stuff 15:36:36 <noonedeadpunk> Or we'd rather delay intentionally to get ubuntu 22.04? 15:37:18 <noonedeadpunk> probably it's topic for ptg though as there will be more details around by this date (like dib and ci images) 15:38:23 <jrosser> whats the release date? 15:38:47 <noonedeadpunk> March 30 15:38:54 <noonedeadpunk> +2 month iirc 15:39:00 <noonedeadpunk> to technically we can fit 15:39:58 <noonedeadpunk> btw... Have I missed how Z will be named ?:) As just realized I have no idea what's the name it will have... 15:40:14 <jrosser> 22.04 is released April 21, 2022 though? so it's not in this cycle? 15:41:34 <noonedeadpunk> well, it's not. but I'd say all depedns on how much we want it:) and when CI images will appear.. If that will with some beta in March and we will be able to start working on it before release... 15:41:59 <noonedeadpunk> it's doable I guess 15:42:04 <jrosser> for ubuntu usually one or two days hacking gets most of it sorted unless there is a major problem 15:42:32 <noonedeadpunk> But yes, historically we were holding ubuntu lts to autumn 15:46:57 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible master: Remove unwanted repositories installed with the zuul configure-mirrors role https://review.opendev.org/c/openstack/openstack-ansible/+/828267 15:47:13 <jrosser> ^ zuul runs older ansible - doh 15:50:27 <jrosser> also i an pretty much done on the ssh keypairs stuff 15:51:01 <noonedeadpunk> I will review this shortly 15:51:15 <jrosser> though somehow i've constructed the patches / depends-on all backwards and it won't pass 15:51:18 <noonedeadpunk> I did quick look through and things look pretty much good 15:51:57 <jrosser> i think it was a mistake to try to bring all the role patches as depends-on the main one to openstack-ansible 15:52:30 <noonedeadpunk> at least openstack-ansible should depends on plugins? 15:53:25 <noonedeadpunk> ah yes. I mean - nova/keystone should depend on integrated repo 15:53:40 <noonedeadpunk> and repo 15:53:49 <noonedeadpunk> and integrated only depend on plugins 15:54:08 <jrosser> correct, that would work fine and would be mergeable 15:55:15 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible master: Create ssh certificate authority https://review.opendev.org/c/openstack/openstack-ansible/+/825292 15:55:42 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-repo_server master: Use ssh_keypairs role to generate keys for repo sync https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/827100 15:56:00 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_nova master: Use ssh_keypairs role to generate cold migration ssh keys https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/825306 15:56:07 <noonedeadpunk> and regarding plugins CI - I haven't looked into it - ENOTIME 15:56:17 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_keystone master: Use ssh_keypairs role to generate fernet sync ssh keys https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/827090 15:57:02 <jrosser> i only looked a little at molecule and saw it was pretty docker centric which is tedious for the docker rate limits 15:57:19 <noonedeadpunk> yep 15:57:37 <noonedeadpunk> and with nodepool we don't even need this 16:01:06 <noonedeadpunk> #endmeeting