In which order are machines terminated during a scale down action in an
auto scaling group
For example instance 1 2 were deployed in a stack. Instances 3 4
were created as a result of load.
When the load is reduced and the instances are scaled back down, which
ones will be removed? And in
Maish,
by default they are deleted in in the same order they were created, FIFO
style.
Best regards,
Pavlo Shchelokovskyy.
On Wed, Nov 26, 2014 at 12:24 PM, Maish Saidel-Keesing
maishsk+openst...@maishsk.com wrote:
In which order are machines terminated during a scale down action in an
auto
The current behavior is not flexible to customer, I see that we have a
blueprint want to enhance this behavior.
https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources
https://wiki.openstack.org/wiki/Heat/AutoScaling
In Use Case section, we have the following:
On 26/11/2014 14:50, Jay Lau wrote:
The current behavior is not flexible to customer, I see that we have
a blueprint want to enhance this behavior.
https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources
https://wiki.openstack.org/wiki/Heat/AutoScaling
In Use Case section,
Thanks Pavlo.
Is there any reason why FIFO was chosen?
Maish
On 26/11/2014 12:30, Pavlo Shchelokovskyy wrote:
Maish,
by default they are deleted in in the same order they were created,
FIFO style.
Best regards,
Pavlo Shchelokovskyy.
On Wed, Nov 26, 2014 at 12:24 PM, Maish Saidel-Keesing
On 26/11/14 09:13, Maish Saidel-Keesing wrote:
Thanks Pavlo.
Is there any reason why FIFO was chosen?
I believe that this was the original termination policy on AWS, and that
was the reason we chose it. It was used on AWS because if you deleted an
instance that was just created you would be
