Bug 989676 - [RFE] Custom "Provider" Resource Based on Nested Stack
[RFE] Custom "Provider" Resource Based on Nested Stack
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat (Show other bugs)
Unspecified Unspecified
high Severity high
: Upstream M3
: 4.0
Assigned To: Angus Salkeld
Zane Bitter
: FutureFeature, OtherQA
Depends On:
Blocks: RHOS40RFE
  Show dependency treegraph
Reported: 2013-07-29 13:29 EDT by Steven Hardy
Modified: 2013-12-19 19:16 EST (History)
10 users (show)

See Also:
Fixed In Version: openstack-heat-2013.2-0.8.b3.el6ost
Doc Type: Enhancement
Doc Text:
Feature: TemplateResources Reason: This feature enables a user to customize an existing Resource type or to create a new Resource type using a Template instead of a python plugin.
Story Points: ---
Clone Of:
Last Closed: 2013-12-19 19:16:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 33038 None None None Never
OpenStack gerrit 33241 None None None Never
OpenStack gerrit 36314 None None None Never
OpenStack gerrit 36323 None None None Never
OpenStack gerrit 36744 None None None Never
OpenStack gerrit 37106 None None None Never

  None (edit)
Comment 3 Steven Hardy 2013-09-18 08:41:10 EDT
Merged for h3, setting status to POST:

Comment 6 Angus Salkeld 2013-10-01 17:54:33 EDT

I have been on PTO for the last 3 weeks, I'll work at providing you some info in the next couple of days - just catching up on things.

Comment 7 Angus Salkeld 2013-10-22 21:30:48 EDT
High level info:
TemplateResource: (or provider) is a way to implement a resource using a template. 
Environment: is a way of defining the mapping between the template path/url and the resource type that you wish to call the resource.

You can override a system resource to customize the behavior or just create a new resource.

In order for us to have a template as a resource we convert the template parameters -> resource properties
outputs  -> resource attributes

so if you have a template:
    Type: String
    Type: ...
    Value: {Fn::GetAtt [something, ipaddress]}

and your env.yaml looks like:
    'OS::Mine::Thing': 'file://path/my_template.yaml'

and your top level_template.yaml looks like: 
    Type: 'OS::Mine::Thing'
      thingy: this_is_it
    Value: {Fn::GetAtt [newthing, thunk]}

Now create your stack:
heat stack-create new -f top_level_template.yaml -e env.yaml

You can do a lot with this feature as it makes heat very flexible, but the basics are shown above.

In the environment you can do other things like give existing resources new names and remove resources.

My testing of this feature involved making a couple of complex TemplateResources. But the simplest thing to do is to get any existing (working) template and use it as a TemplateResource.

So get the standard wordpress template and make a TemplateResource out of it.
Comment 8 Ami Jeain 2013-10-28 07:42:27 EDT
QANAK'ing due to QE capacity
Comment 13 errata-xmlrpc 2013-12-19 19:16:28 EST
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.


Note You need to log in before you can comment on or make changes to this bug.