Bug 1710093

Summary:	[RFE] deploy extra ironic-conductor resources for an undercloud
Product:	Red Hat OpenStack	Reporter:	Alex Schultz <aschultz>
Component:	openstack-tripleo-heat-templates	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Aharon Canan <acanan>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	bdobreli, bfournie, ccopello, gregraka, jcoufal, mburns, mcornea, nlevinki, owalsh, racedoro
Target Milestone:	Upstream M2	Keywords:	FutureFeature, TechPreview, Triaged
Target Release:	16.0 (Train on RHEL 8.1)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.3.1-0.20191121202536.333e4f5.el8ost	Doc Type:	Technology Preview
Doc Text:	Red Hat OpenStack Platform director now enables you to deploy an additional node that can be used to add additional Bare Metal Provisioning conductor service resources for system provisioning during deployments.	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:50:14 UTC

Dependent on the framework created in Bug #1710089

Description of problem:

We would like to be able to deploy an instance of ironic-conductor on an undercloud minion that can be used to add additional ironic provisioning.

1) The undercloud minion configuration file should include a way to enable/disable ironic services
2) The ironic services on the minion 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 25 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