[spike] mac life cycle

[adrianriobo]

Need to explore which would be the best option to handle hot refresh on mac machines.

The idea would be create custom AMIs:

• using [packer based] (https://aws.amazon.com/blogs/compute/building-amazon-machine-images-amis-for-ec2-mac-instances-with-packer/) still that would require spin from AMI to setup the key ?

• another approach would be create a cycle based on qenvs:

1. Create dedicated host
2. Create 12 machine 22. Store private key to access the machine 23. Once machine is healthy create snapshot / and AMI from it (link to private key and data for target type of dedicated host)
3. Same for OS 13
4. Same for OS 14

With previous set of AMIs for a type of dedicated host:

1 Create dedicated host

2. Create mac machine
3. Refresh mac machine #169 . This step would use one of previous AMIs once it is healhty it will change the key for a new generated key within the process

[adrianriobo]

The strategy has been tested through the AWS console and it is working so far, hint when create the AMI from the snapshot make sure the right ARCH is set

[adrianriobo]

Another hint , as AMIs would be created from a different machine when we use the root private key to connect to it we need to do not check the host -o StrictHostKeyChecking=no

[adrianriobo]

Time reduction for spin new instance goes from 1+ hour to 7 mins aprox