We are working on a add-on feature utilizing heat life-cycle plugin and life cycle scheduler hints (https://review.openstack.org/#/c/96889/)
We are using a template as below:
heat_template_version: 2013-05-23
description: >
This is a very simple template that illustrates the basic features
resources:
instance:
type: OS::Heat::AutoScalingGroup
properties:
resource:
type: OS::Nova::Server
properties:
image: tmpl
flavor: xxxxx
min_size: 2
max_size: 10
scale_up_policy:
type: OS::Heat::ScalingPolicy
properties:
adjustment_type: change_in_capacity
auto_scaling_group_id: {get_resource: instance}
cooldown: 60
scaling_adjustment: 1
scale_down_policy:
type: OS::Heat::ScalingPolicy
properties:
adjustment_type: change_in_capacity
auto_scaling_group_id: {get_resource: instance}
cooldown: 60
scaling_adjustment: '-1'
We call 'path_in_stack()' in life cycle plugin when creating nested stack (OS::Nova::Server in the above case) to get the root stack name. The expected output should be [(None, u'x'), (u'instance', u'x-instance-fl76v2a7tvmm')], however, the actual output is [(None, u'x-instance-fl76v2a7tvmm')].
The root cause may come from the patch https://review.openstack.org/#/c/116336/38, which use rpc call to create nested stack, but does not pass the 'parent_resource' parameter. This parameter should be added when creating nested stack via rpc call, otherwise, the 'parent_resource' of nested stack will always be None
I'll fix, but it's not so simple.
1. we have "parent_resource" returned as a part of the resource details, IMHO this is wrong as it should be a part of the stack's details (error in the API)
2. even before the RPC change the api would have *always* returned None for this as it is not persisted in the DB.
3. the RPC create_stack needs a new revision to take the parent_
4. we need to have a new schema to add the parent_
5. we need to load that correctly