Monday, 2025-02-24

cardoeShould we look to define approximate EOL dates for the release list? https://releases.openstack.org/00:21
tkajinamI wonder what is the view from TC about heat being said can be replaced by modern and nice tools and is useless https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/C4QBCXLQTNT5IASEXU2HZB7T7SFUQUYY/#27AU4X2WJDJDAS5LGNCXPBUUDWE54B2N05:20
tkajinamif that's the agreement then I'll propose retiring the project seriously05:21
tkajinamand telling people to replace heat by anything new and better immediately :-)05:22
opendevreviewMerged openstack/election master: Tag value handling for governance repo with note  https://review.opendev.org/c/openstack/election/+/94250511:33
opendevreviewSlawek Kaplonski proposed openstack/governance master: Add TC/PTL results from 2025.2 election  https://review.opendev.org/c/openstack/governance/+/94250711:38
cardoetkajinam: so its used by other OpenStack components so that'll likely lead to its increased deployment usage. but it's not really wrong from a user perspective. opentofu is all around better.14:39
tkajinamcardoe, that's a good point, but as far as I know magnum, tacker and tripleo are known consumers of heat and total of these components does not really match the one of heat14:53
tkajinamusing a cross-cloud tool to manage resources in clouds sounds like a viable approach, though14:53
mnasiadkaMagnum is deprecating the Heat driver, so it’s going to disappear in a couple od cycles, maybe earlier14:58
mnasiadkaTripleO is retired, right?14:58
fungiyes, this is the approach taken by nodepool/zuul for example, workload state managed outside any particular cloud provider because it's orchestrating resources across many different providers14:58
mnasiadkaBut opentofu is not going to fix the autoscaling case, unless everybody runs their applications in Kubernetes nowadays14:59
cardoeI've called out to terraform/opentofu before to do autoscaling.15:00
mnasiadkaRight, but that’s a bit different than what you have with Heat today - I’m not against retiring Heat :)15:03
tkajinamif you have a tool to orchestrate resources across clouds then you may have a different tool to monitor workload across the cluster and implement autoscaling outside of the cloud (theoretically)15:07
JayFIronic is ready for https://review.opendev.org/c/openstack/governance/+/939278 to land, please :) 15:24
JayFTC is core for openstackdocstheme, yeah? https://review.opendev.org/c/openstack/openstackdocstheme/+/942525 fixes a search issue and needs another core review16:46
gouthamrJayF: tc isn't core, gtema is17:18
fungiwell, more specifically, openstackdocstheme is an oslo deliverable at the moment17:53
opendevreviewMerged openstack/governance master: Deprecate ironic-lib  https://review.opendev.org/c/openstack/governance/+/93927817:53
JayFack17:55
gouthamrtc-members: can i have a few more eyes on https://review.opendev.org/c/openstack/governance/+/941935 ?19:05
opendevreviewMerged openstack/openstack-manuals master: Deprecate ironic-lib  https://review.opendev.org/c/openstack/openstack-manuals/+/93928119:59
opendevreviewMerged openstack/governance master: Switch Ironic to Distributed Leadership  https://review.opendev.org/c/openstack/governance/+/94193520:32
spotz[m]I think there's still lots of folks using Heat21:41
spotz[m]I might be biased though I was the Heat system engineer at Rackspace though;)21:42

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!