Integ Test Launches Bottlerocket Instances
webern opened this issue · comments
The integ test binary will need one or more Bottlerocket instances. It should:
- Take the TUF update repo metadata and targets URLs as input. (Maybe with defaults to the known prod URLS)
- Take the integ stack name or ARN as input.
- Take an AMI-ID
- Nice to have: Make the AMI-ID optional and use SSM parameters to figure out what the Latest - 1 version is, then get that AMI-ID automatically. (Skip if it seems complicated or painful.)
- Create appropriate user-data for the instance(s) and launch them.
- Poll to see if the instances join the integ stack ECS cluster.
Issue is not exactly solved as described. But, we have added few scripts in PR-69 which allows creating ECS cluster with Bottlerocket instances based on given AMI as input. There is no provision to change TUF repo URL, we are using the default URL. Update would happen from OS version of AMI to latest version available. In addtion to this, there are scripts to run updater on the cluster and cleanup the resources.
Make the AMI-ID optional and use SSM parameters to figure out what the Latest - 1 version is, then get that AMI-ID automatically. (Skip if it seems complicated or painful.)
Created an issue #74 to track it.