diff options
| author | Michael Mayer <mjmayer@ucdavis.edu> | 2018-05-24 11:29:20 -0700 |
|---|---|---|
| committer | Will Thames <will@thames.id.au> | 2018-06-06 20:51:50 +1000 |
| commit | fbcd6f8a65e40703408ddd483e5a7a8b4f40dc2c (patch) | |
| tree | e67e1fc3e4fe3de04105d02a56cda3a572945a18 /hacking | |
| parent | 8eb9cc3217573d1ae63299effe0214d693acdde1 (diff) | |
| download | ansible-fbcd6f8a65e40703408ddd483e5a7a8b4f40dc2c.tar.gz | |
Add Fargate support for ECS modules
Fargate instances do not require memory and cpu descriptors. EC2 instances
do require descriptions. https://botocore.readthedocs.io/en/latest/reference/services/ecs.html#ECS.Client.describe_task_definition
Fargate requires that cpu and memory be defined at task definition level.
EC2 launch requires them to be defined at the container level.
Fargate requires the use of awsvpc for the networking_mode. Also updated,
the documentation regarding where and when memory/cpu needs to the assigned.
The task_definition variable for the awspvc configuration colided with
the ecs_service for the bridge network. This would cause the test to fail.
Add testing for fargate
Add examples for fargate and ec2
Diffstat (limited to 'hacking')
0 files changed, 0 insertions, 0 deletions