14:00:02 <marios> #startmeeting tripleo
14:00:03 <openstack> Meeting started Tue Jan 19 14:00:02 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:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:06 <openstack> The meeting name has been set to 'tripleo'
14:00:16 <marios> #topic agenda
14:00:16 <marios> * Review last minutes & action items
14:00:16 <marios> * One off agenda items
14:00:16 <marios> * Bugs & Blueprints
14:00:16 <marios> * Projects releases or stable backports
14:00:18 <marios> * Specs
14:00:21 <marios> * open discussion
14:00:23 <marios> Anyone can use the #link, #action and #info commands, not just the moderatorǃ
14:00:26 <marios> Hello folks, who is around today? o/
14:00:52 <marios> hello tripleo anyone here :)
14:01:02 <slagle> hi
14:01:14 <marios> o/
14:01:16 <fultonj> o/
14:01:21 <beagles> o/
14:01:39 <marios> so lets get going and folks can catch up we have a few things in the etherpad
14:01:49 <marios> #topic review last meeting logs & action items
14:02:01 <marios> #link http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-01-05-14.00.html
14:02:06 <fmount> o/
14:02:08 <marios> checking for any AI from last week ...
14:02:33 <gfidente> o/
14:02:38 <Tengu> «o/
14:02:49 <marios> couple of the community ones had AI (bump rocky eol thread and the pip resolver) but we can discuss after
14:03:03 <marios> anything else from last meeting someone wants to hilight before we move on?
14:03:31 <marios> k moving onto
14:03:32 <marios> #topic one off agenda items
14:03:32 <marios> #link https://etherpad.openstack.org/p/tripleo-meeting-items
14:03:47 <marios> so let's take them in order
14:03:52 <rlandy> o/
14:03:54 <marios> #info     [Tengu] conditionnally replacing cURL by a python script for the http healthcheck?
14:03:58 <marios> #link https://review.opendev.org/c/openstack/tripleo-common/+/771422
14:04:04 <marios> Tengu: please go ahead ^
14:04:08 <Tengu> ah :)
14:04:24 <Tengu> sooo yeah. the whole story here is: cURL doesn't support CIDR notation for the no_proxy env var.
14:04:50 <Tengu> this leads to errors on some (many...) corp deploys - the healthchecks are failing because they are trying to go through the proxy...
14:05:06 <Tengu> so after many thoughts and discussions, it appears we'll need to get around this once for all.
14:05:23 <Tengu> so I'm proposing a patch that will try to be smart: default to the standard, fast, tiny efficient "cURL" call
14:05:49 <Tengu> but if it founds a "no_proxy" or NO_PROXY (or a specific env key), it will switch to a "small" python script using python requests
14:06:04 <Tengu> that way..... we should hopefully solve that issue once for all, in a mostly elegant way.
14:06:25 <Tengu> I'd want to raise awareness about this need, and see if anyone has strong concerns or, better, a better idea :)
14:06:37 <Tengu> fact is: neither cURL nor wget supports CIDR notation in the no_proxy
14:06:55 <marios> Tengu: thanks, nicely explained in the commit message there too
14:06:59 <Tengu> python-requests does support it, apparently so does some golang lib... but I'd rather go for python here.
14:07:14 <Tengu> especially since python is installed in the containers - not golanf
14:08:06 <marios> so review request here for https://review.opendev.org/c/openstack/tripleo-common/+/771422
14:08:08 <Tengu> (note: the patch has some errors I'm working on right now, mostly cosmetics - hence the -w)
14:08:10 <marios> anything else on that one?
14:08:32 <Tengu> nope. just wanting to ensure ppl see this change, since it might influence a bit how healthchecks are working
14:08:32 <marios> k moving on
14:08:41 <marios> Tengu: thank you for bringing that
14:08:48 <Tengu> yw :)
14:08:51 <marios> #info ephemeral Heat work is ongoing and we have a tracking etherpad(s)
14:08:58 <marios> #link https://etherpad.opendev.org/p/tripleo-ephemeral-heat
14:09:02 <marios> #link https://etherpad.opendev.org/p/podman-generate-kube
14:09:06 <marios> #link https://etherpad.opendev.org/p/podman-generate-kube
14:09:17 <marios> (I think the meetbot doesn't pick it up if there are spaces) ^^
14:09:32 <marios> slagle: ^^ that yours ... want to say something about it or mainly review requests/info
14:09:40 <slagle> i just wanted to point out the above etherpads
14:09:45 * Tengu follows as well, since working on this as well.
14:09:59 <slagle> to raise awareness
14:10:16 <marios> slagle: great thanks
14:10:33 <marios> lets give it a sec anyone have any comments or anything else to hilight about this item
14:10:41 <slagle> spec is not yet merged, but we're going ahead as written
14:10:42 * marios looks at etherpads
14:10:51 <openstackgerrit> Francesco Pantano proposed openstack/tripleo-ansible master: WIP: Introduce tripleo_cephadm role  https://review.opendev.org/c/openstack/tripleo-ansible/+/770674
14:11:14 <marios> slagle: is the spec blocked on something i thought we were done there
14:11:21 <marios> slagle: i haven't checked for couple days though
14:11:29 <Tengu> mostly cosmetics I think at this point
14:11:59 <slagle> not blocked per se, a few last minute comments which have been addressed
14:12:15 <marios> slagle: k thank you
14:12:17 <slagle> bogdando: do you plan to re-review, or do you want your -1 to remain sticky?
14:13:11 <marios> k lets move on for now
14:13:15 <slagle> yea, i think his concern was addressed
14:13:24 <marios> thanks
14:13:32 <marios> #info tripleo ceph client spec is implemented and is default for scenario004
14:13:36 <marios> #info 004 ceph-ansible for server config but not client config
14:13:41 <marios> #info 001 is all ceph-ansible right now, but will move to new ceph-client and cephadm during this sprint
14:13:49 <marios> #link https://blueprints.launchpad.net/tripleo/+spec/tripleo-ceph-client
14:13:52 <marios> #link https://blueprints.launchpad.net/tripleo/+spec/tripleo-ceph-client
14:14:13 <fmount> marios: yeah so basically the first spec is done, we're actively working on the second one (cephadm integration)
14:14:20 <fultonj> +1
14:14:22 <fmount> deprecating ceph-ansible and moving to cephadm
14:14:27 <marios> fultonj: gfidente: fmount: o/ hi folks anything you want to hilight
14:14:36 <marios> fultonj: thanks
14:14:46 <marios> sorry fmount :) ^
14:14:55 <fultonj> i don't think so, just a status highlight
14:15:14 <fmount> marios: just to share our status, the goal is to reach something working by the end of this milestone
14:15:14 <fultonj> scenario001 will be on cephadm and off of ceph-ansible hopefully within 2 weeks
14:15:16 <fmount> right
14:15:22 <marios> fmount: fultonj: gfidente: k let me paste all the things here sec
14:15:29 <marios> #link https://blueprints.launchpad.net/tripleo/+spec/tripleo-ceph-client
14:15:35 <marios> #link https://review.opendev.org/q/topic:%22cephadm_integration%22
14:15:41 <marios> #info we aim to have scenario001 running without ceph-ansible during this sprint
14:15:46 <marios> #info older branches will continue to use nautilus/ceph-ansible
14:15:51 <marios> #info main branch for wallaby 001 will use ocotopus/cephadm (hopefully 004 too by end of W)
14:15:55 <marios> #info found and patched new bugs from new client
14:16:01 <marios> #link https://launchpad.net/bugs/1912109
14:16:03 <openstack> Launchpad bug 1912109 in tripleo "FATAL | tripleo client role ceph_external_multi_config is unfined" [High,In progress] - Assigned to John Fulton (jfulton-org)
14:16:09 <marios> #link https://launchpad.net/bugs/1912103
14:16:10 <openstack> Launchpad bug 1912103 in tripleo "permission error when linking tripleo-inventory in config-download ceph-ansible subdirecotry" [High,In progress] - Assigned to John Fulton (jfulton-org)
14:16:15 <marios> #link https://bugs.launchpad.net/tripleo/+bug/1912218
14:16:16 <openstack> Launchpad bug 1912218 in tripleo "tripleo-ansible roles/tripleo_ceph_client putting ctlplane IPs in mon_host instead of storage network IPs when using composable networks" [High,In progress] - Assigned to John Fulton (jfulton-org)
14:16:37 <marios> nice thank you folks, something more you want to add here. or anyone else has comments about it
14:16:43 <marios> fmount: fultonj: gfidente: ^
14:16:58 <fultonj> not me
14:17:03 <fmount> me neither
14:17:05 <gfidente> not me either thanks
14:17:16 <marios> k lets give it a sec there's a lot there
14:18:07 <marios> k lets move on then
14:18:21 <marios> #info Inventory re-factoring and support for inventory from neutron resources
14:18:26 <marios> #link https://review.opendev.org/c/openstack/tripleo-common/+/766109
14:18:34 <marios> #link https://review.opendev.org/c/openstack/tripleo-common/+/765902
14:18:49 <marios> hjensas: o/ around? is that yours i suspect ^
14:19:04 <marios> hjensas: something more you want to add or just review requests
14:19:42 <marios> k i think these are all from hjensas going to just paste them here and see if there are comments
14:19:53 <marios> #info A tool to convert Heat nic-config templates to Ansible J2 NIC config templates
14:20:01 <marios> #link https://review.opendev.org/c/openstack/tripleo-heat-templates/+/767466
14:20:10 <marios> #info A good part of the patches to manage network's and ports has been merged
14:20:20 <marios> #link https://review.opendev.org/q/topic:%22network-data-v2%22+(status:open%20OR%20status:merged)
14:20:55 <marios> so review requests and status here ^^^ seems like good progress on the ports v2 spec
14:21:04 <marios> anyone have something further to add to this topic
14:21:48 <marios> k moving on
14:21:56 <marios> #info ci & upgrades having an ongoing discussion around upgrade jobs & how to improve, what to remove etc
14:22:03 <marios> #link https://etherpad.opendev.org/p/tripleo-upgrade-testing-wallaby
14:22:20 <marios> so upgrades and ci teams have had a couple of meetings around this already and it is an ongoing discussion.
14:22:59 <marios> mainly socialising that for now we don't have clear answers yet. highly likely that at least some of the upstream upgrade jobs will be removed or at least changed
14:23:19 <marios> any comments about that? odyssey4me or anyone else from upgrades around want to add something more^^
14:23:59 <marios> k moving on
14:24:08 <marios> #info close to merging upgrades job related excess content-providers https://review.opendev.org/q/topic:reduce-content-providers
14:24:14 <marios> #info last patch in series  gives us the reduction - we'll see it in all the repos after https://review.opendev.org/c/openstack/tripleo-ci/+/769131 merges
14:24:21 <marios> #info last patch in series  gives us the reduction - we'll see it in all the repos after https://review.opendev.org/c/openstack/tripleo-ci/+/769131 merges
14:24:44 <marios> sry .. so this is just to say we're close on that, we were blocked by an ussuri and train bug
14:24:56 <marios> it came up this week as infra was complaining about all the extra content providers
14:25:03 <marios> so we are addressing it, should be done very soon now
14:25:39 <marios> k and couple of community items left on the etherpad... moving on
14:25:48 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019723.html [cinder][tripleo][release] Victoria Cycle-Trailing Release Deadline  Herve Beraud
14:26:12 <marios> so this one.. we hadn't released victoria for os-refresh-config/os-collect-config/tripleo-ipsec
14:26:37 <marios> this started a discussion, first around if anyone is even using these and would they care if we moved it to release-management: none
14:26:47 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019751.html  [tripleo] move os-refresh-config, os-collect-config, tripleo-ipsec to 'release-management': none  Marios Andreou
14:27:06 <marios> and then also possibly about moving the os-*-config under heat governance, assuming they are interested
14:27:17 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019777.html [heat][tripleo] os-apply-config os-refresh-config os-collect-config project governance  Marios Andreou
14:27:43 <marios> so, it seems that they aren't hugely interested (no reply so far) and that is fine. i guess the next step is to decide what we will do with them
14:27:49 <marios> any comments or thoughts about this topic?
14:28:00 <marios> we ended up making the victoria release for now anyway with
14:28:09 <marios> #link https://review.opendev.org/c/openstack/releases/+/769915
14:28:35 * odyssey4me is catching up on scrollback
14:28:35 <marios> we can consider moving them to independent too, as another option. i think this one had some support on the mailing list threads i pointed to above
14:29:27 <marios> OK, folks can reply on the ML if they have thoughts about those
14:29:38 <marios> moving onto next
14:30:01 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.html [TripleO] moving stable/rocky for tripleo repos to unmaintained (+ then EOL) OK?
14:30:04 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019860.html [TripleO] moving stable/rocky for tripleo repos to unmaintained (+ then EOL) OK?
14:30:11 <marios> sorry i keep pasting the space hence the duplicates
14:30:38 <marios> this one.. i asked the question ~10 december so as i said in the last meeting here, i bumped the thread in preparation for taking action here
14:31:09 <marios> i haven't had any response and in particular no objections to this
14:31:50 <marios> we may even go directly to EOL. there isn't an official mechanism for declaring it 'unmaintained' so that doesn't make sense as an option
14:32:21 <marios> if there are no other comments here then moving on, i will post the patch to make it EOL within the next couple weeks and send to the ML as usual
14:32:37 <marios> after that we plan to remove all the upstream CI for it
14:32:48 <marios> #info http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019839.html [release] Release countdown for week R-12 Jan 18 - Jan 22 Herve Beraud
14:32:54 <marios> #info wallaby-2 milestone is this week.  we should release or will be switched to https://releases.openstack.org/reference/release_models.html#cycle-with-rc
14:32:58 <marios> #info wallaby-2 milestone is this week.  we should release or will be switched to https://releases.openstack.org/reference/release_models.html#cycle-with-rc
14:33:19 <marios> this one... so apparently we should make a wallaby release for wallaby-2 which is this week
14:33:37 <marios> i don't know if it really makes sense for us to do that though as nothing is ready for release.
14:33:46 <artom> o/ Hello from nova-land folks. Have a question about using standalone in CI
14:33:50 <artom> And running tempest plugin tests
14:33:57 <marios> as written in that thread, if we don't we might be asked to move to the cycle-with-rc model instead
14:34:10 <marios> artom: o/ hey we are in our irc meeting now
14:34:23 <artom> Whoops :(
14:34:25 <marios> artom: we have an open topic slot in a bit though
14:34:27 <marios> artom: np :)
14:34:28 * artom apologises and waits
14:34:55 <marios> any comments on releasing for wallaby-2?
14:35:26 <bogdando> slagle: hi, yes, we can chat
14:35:41 <marios> imo it doesn't make sense, we'd be releasing just for 'the rules' but what we release isn't at all complete, perhaps there is no expectation for it to be though it is wallaby-2 so ... (and we are trailing release anyway )
14:36:20 <marios> ok, then moving on ...
14:36:25 <marios> folks are very quiet today :D
14:36:36 <marios> #topic Bugs and blueprints
14:36:43 <marios> #link https://bugs.launchpad.net/tripleo/
14:36:43 <marios> #link https://storyboard.openstack.org/#!/project/openstack/tripleo-ansible
14:36:45 <marios> #link  https://launchpad.net/tripleo/+milestone/wallaby-2
14:36:48 <marios> #link https://launchpad.net/tripleo/wallaby
14:37:08 <marios> anyone wants to hilight bugs or blueprints?
14:37:23 <marios> ruck or rover around anything you want to point to /any gate blockers etc right  now?
14:38:21 <marios> ok then moving on
14:38:27 <marios> #topic Project releases or stable backports
14:38:29 <marios> #info tripleo wallaby repos https://releases.openstack.org/teams/tripleo.html#wallaby
14:38:58 <marios> so as just mentioned... we have to decide whether to make a release for wallaby-2
14:39:28 <marios> unless i hear otherwise, i may just go ahead and make the release for the tripleo repos (if that is a requirement of us, per  http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019839.html
14:39:56 <marios> another thing to hilight here is that victoria release https://review.opendev.org/c/openstack/releases/+/769915 i mentioned earlier also
14:40:08 <marios> anything else on this topic, any release requests etc
14:40:26 <bogdando> slagle: it seems that the spec is pending for the update to address my comments?
14:40:48 <marios> bogdando: i'll bring it up again in a sec in the open topics bit sec
14:40:49 <slagle> bogdando: let's sync up post-meeting
14:40:56 <bogdando> ack
14:41:02 <marios> ha or even now cos... lets move on to
14:41:05 <marios> #topic specs
14:41:05 <marios> #info https://review.opendev.org/q/project:openstack/tripleo-specs
14:41:06 <marios> #info https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/wallaby
14:41:14 <marios> ok bogdando slagle want to chat here a bit?
14:41:53 <slagle> bogdando: oh, just the backup/restore comment?
14:41:55 <bogdando> I think unaddressed comments remaining for the DB backup/restore  feature and podman networking mode impact on UC minions feature
14:42:49 <bogdando> also couldnot quickly figure out what was the decision for adding a dependency work or keep it parallel
14:42:50 <slagle> i can say we do not intend to scale Heat with minions in this model
14:42:58 <slagle> does that work for you?
14:43:02 <bogdando> yes please
14:43:06 <slagle> ok
14:43:29 <bogdando> aside of that there may be changs needed to the minion deployment code
14:43:47 <bogdando> to not deploy heat for example
14:44:27 <marios> i think the only other one apart from ephemeral heat that we didn't merge yet is the frrouter one
14:44:30 <slagle> makes sense, i will add that
14:44:36 <marios> #link https://review.opendev.org/c/openstack/tripleo-specs/+/758249
14:44:39 <bogdando> thanks slagle
14:44:58 <marios> it has enough votes but there are some comments there dsneddon are you planning to update it ^^^ or should we merge
14:45:15 <marios> i think i will merge that this week if there are no more updates
14:45:21 <marios> thanks bogdando slagle
14:45:28 <marios> anything else about specs from anyone
14:45:57 <marios> #topic open discussion
14:46:00 <marios> Anything else that folks want to bring up to the meeting?
14:46:03 <openstackgerrit> Merged openstack/tripleo-operator-ansible master: add role to list available tripleo validations  https://review.opendev.org/c/openstack/tripleo-operator-ansible/+/755365
14:46:45 <marios> any comments /feedback on this meeting are very much appreciated
14:46:50 <marios> seems like it took us a while today
14:46:58 <marios> but perhaps that's cos we have them every 2 weeks
14:47:53 <marios> well OK. if there is nothing more then let's close it.
14:48:02 <marios> #info next meeting tuesday 02 Feb
14:48:20 <marios> thank you everyone for participating and bringing topics today
14:48:28 <marios> #endmeeting tripleo