[openstack-dev] [Heat] rough draft of Heat autoscaling API
sbaker at redhat.com
Fri Nov 15 01:58:32 UTC 2013
On 11/15/2013 02:48 PM, Christopher Armstrong wrote:
> The thinking here was:
> - this makes the new config stuff easier to scale (config get applied
> per scaling stack)
> - you can potentially place notification resources in the scaling
> stack (think marconi message resource - on-create it sends a
> - no need for a launchconfig
> - you can place a LoadbalancerMember resource in the scaling stack
> that triggers the loadbalancer to add/remove it from the lb.
> I guess what I am saying is I'd expect an api to a nested stack.
> Well, what I'm thinking now is that instead of "resources" (a mapping
> of resources), just have "resource", which can be the template
> definition for a single resource. This would then allow the user to
> specify a Stack resource if they want to provide multiple resources.
> How does that sound?
As long as this stack can be specified by URL *or* as an inline template
I would be happy.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev