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" Now what i want is to be able to always maintain a min number of instances in my Group, if is min_size been reached than trigger HEAT to spun a new one to be min_size + n On Sat, Oct 25, 2014 at 5:23 PM, Qiming Teng <[email protected]> wrote: > On Sat, Oct 25, 2014 at 07:58:28AM +0100, Daniel Comnea wrote: > > HI all, > > > > > > Unfortunately i couldn't find any resource - blueprint/ document/ > examples/ > > presentations about my below use case, hence the question i'm raising now > > (if this is not the best place to ask, please let me know). > > > > > > Having a group of 5 instances, i'd like to always maintain a minimum of 2 > > instances by using the HEAT autoscaling feature and Ceilometer? > > Did you try set the 'min_size' property of your auto-scaling group? > > Qiming > > > I've seen the Wordpress autoscalling examples based on cpu_util metric > but > > my use case is more on the number of instances. > > > > > > Cheers, > > Dani > > > _______________________________________________ > > OpenStack-dev mailing list > > [email protected] > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
