Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1066230 - [RFE][heat]: Allow the Resource name to be overridden and paramaterized in ResourceGroups
Summary: [RFE][heat]: Allow the Resource name to be overridden and paramaterized in Re...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
Whiteboard: upstream_milestone_next upstream_stat...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-02-18 05:03 UTC by RHOS Integration
Modified: 2015-03-19 17:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2015-03-19 17:34:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description RHOS Integration 2014-02-18 05:03:41 UTC
Cloned from launchpad blueprint


In order to assist in the supporting of underlying resources spun up by Heat, giving resources created by a resource group human-readable names (including numbering) would be very helpful.

Example: in a HoT, a ResourceGroup is defined to spin up 6 compute instances (e.g. web servers that would sit behind a load balancer). In order to help customer support easily locate those instances in a list, naming them something like this would be helpful:

Allowing the resource name to be overridden in the template and defined with a parameter would allow this. In Python string formatting terms, this would be something like:

for number in range(0, 7):
  print "%s%02d%s" % ('web', number, '')

So, being able to achieve something similar in a template would be very helpful.

It would also be very helpful to be able to then refer to the resource by it's generated resource name elsewhere in the template.

Specification URL (additional information):


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