Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1710092

Summary:	[RFE] deploy extra heat-engine resources for an undercloud
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	python-tripleoclient	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Aharon Canan <acanan>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	bdobreli, hbrock, jamsmith, jcoufal, jschluet, jslagle, mburns, mcornea, nlevinki, nwolf, pweeks
Target Milestone:	beta	Keywords:	FutureFeature, TechPreview, Triaged
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-12.3.1-0.20191115200343.315f6d4.el8ost	Doc Type:	Technology Preview
Doc Text:	Director now provides the ability to deploy an additional node that you can use to add additional heat-engine resources for deployment related actions.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-06 14:40:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1710089
Bug Blocks:	1771551

Description Alex Schultz 2019-05-14 20:48:09 UTC

Dependent on the framework created in Bug #1710089

Description of problem:

We would like to be able to deploy an instance of heat-engine on an undercloud minion that can be used to add additional heat processing capacity.

1) The undercloud minion configuration file should include a way to enable/disable heat-engine
2) The heat-engine should be configured to communicate with the services on the original seed undercloud.

Additional info:

https://blueprints.launchpad.net/tripleo/+spec/undercloud-minion
https://specs.openstack.org/openstack/tripleo-specs/specs/train/undercloud-minion.html

Comment 9 errata-xmlrpc 2020-02-06 14:40:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:0283