Stack Metadata

Registered by Steven Hardy on 2013-05-01

From: http://lists.openstack.org/pipermail/openstack-dev/2013-April/007989.html

Introduce the concept of _stack_ Metadata, and provide a way to access it in a template (pseudo-parameter?)

Blueprint information

Status:
Complete
Approver:
Steven Hardy
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
Liang Chen
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Liang Chen on 2013-06-23
Completed by
Liang Chen on 2013-07-08

Related branches

Sprints

Whiteboard

With further discussion on the mailing list:
http://lists.openstack.org/pipermail/openstack-dev/2013-June/010781.html

Parent resources' Metadata, DeletePolicy, and UpdatePolicy will be accessible to stack resource in a uniform way as below,

 {'Fn::ResourceFacade': 'Metadata'}
 {'Fn::ResourceFacade': 'DeletePolicy'}
 {'Fn::ResourceFacade': 'UpdatePolicy'}

*UPDATE*
The merits of using a pseudo-parameter were discussed on the mailing list here:
http://lists.openstack.org/pipermail/openstack-dev/2013-June/010012.html

with a proposal that we use a function along the lines of:

  {'Fn::ProvidedResource': 'Metadata'}

instead.

---

A provider template will need a way of accessing the following "attributes" (not to be confused with the attributes accessed through Fn::GetAtt) of its parent resource:

* Metadata
* DeletionPolicy
* UpdatePolicy

These should probably be passed to the provider template as parameters, with appropriate namespacing, e.g. OS::Heat::Metadata, OS::Heat::DeletionPolicy, OS::Heat::UpdatePolicy.

Gerrit topic: https://review.openstack.org/#q,topic:bp/stack-metadata,n,z

Addressed by: https://review.openstack.org/34139
    implement stack metadata

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.