14:00:10 <marios> #startmeeting tripleo
14:00:11 <openstack> Meeting started Tue Mar 16 14:00:10 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:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:14 <openstack> The meeting name has been set to 'tripleo'
14:00:22 <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:25 <marios> * Specs
14:00:27 <marios> * open discussion
14:00:30 <marios> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:00:52 <marios> hello tripleo who is with us today on this fine tuesday ;) o/
14:01:07 <mwhahaha> hi2u
14:01:08 <fultonj> o/
14:01:17 <tkajinam> o/
14:01:27 <fmount> o/
14:01:46 <marios> well fantastic then :) k we can get going and folks will catch up as usual ]
14:01:48 <marios> \o/
14:02:01 <marios> #topic review last meeting logs & action items
14:02:14 <marios> #link http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-03-02-14.00.html
14:02:25 <marios> anyone want to bring up something to do with the last meeting ^^^ ?
14:02:28 * marios checks the logs
14:02:54 <slagle_> o/
14:03:49 <marios> cant spot something (maybe the redfish driver thing https://review.opendev.org/c/openstack/tripleo-common/+/774787 but seems it is still in review/progress by the author)
14:03:57 <marios> k moving on if there is nothing else
14:04:13 <marios> #topic one off agenda items
14:04:15 <marios> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:04:27 <Tengu> ah, right. the meeting :).
14:04:34 <marios> please add things you want to raise there ^^^ we will go through them one at a time
14:04:57 <marios> from the CI team we have updates on the move to centos stream
14:04:57 <openstackgerrit> Sorin Sbârnea proposed openstack/tripleo-heat-templates master: Add support for py39  https://review.opendev.org/c/openstack/tripleo-heat-templates/+/780854
14:05:12 * Tengu pushed a link just in time
14:05:14 <marios> #link     http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021053.html [tripleo] Update: migrating master from CentOS-8 to CentOS-8-Stream - starting this Sunday (March 07)
14:05:37 <marios> latest is that ussuri and train are now also moved to use stream content. we will start using stream nodes too once         * https://review.opendev.org/c/openstack/tripleo-ci/+/780654
14:06:02 <marios> any questions/comments on this?
14:06:05 <marios> rlandy: fyi ^^^
14:06:08 <marios> weshay|ruck: ^^
14:06:43 <rlandy> marios: once https://review.opendev.org/c/openstack/tripleo-ci/+/780654 merges, we are done
14:06:45 <rlandy> with stream move
14:06:53 <marios> all i can say is fantastic job from the tripleo-ci team getting this done with basically no disruption
14:06:56 <marios> rlandy:++
14:06:59 <rlandy> all nodes and content will be stream
14:07:01 <openstackgerrit> Michele Baldessari proposed openstack/tripleo-heat-templates master: Remove extra bash process in frr container  https://review.opendev.org/c/openstack/tripleo-heat-templates/+/780430
14:07:14 <rlandy> and the dependency pipeline will be removed
14:07:30 <marios> rlandy: thank you
14:08:01 <marios> ok, moving on ... Tengu would you like to introduce your topic please go ahead (I see you added under Deployment)
14:08:56 <marios> #link Please merge https://review.opendev.org/c/openstack/tripleo-common/+/779438 :)
14:08:57 <Tengu> ah, yeah. just a request to merge this -^^
14:09:04 <marios> ack thanks Tengu
14:09:10 <Tengu> it's been sitting in CI for long enough :)
14:09:45 <marios> well it has 2 core +2 already
14:09:51 <marios> anyone object to me merging now?
14:10:06 <mwhahaha> already did
14:10:12 <marios> cool thanks mwhahaha
14:10:18 <Tengu> thanks mwhahaha :)
14:10:36 <marios> ok, then lets move on... storage team fultonj o/ around?
14:10:42 <slagle> you can merge your own stuff if it has 2 +2's
14:10:42 <fultonj> o/
14:10:48 <slagle> just sayin :)
14:10:51 <marios> slagle: yah i was going to say that ... but
14:11:00 <marios> slagle: it never hurts to ask first and see if someone else will
14:11:08 <marios> slagle: otherwise if you've done that then yeah totally agree
14:11:21 <openstackgerrit> Grzegorz Grasza proposed openstack/tripleo-heat-templates master: Add TLS support to services using memcached  https://review.opendev.org/c/openstack/tripleo-heat-templates/+/761612
14:11:29 <marios> fultonj: please go ahead
14:11:31 <fultonj> scenario001 standalone is now using cephadm with octopus
14:11:58 <fultonj> scenario004 standalone is using ceph-ansible but now with octopus
14:12:20 <fultonj> getting 004 to cephadm is blocked by an update to pacific
14:12:36 <fultonj> m3 is closing now
14:12:53 <fultonj> pacific is expected march 20-something
14:13:15 <fultonj> can we release wallaby with pacific (provided all tests pass)?
14:13:24 <fultonj> when it GAs
14:13:37 <fultonj> any concerns about switching the ceph verion that late?
14:13:44 <marios> fultonj: so obviously we have like 2/3 weeks beyond the 'normal' upstream dates
14:13:57 <marios> fultonj: meaning we have a _bit_ more time but ... it does seems like a big change to make
14:14:10 <marios> fultonj: so we're basically moving to octopus during wallaby then also to pacific
14:14:16 <fultonj> Pacific Dev container is already working
14:14:19 <fultonj> #link https://review.opendev.org/c/openstack/tripleo-heat-templates/+/778915
14:14:53 <fultonj> marios: my thought was to consider octopus a step but for wallaby to GA w/ pacific
14:15:17 <fmount> marios: yeah it's a matter of seeing the container working w/ all our scenarios (and the current merged code), then bump the container tag to pacific
14:15:26 <fmount> if everything works as expected of course
14:15:38 <marios> fultonj: so perhaps we can re-evaluate at the next meeting, by which time pacific will have been GAd
14:15:40 <fultonj> the plan is for pacific to be what goes out at wallaby GA (and octopus was just something we used during development now)
14:15:49 <fultonj> marios: ok, sounds good
14:15:55 <fmount> +1
14:16:07 <fultonj> sounds like it's still an option and not yet off the table
14:16:12 <marios> fmount: i see, i thought octopus was the target for W didn't realise we were working towards using Pacific release
14:16:28 <marios> fmount: i mean, "if it works OK" ... and if no-one else is shouting about it...
14:16:55 <marios> fmount: but in general we dont want to be making these big changes at this point in the cycle
14:17:06 <fultonj> right, that's why i asked ;)
14:17:59 <fmount> exactly yes, pacific is supposed to be the next "lts" after nautilus, that's the reason we want to bump to a stable, lts version as soon as possible
14:18:00 <fultonj> another question: is podman3 the default for wallaby?
14:18:13 <fultonj> seems to be, but i saw job failing w/ podman2 last night
14:18:19 <marios> don't know mwhahaha ^^^ ?
14:18:22 <fultonj> #link https://2a5c2cbd9d7adf274eb4-5d50e8ef24c23b6b3512cdd707b25e49.ssl.cf2.rackcdn.com/778915/4/check/tripleo-ci-centos-8-scenario001-standalone/ddb4195/logs/undercloud/home/zuul/standalone-ansible-txbbu4dw/cephadm/cephadm_command.log
14:18:35 <mwhahaha> i don't think we're consistently applying podman3, it should be the default soon (tm)
14:18:52 <fultonj> ok, so i'll asume we'll be on 3. thanks
14:19:48 <fultonj> regarding ceph integration and wallaby, we're still using ceph-ansible because cephadm/tripleo integration doesn't yet support rgw, mds, dashboard
14:20:01 <marios> fultonj: https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-8-scenario001-standalone&project=openstack%2Ftripleo-heat-templates hmmm... doesn't seem to be very consistent
14:20:01 <fultonj> though you can use cephadm to do full rbd cluster
14:20:43 <marios> fultonj: oh so we're keeping ceph-ansible for W?
14:21:00 <fultonj> yes, we're supporting both as we transition
14:21:20 <marios> fultonj: ack yeah i think you said at PTG that we'd make it default if it was ready sounds like it isn't yet
14:21:29 <fultonj> yues
14:21:30 <fultonj> yes
14:21:34 <fultonj> full removal of ceph-ansible in X
14:21:44 <fultonj> for W you can use cephadm if you only need rbd
14:21:53 <marios> but ceph-ansible is default for W then
14:21:53 <fultonj> or you can use ceph-ansible for rbd+
14:22:13 <fultonj> marios: you just pick the env file for the tool you want to use
14:22:16 <fultonj> we support both
14:22:25 <fultonj> -e cephadm.yaml or -e ceph-ansible.yaml
14:22:28 <marios> fultonj: ah so no 'default'
14:22:42 <fultonj> if people keep doing what they always did, they'll get ceph-ansible
14:22:50 <marios> fultonj: as in, by default there is no ceph in the overcloud-resource-registry.j2 you have to pick the env file
14:22:51 * fultonj writing docs
14:22:52 <marios> fultonj: gotcha
14:23:00 <fultonj> marios: yes, exactly right
14:24:06 <fultonj> we should move on, thanks for giving ceph this much time
14:24:13 <marios> fultonj: ack thanks for all the updates
14:24:15 <fultonj> that's the update and where we're landing for W
14:24:16 <fmount> thanks marios and fultonj
14:24:25 <marios> any comments or questions about the storage update from anyone ?
14:25:00 <marios> thank you fmount fultonj ... moving on
14:25:10 <marios> ok some community items
14:25:21 <marios> #link     [TripleO] Wallaby cycle highlights  http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020875.html     https://review.opendev.org/c/openstack/releases/+/778971
14:25:37 <marios> there was a request to provide some cycle highlights thanks to folks who helped out with that ^^^ fyi
14:25:44 <marios> hope i got all the important stuff there
14:26:04 <marios> i think we might be able to update if there is something you really want to change there but the deadline has now passed
14:26:27 <marios> #link     stable/rocky EOL merged  http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020912.html   https://review.opendev.org/c/openstack/releases/+/774244
14:26:30 <marios> \o/
14:26:34 <marios> finally merged that
14:26:42 <marios> please, no more patches to stable/rocky for tripleo things
14:26:55 <marios> if we have open patches they won't be able to delete the branch
14:27:17 <marios> #link     [TripleO] Xena PTG - registration and reserved time slots http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020953.html
14:27:45 <marios> ptg time again ! i reserved some time slots as explained there ^^^ i kept the same times we had in Wallaby ptg
14:27:53 <marios> please speak up if you want to discuss some different slots
14:28:12 <marios> it is hard to find good times that will suit everyone as we are all so distributed
14:28:30 <marios> the slots i chose are basically favoring US (early in the day ) and EU (mid-end of day)
14:28:56 <marios> #info remember to register for Xena PTG https://april2021-ptg.eventbrite.com/
14:29:03 <openstackgerrit> Grzegorz Grasza proposed openstack/tripleo-heat-templates master: Add TLS support to services using memcached  https://review.opendev.org/c/openstack/tripleo-heat-templates/+/761612
14:29:15 <marios> #info please avoid  self merge patches
14:29:34 <marios> i added this on request from someone in our community and in general we need to avoid this
14:29:56 <marios> i have only seen it very rarely but it is ofcourse a violation of openstack review guidelines
14:30:12 <marios> and really, we don't need to do that as in tripleo has enough people around during a given 24 hour cycle
14:30:25 <marios> any comments or questions about any of the community topics please?
14:30:45 <marios> so there was one more that i saw this morning actually i will add it now
14:31:17 <marios> #link      [all][tc][legal] Possible GPL violation in several places http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021063.html
14:31:29 <marios> #link https://bugs.launchpad.net/kolla-ansible/+bug/1918663
14:31:31 <openstack> Launchpad bug 1918663 in kolla-ansible "Possible licensing issue" [Undecided,New]
14:31:47 <marios> not sure we need to do anything here yet or if there is even an issue but we should watch the thread
14:32:10 <marios> tl;dr ansible gpl vs apache license
14:32:20 <fultonj> wow
14:33:05 <marios> fmount: yeah... but as i said it isn't clear yet if there is an issue and what we need to do about it if there is
14:33:18 <marios> err fultonj ^
14:33:41 <marios> k going to move on if there is nothing else on the one-off items
14:33:42 <fultonj> np
14:34:10 <marios> #topic Bugs and blueprints
14:34:10 <marios> #link https://bugs.launchpad.net/tripleo/
14:34:10 <marios> #link https://storyboard.openstack.org/#!/project/openstack/tripleo-ansible
14:34:10 <marios> #link  https://launchpad.net/tripleo/+milestone/wallaby-3
14:34:14 <marios> #link https://launchpad.net/tripleo/wallaby
14:34:15 <openstackgerrit> Merged openstack/tripleo-validations master: Trigger molecule tests when modifying CI scripts  https://review.opendev.org/c/openstack/tripleo-validations/+/778943
14:34:19 <openstackgerrit> Merged openstack/tripleo-validations master: Replace user with openssh_keypair  https://review.opendev.org/c/openstack/tripleo-validations/+/778899
14:34:27 <marios> anyone have bug related business they want to bring up?
14:34:52 <marios> haven't done any more bug clearing since last meeting... wallaby-3 still has a huge number of targetted bugs...
14:34:59 <marios> reminder please keep your bug status updated
14:35:26 <marios> hmmm i should probably move that to closed actually !
14:35:28 <marios> :)
14:35:42 <marios> wallaby-3 was last friday
14:35:49 * marios takes a note
14:36:36 <marios> bhagyashri|rover: soniya29|ruck: any big blocker bugs we can mention here?
14:36:51 <marios> anything blocking gates for example
14:36:57 <bhagyashri|rover> marios, nope
14:37:01 <marios> thank you bhagyashri|rover
14:37:02 <soniya29|ruck> marios, nope
14:37:06 <marios> thanks soniya29|ruck
14:37:11 <marios> fantastic then :D
14:37:17 <marios> moving on ...
14:37:25 <marios> #topic Project releases or stable backports
14:37:26 <marios> #info tripleo wallaby repos https://releases.openstack.org/teams/tripleo.html#wallaby
14:37:31 <marios> any release requests?
14:37:52 <marios> i'm thinking we need to make our releases more consistent so we don't lose track (i don't lose track ;) )
14:38:04 <marios> i was thinking of something like release all the branches once a month
14:38:06 <marios> any thoughts?
14:39:11 <marios> OK... moving on again ... ;)
14:39:16 <marios> #topic specs
14:39:16 <marios> #info https://review.opendev.org/q/project:openstack/tripleo-specs
14:39:17 <marios> #info https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/wallaby
14:39:32 <marios> so i think the only one right now is the tripleo-repos spec from ci team
14:39:35 * marios checks
14:40:27 <marios> #link https://review.opendev.org/q/project:openstack/tripleo-specs
14:40:46 <marios> #link https://review.opendev.org/c/openstack/tripleo-specs/+/772442 Add spec for single sourcing repo setup
14:40:59 <marios> that is still being worked on.... obviously we won't deliver for W
14:41:07 <marios> but we might still merge it in W for delivery in X
14:41:17 <marios> comments/thoughts or any other business for tripleo-specs?
14:42:09 <marios> slagle: o/ https://review.opendev.org/c/openstack/tripleo-specs/+/771229 what about that one
14:42:17 * marios hasn't noticed it before ;)
14:42:49 <marios> well commit message is pretty clear... so it sounds like another case of possibly land in W but deliver in X ?
14:43:38 <marios> OK... well lets close this out then if there is nothing else moving on to open discussion
14:43:45 <marios> #topic open discussion
14:43:48 <marios> Anything else that folks want to bring up to the meeting?
14:44:21 <marios> i'll have to start organising the PTG in the next week
14:44:27 <marios> as in harrassing people for topics ;)
14:44:36 <fultonj> :)
14:44:38 <marios> please start thinking about things you want to discuss there
14:44:45 <marios> 19th April
14:45:07 <marios> k going to close in a minute if no one speaks up :)
14:45:28 <marios> #info next meeting Tuesday 30th March
14:45:35 <openstackgerrit> Jiri Podivin proposed openstack/tripleo-validations master: Test folder structure rearranged.  https://review.opendev.org/c/openstack/tripleo-validations/+/778986
14:46:02 <marios> thank you everyone for bringing your updates and topics today
14:46:09 <marios> #endmeeting tripleo