14:00:11 <marios> #startmeeting tripleo
14:00:12 <openstack> Meeting started Tue Mar 30 14:00:11 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:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:15 <openstack> The meeting name has been set to 'tripleo'
14:00:21 <marios> #topic agenda
14:00:22 <marios> * Review last minutes & action items
14:00:22 <marios> * One off agenda items
14:00:22 <marios> * Bugs & Blueprints
14:00:22 <marios> * Projects releases or stable backports
14:00:24 <marios> * Specs
14:00:26 <marios> * open discussion
14:00:29 <marios> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:00:38 <marios> \o/ Hello TripleO good morning/afternoon/evening !
14:00:47 <fultonj> o/
14:00:49 <marios> who is with us today?
14:01:04 * marios thinks the EU daylight savings may throw folks off today
14:01:07 <cloudnull> o/
14:01:26 <marios> this meeting is an hour later than "normal" in EU today
14:01:34 <slagle> hi
14:02:03 <marios> ok well lets get going and we'll see if more join ;)
14:02:11 <marios> #topic review last meeting logs & action items
14:02:25 <marios> #link http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-03-16-14.00.html
14:02:33 <marios> anyone has something they want to bring up from last meet?
14:02:36 * marios checks logs
14:03:15 <fmount> o/
14:04:03 <marios> was wondering about that one [all][tc][legal] Possible GPL violation in several places http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021063.html
14:04:12 <marios> but i don't see anything further in the bug or the mail thread
14:04:16 * cloudnull reading
14:05:19 <marios> k if there is nothing else here lets go to the one-off items
14:05:57 <marios> #topic one off agenda items
14:06:03 <marios> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:06:28 <marios> for CI team heads up that we have started preparing for the wallaby release
14:06:40 <marios> #info     started preparing for wallaby branching - working on getting integration/component and upstream jobs & pipelines in place
14:07:09 <marios> the tripleo-ci-reduce effort is mostly done for now
14:07:18 <marios> #info mostly done @ https://review.opendev.org/q/topic:tripleo-ci-reduce
14:07:30 <marios> at least i can't think of somethign further to 'reduce' there :) doesn't mean there isn't lots ;)
14:07:51 <marios> now a related effort to remove the rocky stuffs after we EOL rocky
14:08:02 <marios> #link https://review.opendev.org/q/topic:tripleo-ci-reduce-rocky
14:08:12 <marios> anyone around from tripleo-ci wants to add anything further?
14:09:03 <marios> k moving on ...
14:09:16 <marios> storage folks fultonj o/ fmount gfidente
14:09:21 <marios> please go ahead when ready
14:09:23 <fultonj> Ceph Pacific should GA today or tomorrow (we're still on Octopus)
14:09:30 <fultonj> TripleO still seems to have podman 1.6 so this version of Ceph won't work until we have >= 2.0.2
14:09:38 <fultonj> we have patches to move to -pacific for both repos and containers
14:09:52 <fultonj> #link https://review.opendev.org/q/topic:%22cephadm_pacific%22+(status:open%20OR%20status:merged)
14:10:37 <marios> fultonj: tripleo wallaby release is gonna be just after PTG so say ~1 month from now
14:10:52 <fultonj> marios: ok
14:10:53 <marios> fultonj: hopefully the podman blocker will be resolved by then ?
14:10:59 <fultonj> so we'll be testing pacific soon and then we can decide when to move to it
14:11:33 <fultonj> marios: right, that's the question.
14:11:45 <fultonj> i assume wallaby will GA w/ podman 3
14:11:57 <fultonj> and we just haven't moved there yet in CI 001-standalone
14:12:25 <marios> weshay|ruck: mwhahaha: cloudnull: any idea re newer podman needed for ceph pacific? ^^
14:12:46 <mwhahaha> yes we need to support podman3
14:12:52 <marios> mwhahaha: ok great thanks :D
14:12:53 <mwhahaha> and even for train
14:12:56 <mwhahaha> so good luck
14:12:59 * mwhahaha runs away
14:12:59 <cloudnull> oh...
14:13:03 <gfidente> hurrah
14:13:05 <marios> mwhahaha: i assume you were joking :)
14:13:09 <mwhahaha> i am not
14:13:10 <cloudnull> nope
14:13:26 <cloudnull> c8-stream is shipping podman 3 by default
14:13:33 <marios> ... /me runs over mwhahaha running away
14:13:58 <fultonj> and i assume c8-stream is what's used in standalone001
14:13:59 * gfidente leaves the place
14:14:12 <mwhahaha> container-tools:3.0 is what will be supported for rhel8.4
14:14:14 <marios> mwhahaha: is there something worth discussing here i mean something the wider community can help with? reviews etc
14:14:24 <mwhahaha> no idea, i'm not working on it
14:14:27 <mwhahaha> just conveying info
14:14:27 <cloudnull> I think we're still setting up repos for podman to only provide 1.x/2.x?
14:14:29 <marios> mwhahaha: ack
14:14:42 <cloudnull> for ci that is
14:14:53 <marios> cloudnull: yeah container tools version i guess you mean
14:15:18 <mwhahaha> currently there is an issue that container-tools:3.0 is not available upstream
14:15:20 <mwhahaha> in stream
14:15:51 <fultonj> Does container-tools, not appstream provides podman in scenari001 standalone?
14:16:04 * fmount reading (late :/)
14:16:25 <cloudnull> marios++
14:16:38 <marios> cloudnull: ;) which bit
14:16:44 <ysandeep> i noticed some work in upstream deps line to move to container-tools:3.0 https://review.opendev.org/c/openstack/tripleo-quickstart/+/780941
14:16:47 <marios> fultonj: i believe so yes container tools gives up podman
14:17:07 * fultonj is trying to figure out why standalone-001 is still using the older podman
14:17:15 <chkumar|ruck> marios: what about switching to container-tools:rhel8 it will give 2.2.1-7.module_el8.3.0+699+d61d9c41
14:17:22 <chkumar|ruck> but it might contains bugs
14:17:23 <cloudnull> 09:14 <marios> cloudnull: yeah container tools version i guess you mean - yes
14:17:25 <chkumar|ruck> not sure
14:17:51 <marios> chkumar|ruck: i guess we could try it, but it doesn't sound like a blocker.i mean worst case we can GA wallaby with octopus
14:18:04 <marios> and then just bring pacific in X and backport if possible fultonj ? i think that was your plan right
14:18:07 <marios> was/is
14:18:26 <fultonj> marios: yes, i can do that
14:18:27 <marios> chkumar|ruck: my point is we can try it if the ceph team REALLY don't want to GA with octopus
14:18:34 <fultonj> but regardless of ceph...
14:18:41 <fultonj> is wallaby is supposed to go out w/ podman3?
14:18:44 <fmount> marios: we can yes, and we can backport it when container-tools:3.0 is available
14:18:58 <marios> fmount: right ...
14:19:04 <fultonj> is wallaby supposed to go out w/ podman3?
14:19:07 <marios> fultonj: yes right
14:19:21 <marios> fultonj: you're right so really one way or another we will do it i guess ;)
14:19:48 <fultonj> i guess the answer yes, but we're blocked by not having container-tools:3.0 upstream
14:19:49 <fmount> fultonj: good question, but at some point we need to align X and W (having podman 3) because otherwise backporting will be problematic
14:19:58 <marios> fultonj: i mean we will have to get podman 3 .. question is if it will give you enough time to merge https://review.opendev.org/q/topic:%22cephadm_pacific%22+(status:open%20OR%20status:merged) at the end
14:20:16 <marios> fultonj: like if the podman3 situation is sorted really late
14:20:21 <fultonj> c8stream appstream provides podman3 but i assume that's not sufficient and we need container tools
14:20:31 <marios> we can also delay the release a bit further i mean i think 6 months is the latest for trailing?
14:20:38 <marios> not saying we want to delay 6 months
14:20:49 <marios> but we can do for a couple/few weeks if we want/needed to
14:21:33 <fultonj> i wouldn't want to delay the relase for ceph pacific
14:21:54 <fultonj> we can do ocotpus, i was trying to figure out the podman version plan and fit ceph into it as best it could
14:22:42 <fmount> exactly, in any case bumping to -pacific will be not so hard, it's a matter of aligning repos and changing the containers
14:22:51 <fmount> but I'm not planning any change to the existing code
14:22:55 <fmount> from tripleo point of view
14:23:17 <marios> fultonj: ok, so let's just keep revisiting it. sounds like you folks are prepared either way with https://review.opendev.org/q/topic:cephadm_pacific
14:23:27 <fultonj> yeah, we're prepared
14:23:27 <fmount> yeah
14:23:29 <fmount> :D
14:23:40 <marios> we can see where we're at in 2 weeks again and also PTG after that we can have a bigger discussion about this
14:23:54 <fmount> +1 thanks marios works for me
14:24:30 <marios> ok anything further from storage please or anyone has any further comments about any of that?
14:24:46 <fultonj> not me
14:24:58 <fmount> not from me, thanks marios
14:25:17 <marios> k thanks fultonj fmount gfidente let's move on
14:25:27 <marios> couple community topics
14:25:37 <marios> #info     http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021201.html [tripleo] Nominate David J. Peacock (dpeacock) for Validation Framework Core
14:25:43 <marios> congrats David \o/
14:25:52 <marios> thanks for your work
14:25:54 <marios> dpeacock: ^^
14:26:17 <marios> there was a side discussion there about creating a validations subgroup in gerrit.. gchamoul i have to revisit that
14:26:32 <marios> #info     http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021180.html [tripleo] launchpad wallaby-3 milestone closed use wallaby-rc1
14:26:51 <marios> use wallaby-rc1 for launchpad bugs ^^^
14:27:02 <marios> #info     http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021313.html [TripleO] Xena PTG is coming 19 April
14:27:19 <marios> thank you everyone for adding your topics at https://etherpad.opendev.org/p/tripleo-xena-topics
14:27:40 <marios> beginning of next week we can start to organise those into some schedule
14:27:52 <marios> #info     register @ https://april2021-ptg.eventbrite.com/
14:28:08 <marios> any comments or questions about any of those?
14:29:01 <marios> k let's move on then
14:29:06 <marios> #topic Bugs and blueprints
14:29:06 <marios> #link https://bugs.launchpad.net/tripleo/
14:29:06 <marios> #link https://storyboard.openstack.org/#!/project/openstack/tripleo-ansible
14:29:13 <marios> #link  https://launchpad.net/tripleo/+milestone/wallaby-rc1
14:29:20 <marios> #link https://launchpad.net/tripleo/wallaby
14:29:55 <weshay|ruck> marios, chkumar|ruck containers-tools 3.0 will be available soonish for c8-stream, I would assume we can leave train pinned to 2.0
14:29:56 <marios> any bugs related business ? chkumar|ruck zbr|rover i know you folks are having a pretty tough week... any gate blockers we need to hilight?
14:30:27 <marios> weshay|ruck: thanks... from what mwhahaha we may need it on train too
14:30:38 <marios> what mwhahaha *said*
14:31:11 <marios> k then usual reminder to please keep your bug status updated especially moving things fix-released when done
14:31:24 <weshay|ruck> marios, I don't think so
14:31:28 <marios> moving on if there are no other bugs topics
14:31:30 <chkumar|ruck> marios: upstream is in good shape, we had some bumps in past due to https://bugs.launchpad.net/tripleo/+bug/1921679 in integration line, but all good now so far.
14:31:31 <openstack> Launchpad bug 1921679 in tripleo "openstack: 'undercloud install' is not an openstack command. See 'openstack --help'." [Critical,Triaged]
14:31:43 <marios> thank you chkumar|ruck
14:32:09 <weshay|ruck> we'll see results here first http://dashboard-ci.tripleo.org/d/jwDYSidGz/rpm-dependency-pipeline?orgId=1
14:32:28 <chkumar|ruck> just a request, if you see any gate failure, please add the reason in the code review and then recheck
14:32:46 <marios> chkumar|ruck: ack thanks folks please ^^^
14:33:22 <marios> weshay|ruck: yes i forgot we have a podman dependency line !
14:33:29 <weshay|ruck> heh..
14:33:48 <weshay|ruck> marios is getting old :)
14:33:55 <marios> k lets move onto next topic in agenda
14:34:01 <marios> weshay|ruck: i need holidays can you ask my boss?
14:34:09 <marios> #topic Project releases or stable backports
14:34:11 <marios> #info tripleo wallaby repos https://releases.openstack.org/teams/tripleo.html#wallaby
14:34:32 <marios> any release related business/comments/requests?
14:35:11 <marios> during wallaby cycle i was making releases in kind of a haphazard fashion... so decided i want to do better this time :) I am going to try and make a release 1/month for each branch
14:35:17 <marios> comments/questions?
14:35:32 <marios> i started with wallaby yesterday and will try and do ussuri today/train tomorrow etc until end of week
14:35:40 <marios> and then aim for end of each month ish
14:35:46 * marios famous last words
14:35:50 <marios> is this thing logged?
14:35:51 <marios> :D
14:36:13 <marios> k if there is nothing else moving on ...
14:36:41 <marios> #topic specs
14:36:41 <marios> #info https://review.opendev.org/q/project:openstack/tripleo-specs
14:36:43 <marios> #info https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/wallaby
14:37:13 <marios> i guess nothing to discuss here ... but probably time to start thinking about the xena specs together with the ptg topics
14:37:27 <marios> anyone wants to hilight something about specs?
14:38:04 <marios> ok then
14:38:09 <marios> #topic open discussion
14:38:10 <marios> Anything else that folks want to bring up to the meeting?
14:38:50 <marios> next meeting on Tuesday 13th April
14:39:43 <marios> thanks cloudnull fultonj fmount cloudnull chkumar|ruck weshay|ruck ysandeep for participating today \o/
14:39:52 <marios> have a good day bai
14:40:00 <marios> #endmeeting tripleo