There has been discussion about improving performance time, AWS resource usage on CLI commands, and various AWS CLI/STAF failures by removing the instantiation of machines for test runs. Instead what would be used is a subset of static machines with elastic IPs to be used as available resources for running tests, say ten machines that are always up as reserved instances that then the runner would know about and use all the time for queued tests. This would remove security group calls for attachment, ec2 instantiation (improve windows test run time since the windows machines would already be up), various STAF commands could already be done, etc.
There has been discussion about improving performance time, AWS resource usage on CLI commands, and various AWS CLI/STAF failures by removing the instantiation of machines for test runs. Instead what would be used is a subset of static machines with elastic IPs to be used as available resources for running tests, say ten machines that are always up as reserved instances that then the runner would know about and use all the time for queued tests. This would remove security group calls for attachment, ec2 instantiation (improve windows test run time since the windows machines would already be up), various STAF commands could already be done, etc.