It's a resource, mostly like any other resource in Heat, that happens to represent another Heat stack.
Unlike any other resource in Heat, however, you can create an OS::Heat::Stack resource in a different region to where its parent stack is. That allows you to use Heat to manage multi-region deployments.
Regions can be considered separate clouds that have a common identity service. Apart from Keystone, which is shared, each region has its own service catalog with its own endpoints.
It's just another stack that is managed by your ("local") stack. See https://docs.openstack.org/developer/....
Thanks, I'm in a traineeship and I have the folowing problem: Suppose that i have resources in public cloud and i want to manage them with Heat which is intalled in the private Cloud, is that possible? I have searched about this problem and I didn't find something that could help me :/
I don't think you can do that with Heat. You need a separate cloud management platform. See also the architecture guide.
Heat only supports multi-region (i.e. shared Keystone). There was a proposal to support multi-cloud, but that hasn't gone ahead for lack of a secure way to store the authentication credentials for the other clouds. What you might be able to do is use a local Heat installation in "standalone" mode.
Asked: 2017-02-16 05:11:06 -0500
Seen: 66 times
Last updated: Feb 16 '17
