Bug 2140098

Summary: Remove openstack-heat-agents from overcloud image
Product: Red Hat OpenStack Reporter: Jesse Pretorius <jpretori>
Component: openstack-tripleo-puppet-elementsAssignee: OSP Team <rhos-maint>
Status: CLOSED DEFERRED QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 18.0 (Zed)CC: bdobreli, hbrock, jschluet, jslagle, jstransk, mburns, ramishra, rhos-maint, sathlang, sbaker, tkajinam
Target Milestone: ---Keywords: Triaged
Target Release: ---Flags: ifrangs: needinfo? (rhos-maint)
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-06 08:29:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jesse Pretorius 2022-11-04 13:02:04 UTC
Description of problem: The openstack-heat-agents package installs a significant number of dependencies, none of which have been required by OSP/TripleO directly for some time (since stable/wallaby aka OSP 17.x at the very least).

Partner/Customer integrations could be using these. The preferred method of integration is to use Ansible instead.

As noted in https://review.opendev.org/c/openstack/tripleo-common/+/838633 (present in stable/zed aka OSP 18.0) there is no OSP-native requirement for the heat agents any more.

We should ideally deprecate the inclusion of this package in the overcloud base image in OSP 17.1 and remove it in OSP 18.0. 

We should also consider deprecating the interface in OSP 17.1 and stopping support for it in OSP 18.0.

To do this may require some changes to the partner integration documentation [a] and the example integration repository [b].

[a] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/partner_integration/index
[b] https://github.com/redhat-openstack/tripleo-example-integration

Comment 1 Takashi Kajinami 2022-11-05 03:34:28 UTC
AFAIK the heat-agent package is still required for the ExtraConfigPre/Post resources.
If we aim to remove the package then we should implement an anternative interface to
implement the same pre/post configuration hook.

Comment 3 Rabi Mishra 2022-11-07 08:02:40 UTC
I think before proposing to drop the package from overcloud image, As Takashi mentioned, we need to either replace/drop interface and provide a way for users to migrate.

Comment 4 Bogdan Dobrelya 2022-11-16 13:19:30 UTC
FTR, we need another bz for removing puppet from overcloud images, and moving it/modules to the corresponding components' base container images.