15:00:34 #startmeeting openstack_ansible_meeting 15:00:34 Meeting started Tue Dec 14 15:00:34 2021 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:34 The meeting name has been set to 'openstack_ansible_meeting' 15:00:46 #topic office hours 15:00:55 o/ 15:00:57 hey! 15:01:08 o/ hello 15:02:30 tbh I don't have too much things to discuss:) 15:02:49 except maybe if it's worth doing rc2 just for gitreview files... 15:03:20 hey 15:03:23 I actually talked to releases team and from their POV we can just have stable tag based just on RC1 15:03:44 are we safe with apache log4j ? 15:03:59 openstack doesn't use java, so... 15:04:27 can't say so regarding ELK or graylog, but that's quite different stories 15:04:47 Oh, also I think we should finally EOL ocata https://review.opendev.org/c/openstack/openstack-ansible/+/795690 15:05:20 And I'm also thinking that time for pike and might be queens? 15:06:28 graylog have some fixes. 15:07:26 ah, and gerrit ofc 15:08:41 Once https://review.opendev.org/c/openstack/openstack-ansible/+/821476 land we should be able to land upcoming changes. jrosser has started with dropping CentOS 8, Debian 10 and Ubuntu bionic support 15:08:51 Which is really good and worthy cleanup 15:09:03 actually i wonder how many releases are we obligated to support? or it depend entirely on us? 15:09:44 Eventually we follow https://releases.openstack.org/ for maintained state 15:09:53 regarding EOL - it's up to projects 15:09:56 we need to have some sort of decision / "words in a release note" about what we do with centos-8 on stable branches 15:10:22 as i think the infra people are talking about removing the ci images soon 15:10:58 I'd say we just stop testing it there 15:12:06 and reno could be also like that "With CentOS 8 EOL we stop completing CI testing for this Operating System. It is highly recommended to upgrade to one of the supported systems" 15:12:09 ah, so IMO we may mark pike and queens EOL ;) 15:13:18 damiandabrowski[m]: I believe that Octavia have already EOLed even stein 15:13:35 they're kind of leaders for keeping minimal releases even in EM state 15:16:09 jrosser: mgariepy wdyt about eoling pike/queens? 15:16:33 i would be OK with that - we don't see anyone submitting fixes 15:17:09 i'm also ok with this. and if we do see some stuff that really need fixing we can always fix it.. 15:17:33 we won't be able to backport, but I doubt we will anyway 15:17:52 looking at review dashboard we have some fixes for Rocky that we can't merge for quite a while 15:18:44 mainly because tempest is broken... https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/782990 15:19:14 #agreed EOL Pike and Queens 15:20:31 oh, eventually with that I was also thinking that we should change landing page of our docs for stable branches 15:20:54 maybe it's the right time to announce how many releases we're going to support? just to make it official and predictable 15:20:59 and leave there only current release data 15:21:59 We _really_ support only releases that OpenStack considers as maintained 15:22:12 As for EM, it's more like security patching 15:23:04 So we jsut follow openstack state here https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases 15:23:28 as for number of releases in EM - that's good question. I won't them call supported though :D 15:23:43 its a good time to clean up - there are relatively few outstanding stable branch patches 15:24:39 I'd say we can probably carry 3 releases in EM for sure? 15:25:19 or actually 4 I guess now (as U is in EM now) 15:25:28 it's a bit harder as we're trailing 15:26:19 jrosser: the obvious problem is with https://review.opendev.org/c/openstack/openstack-ansible-os_almanach/+/658585 15:26:25 as we've retired repo 15:26:33 so we don't have access to abandon it... 15:26:43 * noonedeadpunk reaching infra-rrot 15:26:46 we can ask in #opendev to get those patches abandoned 15:26:47 *root 15:26:53 yep 15:27:21 Would be also great to clean-up master but well... 15:27:30 we have tons of leftovers there... 15:27:52 keeping 3-4 EM releases is fine to me 15:30:56 ok, great 15:31:01 will prepare patches then 15:37:58 eventually I hope that with left focal and debian 11 (and centos 8-stream) we will be able to have ansible-core 2.12.... 15:38:37 not sure if 8-stream does have libselinux for py38 but we can probably have some nasty workaround for it.... 15:38:53 there was a pip module i think? 15:39:14 https://pypi.org/project/selinux/ 15:39:55 well it doesn't look too promising tbh.... 15:40:21 unfortunatelly zbr is not around to ask... 15:47:46 Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821720 15:49:50 Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/wallaby: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821723 15:51:09 Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821720 15:51:30 Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/wallaby: [doc] Clean out project index page for stable branches https://review.opendev.org/c/openstack/openstack-ansible/+/821723 15:51:33 sorry, updated a bit 15:52:04 as we already have that format for R->V 15:52:16 only missed that for W and X 15:54:16 Dmitriy Rabotyagov proposed openstack/openstack-ansible master: [doc] Update stable releases support status https://review.opendev.org/c/openstack/openstack-ansible/+/821726 15:59:58 #endmeeting