14:00:00 <marios> #startmeeting tripleo
14:00:00 <opendevmeet> Meeting started Tue Jul 20 14:00:00 2021 UTC and is due to finish in 60 minutes.  The chair is marios. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:00 <opendevmeet> The meeting name has been set to 'tripleo'
14:00:09 <marios> #topic agenda
14:00:09 <marios> * Review last minutes & action items
14:00:09 <marios> * One off agenda items
14:00:09 <marios> * Bugs & Blueprints
14:00:09 <marios> * Projects releases or stable backports
14:00:11 <marios> * Specs
14:00:14 <marios> * open discussion
14:00:16 <marios> Anyone can use the #link, #action and #info commands, not just the moderator«É
14:00:24 <marios> hello o/ tripleo good morning afternoon evening
14:00:28 <marios> is anyone around today?
14:00:50 <marios> i know some folks are away, and there is a conflict with a call that everyone else is likely on right now
14:01:16 <tkajinam> o/
14:01:27 <odyssey4me> o/
14:01:38 <marios> we can make this a brief meeting, perhaps skip some of the agenda
14:01:42 <marios> moving on
14:01:54 <marios> #topic review last meeting logs & action items
14:01:56 <beagles> o/
14:02:05 <marios> #link https://meetings.opendev.org/meetings/tripleo/2021/tripleo.2021-07-06-14.00.html
14:02:16 <marios> anything to raise regarding last meeting? /me checks logs
14:02:37 <marios> ah yeah, last meeting was very quiet also ;)
14:03:07 <marios> moving on...
14:03:08 <marios> #topic one off agenda items
14:03:10 <marios> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:03:32 <beagles> there's another meeting otg that some others might be paying attention to atm fwiw
14:03:39 <marios> taking these in order, only have some community items there right now, feel free to add things
14:04:05 <marios> beagles: yeah thanks i mentioned it at the start, will try and get through it quickly since folks are busy.. regardless the logs will be there if folks want to catch up later
14:04:41 <marios> beagles: i am also on that call :)
14:04:50 <marios> #info PTG timeslot vote @ https://doodle.com/poll/mre6tghmbntbivdd & http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023623.html
14:04:56 <beagles> marios: whoops .. missed that in context switches sorry ;)
14:05:09 <marios> i started a poll to sanity check the time for the ptg meetup
14:05:15 <marios> beagles: np thanks for mentioning it ;)
14:05:27 <marios> we've done 1300-1700 UTC in the other virtual ptg
14:05:45 <marios> looks like that is still the preferred choice. I'll close the poll and book that timeslot
14:06:05 <marios> any comments on this?
14:06:47 <opendevreview> Danni Shi proposed openstack/diskimage-builder master: Add a keylime-agent element and a tpm-emulator element  https://review.opendev.org/c/openstack/diskimage-builder/+/789601
14:06:49 <odyssey4me> nope, sounds good
14:07:02 <marios> #info releases - wallaby @ (merged) https://review.opendev.org/c/openstack/releases/+/800812 - victoria @ https://review.opendev.org/c/openstack/releases/+/801353
14:07:05 <marios> thanks odyssey4me ;)
14:07:23 <marios> doing another round of releases... wallaby down and victoria in progress will move on as they merge
14:07:48 <marios> note if anyone is interested in learning more about how that process works please reach out we can do the next one together ;)
14:08:19 <marios> pausing a sec for any comments
14:08:55 <marios> next topic is stein/queens EOL:
14:09:35 <marios> i abandoned the open patches against S & Q (thanks tkajinam for your help)
14:09:44 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023537.html [TripleO] Abandoning all open stable/stein and stable/queens patches for EOL
14:09:55 <marios> #info queens merged @ https://review.opendev.org/c/openstack/releases/+/798924 ,  stein open@  https://review.opendev.org/c/openstack/releases/+/798925
14:10:08 <marios> so queens is now officially EOL, we are waiting for the stein patch to merge
14:10:17 <marios> any comments about this topic?
14:10:20 <opendevreview> Pranali Deore proposed openstack/tripleo-heat-templates master: Allow configuring secure RBAC in glance  https://review.opendev.org/c/openstack/tripleo-heat-templates/+/783623
14:10:39 <odyssey4me> None from me. Long live the Queen! ;)
14:10:54 <marios> odyssey4me: :D
14:11:06 <marios> final topic here
14:11:08 <beagles> no, thanks for that! I should've abandoned those patches long ago - affinity for clutter
14:11:20 <marios> ack beagles np
14:11:30 <marios> we all have some 3 year old patches open ;)
14:11:37 <beagles> :)
14:11:38 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023726.html  [tripleo] Changing TripleO's release model
14:11:57 <marios> me and weshay|ruck spoke about this again last week and we wanted to revisit ... i bumped the thread with ^^^
14:12:13 <marios> the idea was to summarize that discussion and re-focus on the decision
14:12:36 <marios> i am also trying to get a spec together so we can talk about some of the specifics in more detail
14:12:48 <odyssey4me> Honestly I thought the decision was already made. :)
14:12:53 <marios> for now, please check the thread and continue to raise any concerns/comments
14:13:21 <marios> odyssey4me: ack we just want to make sure we aren't missing something, especially the bit about how we will use tags for the stable/branch compatibility
14:13:53 <marios> odyssey4me: and we have to follow the 'normal' process where we allow for discussion etc so... yeah unless somethign changes we are working towards the same goal
14:13:54 <beagles> fwiw I'm all for it - I thought I had replied to the thread already tbh but will add my $0.02 CDN
14:14:13 <marios> thanks folks
14:14:17 <odyssey4me> It seems to me that tripleo itself should be considered its own entity. It deploys openstack, which is another entity. The two don't need to be married to the same release versions.
14:14:43 * beagles nods
14:14:47 <marios> odyssey4me: yeah but tripleo deploys openstack so someone will say, 'which version of tripleo can i use to deploy openstack xena'? e.g. if there is no tripleo stable/xena
14:15:10 <tkajinam> one problem is that each service deprecates and removes parameters in shorter cycle
14:15:12 <odyssey4me> Well, I think we can cover that with a spec, and perhaps some docs changes.
14:15:16 <tkajinam> if we extend tripleo's cycle
14:15:21 <marios> odyssey4me: our current plan is to say 'tripleo-heat-templates from git tag 15.1 to 15.99 and tripleo-ansible tags... etc
14:16:02 <odyssey4me> marios ok, so the tag provides a way to recreate a branch if need be based on what we know is a consistent release?
14:16:19 <beagles> tkajinam: puppet modules will continue tracking the traditional branching right? except maybe puppet-tripleo that is
14:16:37 <tkajinam> beagles, yes. there is no plan to change release cycles in puppet
14:16:40 <beagles> ack
14:16:51 <marios> odyssey4me: yeah... one thing that concerns me a bit/not 100% clear is how we will 'backport' things... like there is a bug that needs fixing for the 'xena' versions of our repos e.g. in tht. but we don't have a stable/xena
14:16:58 <tkajinam> and IMO we can't. because each module need to be consistent with each services
14:17:01 <marios> what do we backport to? (with the 'tags' solution i mean)
14:17:26 <tkajinam> there are no mechanisms to officially support multiple releases of services by a single branch of puppet. we do it for deprecation cycle but that is kept for only one cycle.
14:17:30 <odyssey4me> marios what sort of things would need backporting?
14:17:51 <marios> odyssey4me: bug fix i don't know something that breaks the deployment of xena
14:18:02 <marios> odyssey4me: ah i guess, "tripleo doesnt' support xena" (for example)
14:18:04 <marios> so end of story
14:18:30 <tkajinam> if we switch from branch to tag then we can't backport anything
14:18:50 <tkajinam> each distribution can create their own package and cherry pick patches to old version but I don't think ROD folks will do that by their own
14:18:54 <marios> tkajinam: yeah no backport for stable/branch since we don't support stable/branch (when we decide not to create that one)
14:18:58 <odyssey4me> yeah, in my view we should aim to disassociate tripleo's branch from the openstack it deploys... and we should potentially open the door for dep[loying independent versions of openstack services
14:19:01 <marios> tkajinam: that's what confused me
14:19:28 <marios> so hoping this and anything else details-wise can be brought up in the spec or at least in the comments on the spec
14:19:37 <marios> i will try and get somethign out asap at least before the next meeting
14:19:51 <marios> because as mentioned in the thread http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023726.html
14:20:00 <marios> there is concern about doing this in time for stabl/xena
14:20:11 <marios> moving on in a sec if there is nothing further here for now
14:21:06 <marios> i propose that we will skip the rest of the agenda since folks are out, unless there is something specific someone here wants me to cover?
14:21:16 <marios> will move to open discussion and then close
14:21:45 <marios> ok...
14:21:48 <marios> #topic open discussion
14:21:50 <marios> Anything else that folks want to bring up to the meeting?
14:22:03 <marios> thanks beagles odyssey4me tkajinam o/
14:22:13 <odyssey4me> nothing from me
14:22:21 <marios> #info next meeting Tue 03 August 2021 @ 1400 UTC
14:22:32 <marios> #endmeeting tripleo