15:01:43 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:01:43 <opendevmeet> Meeting started Tue Jan 21 15:01:43 2025 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:43 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:43 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:01:47 <noonedeadpunk> #topic rollcall
15:01:51 <noonedeadpunk> o/
15:02:11 <NeilHanlon> o/
15:02:27 <NeilHanlon> noonedeadpunk: sure thing re: those reviews
15:02:54 <NeilHanlon> NVM damiandabrowski did them :D
15:03:28 <noonedeadpunk> sorry just pinged couple of ppl to be sure :)
15:04:07 <NeilHanlon> hehe no worries
15:05:18 <noonedeadpunk> #topic office hours
15:06:43 <damiandabrowski> hi!
15:06:48 <noonedeadpunk> ok, so first of all, TC has merged the patch that confirms HTTP repo as recognized one by OpenStack: https://review.opendev.org/c/openstack/governance/+/935694
15:07:14 <jrosser> o/ hello
15:07:31 <noonedeadpunk> retirement of qdrouterd is still pending though:
15:07:33 <noonedeadpunk> #link https://review.opendev.org/c/openstack/governance/+/938193
15:07:55 <noonedeadpunk> from our side everything merged except manila
15:08:03 <noonedeadpunk> which is broken on ganesha setup
15:08:22 <noonedeadpunk> so potentially some love is needed there
15:10:06 <jrosser> we are going to get CI breakage when qdrouterd is retired
15:11:07 <jrosser> should we already start removing it from the stable branches?
15:13:25 <noonedeadpunk> doh, yes, we should....
15:13:40 <noonedeadpunk> very-very good point
15:15:11 <jrosser> this is just from requried-projects isnt it, nothing more than that
15:15:29 <noonedeadpunk> yes
15:16:10 <noonedeadpunk> though let's not backport to 2023.1this removal https://opendev.org/openstack/openstack-ansible-tests/src/branch/master/zuul.d/jobs.yaml#L69
15:16:35 <noonedeadpunk> as otherwise I'd had to update https://review.opendev.org/c/openstack/releases/+/938952 again, and it's long overdue
15:17:17 * noonedeadpunk thinks unmaintained policy is huge overcomplication
15:18:21 <jrosser> i am hoping that 2023.1 might be the first branch moved to unmaintaind that is not broken so badly we can't fix it
15:18:32 <noonedeadpunk> but also - once roles are switched to unmaintained - I'll propose shas update for integrated repo
15:18:51 <noonedeadpunk> I think Zed was okeyish?
15:18:58 <jrosser> ish
15:19:02 <noonedeadpunk> yeah
15:19:22 <jrosser> this sort of ish https://review.opendev.org/c/openstack/openstack-ansible/+/932921?tab=change-view-tab-header-zuul-results-summary
15:19:29 <noonedeadpunk> hopefully it's a marker of effort put into roles stability
15:20:22 <noonedeadpunk> hm
15:20:29 <noonedeadpunk> I wonder what went wrong there
15:21:01 <noonedeadpunk> as we don't do much in post_jobs
15:21:10 <jrosser> it is very sad that our branches that transition to unmaintained are basically wrecked
15:21:42 <noonedeadpunk> I guess it's matter of capacity to maintain them
15:22:24 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible stable/2024.2: Remove ansible-role-qdrouterd from zuul required-projects  https://review.opendev.org/c/openstack/openstack-ansible/+/939723
15:22:43 <jrosser> well as i've said a few times we basically kept things working for some pretty long time
15:23:12 <jrosser> but i put really a massive effort into trying to fix the transitioned unmaintained branches, at the expense of working on new stuff
15:23:18 <jrosser> and i pretty much failed on them all
15:23:42 <noonedeadpunk> yes, true
15:24:26 <noonedeadpunk> I frankly not sure what to suggest here. We can go EOL for these branches in 6 month after EOM
15:24:35 <noonedeadpunk> but it could also be un-ideal
15:25:15 <noonedeadpunk> so basically drop all to Zed right away
15:25:24 <jrosser> and the timing is so bad too
15:25:40 <jrosser> as we have a huge fight with the just-made-unmainted branch right in the middle of the current cycle
15:25:58 <jrosser> and distract from getting the new release sorted out in time
15:26:02 <jrosser> anyway, <rant>
15:26:29 <noonedeadpunk> so, we have a choice kinda. Previously we were very distracted as unmaintained timing was right during our preparation for the release
15:26:47 <jrosser> well like i say i am hopeful that 2023.1 will be much better
15:26:57 <noonedeadpunk> I got understanding that we are having trailing release, so we can go to unmaintained in 1 month after our release or so
15:27:06 <jrosser> there is handling for automatically handling both stable and unmaintained branch names in the scripts now
15:27:24 <noonedeadpunk> so basically that's the activity at the very beginning of "our" cycle
15:28:08 <jrosser> yeah this is true
15:28:33 <jrosser> perhaps we just need to be more strict about getting that transition done stright after our release
15:28:40 <noonedeadpunk> and usually that's the least loaded time
15:30:11 <noonedeadpunk> yeah, and that's pretty much on me
15:30:20 <noonedeadpunk> (and I'm failing with that from time to time)
15:32:00 <noonedeadpunk> but indeed - will try to be just more organized
15:33:33 <jrosser> so molecule and tests repo?
15:33:47 <jrosser> we had some good progress and some bugs there this week
15:33:58 <noonedeadpunk> yes. I think the only uncovered part is plugins, where tests repo runs
15:34:26 <noonedeadpunk> at least according to this: https://codesearch.openstack.org/?q=openstack-ansible-role-jobs&i=nope&literal=nope&files=&excludeFiles=&repos=
15:35:35 <noonedeadpunk> so given your work with LXC containers role - it should be doable now
15:36:03 <jrosser> yes - i have got a bit distracted from that this week
15:36:05 <opendevreview> Dmitriy Rabotyagov proposed openstack/openstack-ansible unmaintained/zed: [CI] Remove periodic jobs from unmaintained branch  https://review.opendev.org/c/openstack/openstack-ansible/+/932921
15:36:27 <jrosser> but i think that now everything should be in place to pretty quickly convert the old tests to molecule
15:36:37 <noonedeadpunk> I frankly just didn't have time as summoned to finalize an ovn-bgp-agent setup
15:37:00 * noonedeadpunk not very good in networking
15:37:45 <NeilHanlon> heh
15:37:51 <jrosser> i need to get back on with the lxc_container_create one
15:38:01 * jrosser also been distracted from that
15:38:38 <noonedeadpunk> but it seems we're 99% done with functional tests at this point (given the whole scope over years)
15:39:18 <jrosser> there is also adding coverage for the other things in the plugins repo
15:39:31 <noonedeadpunk> and not only there
15:39:53 <jrosser> which could mean we don't necessarily need to run the full suite of integrated repo tests if we make a good job of that
15:39:54 <noonedeadpunk> like rabbitmq and galera are also good candidates I guess
15:46:10 <noonedeadpunk> btw last week I also had a look into topic we've discussed long time ago - simplifying bootastrap process
15:46:20 <noonedeadpunk> or better say - moving complexity around :D
15:46:23 <noonedeadpunk> #link https://review.opendev.org/c/openstack/openstack-ansible/+/939151/
15:46:27 <jrosser> ah yes i did see that
15:46:45 <noonedeadpunk> I can't recall why I did set a WIP there though
15:47:39 <jrosser> is this OK for upgrades?
15:47:59 <noonedeadpunk> Part I liked more is the next patch, which replaces set_fact in loop with som jinja
15:48:19 <noonedeadpunk> a downside is being way less verbose
15:49:02 <noonedeadpunk> but user-facing stuff is way cleaner and readable, imo
15:49:24 <noonedeadpunk> yeah, it does work for upgrades now
15:49:43 <noonedeadpunk> that was a nasty part to do for upgrades: https://review.opendev.org/c/openstack/openstack-ansible/+/939151/21/scripts/gate-check-commit.sh
15:50:42 <noonedeadpunk> I'm really not sure I like it. But I can't come up with better thing to trigger role pull from zuul
15:50:57 <noonedeadpunk> once pre-task have finished and we're in gate-check-commit
15:50:58 <jrosser> so we don't actually test the user facing script?
15:51:19 <noonedeadpunk> we do with shastest only
15:51:24 <noonedeadpunk> https://zuul.opendev.org/t/openstack/build/9a806d6a192a424d816fe01288c15850
15:51:36 <noonedeadpunk> but it's same today
15:51:59 <noonedeadpunk> or well, we test a very specific unrealistic version of it
15:53:36 <jrosser> oh well actually we do use it
15:53:49 <jrosser> with a user-role / collection requirements setup by the pre- job
15:54:12 <noonedeadpunk> ah
15:54:21 <noonedeadpunk> yes, we prepare user-requirements, true
15:54:24 <opendevreview> Merged openstack/openstack-ansible-apt_package_pinning master: Use OSA_TEST_REQUIREMENTS_FILE for molecule job  https://review.opendev.org/c/openstack/openstack-ansible-apt_package_pinning/+/939299
15:54:29 <jrosser> i think thats what i'd missed
15:54:42 <jrosser> it's not that we duplicate the functionality into the zuul pre job
15:54:47 <noonedeadpunk> but it's still like... not what every user will do
15:54:53 <noonedeadpunk> no-no
15:54:54 <jrosser> it's more preparing the input for the user overrides
15:55:02 <noonedeadpunk> Ive jsut moved zuul-specific things there
15:55:14 <jrosser> yes that makes sense
15:55:18 <opendevreview> Merged openstack/ansible-role-systemd_service master: Use OSA_TEST_REQUIREMENTS_FILE for molecule job  https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/939292
15:55:32 * noonedeadpunk also having someobvious memory issues
15:55:46 <opendevreview> Merged openstack/ansible-config_template master: Use OSA_TEST_REQUIREMENTS_FILE for molecule job  https://review.opendev.org/c/openstack/ansible-config_template/+/939302
15:55:51 <jrosser> and it previously it could swap in the zuul repos sort of in-line
15:56:01 <noonedeadpunk> I kind of can recall adding some molecule jobs to the integrated repo....
15:56:46 <noonedeadpunk> I never pushed that?
15:57:02 <jrosser> it would be nice if that playbook kept a copy of the requirements files for the two branches in an upgrade
15:57:07 <noonedeadpunk> regarding test of user-role-requirements.....
15:57:46 <noonedeadpunk> so I'm not sure if it can use zuul stuff for N-1
15:57:59 <noonedeadpunk> or better say - I don't know how to do that
15:58:15 <opendevreview> Merged openstack/ansible-role-systemd_networkd master: Use OSA_TEST_REQUIREMENTS_FILE for molecule job  https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/939304
16:00:42 <noonedeadpunk> ok, I can't find the patch for testing user-role-requirements locally either
16:00:48 <noonedeadpunk> Maybe I dreamt of it...
16:00:50 <noonedeadpunk> anyway
16:00:54 <noonedeadpunk> #endmeeting