Open Stack

Daniel Comnea <comnea.dani at gmail.com> wrote on 10/27/2014 07:16:32 AM:

> Yes i did but if you look at this example
> 
> 
https://github.com/openstack/heat-templates/blob/master/hot/autoscaling.yaml

> 

> the flow is simple:

> CPU alarm in Ceilometer triggers the "type: OS::Heat::ScalingPolicy"
> which then triggers the "type: OS::Heat::AutoScalingGroup"

Actually the ScalingPolicy does not "trigger" the ASG.  BTW, 
"ScalingPolicy" is mis-named; it is not a full policy, it is only an 
action (the condition part is missing --- as you noted, that is in the 
Ceilometer alarm).  The so-called ScalingPolicy does the action itself 
when triggered.  But it respects your configured min and max size.

What are you concerned about making your scaling group smaller than your 
configured minimum?  Just checking here that there is not a 
misunderstanding.

As Clint noted, there is a large-scale effort underway to make Heat 
maintain what it creates despite deletion of the underlying resources.

There is also a small-scale effort underway to make ASGs recover from 
members stopping proper functioning for whatever reason.  See 
https://review.openstack.org/#/c/127884/ for a proposed interface and 
initial implementation.

Regards,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141027/9fe5d9b8/attachment.html>