[heat][tacker] After Stack is Created, will it change nested stack Id?

Patil, Tushar Tushar.Patil at nttdata.com
Tue Feb 4 07:53:45 UTC 2020


Hi All,

In tacker project, we are using heat API to create stack.
Consider a case where we want to add OS::Heat::AutoScalingGroup in which there are two servers and the desired capacity is set to 2.
So internally heat will create two nested stacks and add following resources to it:-

child stack1
VDU1 - OS::Nova::Server
CP1 - OS::Neutron::Port
VDU2 - OS::Nova::Server
CP2- OS::Neutron::Port

child stack2
VDU1 - OS::Nova::Server
CP1 - OS::Neutron::Port
VDU2 - OS::Nova::Server
CP2- OS::Neutron::Port

Now, as part of tacker heal API, we want to heal VDU1 from child stack2. To do this, we will mark the status of the resources from "child stack2" as unhealthy and then update "child stack2" stack.

Since VDU1 resource is present in the two nested stacks, I want to keep the nested stack id information in tacker so that after the stack is updated, I can pull physical resource id of the resources from the nested child stack directly.

My question is after the stack is created for the first time, will it ever change the nested child stack id?

Thank you.

Regards,
tpatil
Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding.



More information about the openstack-discuss mailing list