<div dir="ltr"><div><div><div><div>The current behavior is not flexible to customer, I see that we have a blueprint want to enhance this behavior.<br><br><a href="https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources">https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources</a><br><a href="https://wiki.openstack.org/wiki/Heat/AutoScaling">https://wiki.openstack.org/wiki/Heat/AutoScaling</a><br><br></div><div>In Use Case section, we have the following:<br>==========================================<br><h1><span class="" id="Use_Cases">Use Cases</span></h1>
<ol><li> Users want to use AutoScale without using Heat templates.</li><li> Users want to use AutoScale *with* Heat templates.</li><li> Users want to scale arbitrary resources, not just instances.</li><li> Users want their autoscaled resources to be associated with shared
resources such as load balancers, cluster managers, configuration
servers, and so on.</li><li> TODO: Administrators or automated processes want to add or remove
*specific* instances from a scaling group. (one node was compromised or
had some critical error?)</li><li> TODO: Users want to specify a general policy about which resources to delete when scaling down, either newest or oldest</li><li> TODO: A hook needs to be provided to allow completion or cancelling
of the auto scaling down of a resource. For example, a MongoDB shard
may need draining to other nodes before it can be safely deleted. Or
another example, replica's may need time to resync before another is
deleted. The check would ensure the resync is done.</li><li> <span style="color:rgb(0,0,255)"><b>TODO: Another hook should be provided to allow selection of node to
scale down. MongoDB example again, select the node with the least
amount of data that will need to migrate to other hosts.</b></span></li></ol></div>=======================================<br><br></div>Item 8 is enabling customer can customize the instance to scale down.<br></div></div><div><div><div><br>Thanks!<br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2014-11-26 18:30 GMT+08:00 Pavlo Shchelokovskyy <span dir="ltr"><<a href="mailto:pshchelokovskyy@mirantis.com" target="_blank">pshchelokovskyy@mirantis.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Maish,<div><br></div><div>by default they are deleted in in the same order they were created, FIFO style.</div><div><br></div><div>Best regards,</div><div>Pavlo Shchelokovskyy.</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Wed, Nov 26, 2014 at 12:24 PM, Maish Saidel-Keesing <span dir="ltr"><<a href="mailto:maishsk+openstack@maishsk.com" target="_blank">maishsk+openstack@maishsk.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In which order are machines terminated during a scale down action in an<br>
auto scaling group<br>
<br>
For example instance 1 & 2 were deployed in a stack. Instances 3 & 4<br>
were created as a result of load.<br>
<br>
When the load is reduced and the instances are scaled back down, which<br>
ones will be removed? And in which order?<br>
<br>
>From old to new (1->4) or new to old (4 -> 1) ?<br>
<br>
Thanks<br>
<span><font color="#888888"><br>
--<br>
Maish Saidel-Keesing<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr">Pavlo Shchelokovskyy<div>Software Engineer</div><div>Mirantis Inc</div><div><a href="http://www.mirantis.com" target="_blank">www.mirantis.com</a></div></div></div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>Thanks,<br><br></div>Jay<br></div></div>
</div>