Bug 1334466

Summary:	[RFE] Add Support for Resource Chains
Product:	Red Hat OpenStack	Reporter:	Jaromir Coufal <jcoufal>
Component:	openstack-heat	Assignee:	Jay Dobies <jason.dobies>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	9.0 (Mitaka)	CC:	jjoyce, mburns, nlevinki, rhel-osp-director-maint, sbaker, shardy, srevivo
Target Milestone:	ga	Keywords:	FutureFeature, TestOnly, ZStream
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-heat-6.0.0-1.el7ost	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-24 12:53:55 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:
Bug Depends On:
Bug Blocks:	1362719

Description Jaromir Coufal 2016-05-09 16:53:48 UTC

The resource registry enables template extension and customization through the ability to map a particular template/implementation to a resource type name. TripleO uses this pattern extensively to provide integration points at various steps in the stack deployment that can be used to add 3rd party integrations, such as service and driver configuration.

The problem is, only one template can be specified for each of these hooks. This spec is attempting to alleviate that by introducing a new type that will aggregate one or more templates into a nested stack.

Blueprint: http://specs.openstack.org/openstack/heat-specs/specs/mitaka/resource-chains.html

Comment 7 errata-xmlrpc 2016-08-24 12:53:55 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://rhn.redhat.com/errata/RHEA-2016-1761.html