1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00

ec2_asg: adding explanation of replace_all_instances (#46694)

* adding explanation of replace_all_instances

How does "replace_all_instances" work? does it increase the number of instances by 1 in the Load balancer and it scales in a server and waits for it to complete its health check, OR   does it terminate a node a that causes an autoscale event to happen and then adds a new server?
+label: docsite_pr
This commit is contained in:
AndyG 2018-10-10 10:59:27 +01:00 committed by Will Thames
parent f34f75be45
commit fcef4fdb26

View file

@ -82,7 +82,10 @@ options:
- Desired number of instances in group, if unspecified then the current group value will be used. - Desired number of instances in group, if unspecified then the current group value will be used.
replace_all_instances: replace_all_instances:
description: description:
- In a rolling fashion, replace all instances with an old launch configuration with one from the current launch configuration. - In a rolling fashion, replace all instances that used the old launch configuration with one from the new launch configuration.
It increases the ASG size by C(replace_batch_size), waits for the new instances to be up and running.
After that, it terminates a batch of old instances, waits for the replacements, and repeats, until all old instances are replaced.
Once that's done the ASG size is reduced back to the expected size.
version_added: "1.8" version_added: "1.8"
default: 'no' default: 'no'
replace_batch_size: replace_batch_size: