Details
-
Story
-
Status: Complete
-
High
-
Resolution: Done
-
None
-
None
-
None
-
Ev 18.21
-
Unset
Description
Additional requirements:
- groups should be named
- instances of group should be created in different AWS regions
- there should be easy way to generate ssh config to access instances in pool
- there should be easy way to access all instances in group as a whole using Ansible
There are two major options how this can be implemented:
1. Tool that creates pool should outputs ssh config and ansible inventory file that could be used to access group instances without requiring access to AWS API.
2. Tool that creates pool just tags instances somehow, so Ansible dynamic or in-memory inventory could be used, which can be easier for further automation.
Attachments
Issue Links
- blocks
-
INDY-1632
As a dev/QA I need an easy way to give access to testing pool to other team members
-
- Complete
-
- relates to
-
INDY-1785
As a dev/QA I need to have a possibility to use spot instances for testing
-
- Complete
-
-
INDY-1788
As a dev/QA I need to be able to refer different groups in the same namespace using one inventory
-
- Complete
-
-
INDY-1786
As a dev/QA I need to have a possibility to scale AWS EC2 instances sizes
-
- New
-
-
INDY-1787
As a dev/QA I need to have a possibility to combine aws_manage with other roles in one playbook
-
- New
-
-
INDY-1789
As a dev/QA I need to be able to parametrize search criteria for AWS AMI
-
- New
-
-
INDY-1784 Remove security groups at tear-down phase for both tests and playbooks
-
- Complete
-
-
-
- New
-
-
-
- New
-
-
-
- New
-