🎨Autoscaling: Change max time to wait for EC2 readyness to 1 minute

[sanderegg]

What do these changes do?

Tests have shown that with the newest tooling we are now down from 3 minutes to <1 minutes to start an EC2 instance.

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[odeimaiz]

🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.3%. Comparing base (cafbf96) to head (3e92c91).
Report is 151 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #5739      +/-   ##
=========================================
- Coverage    84.5%   66.3%   -18.2%     
=========================================
  Files          10     607     +597     
  Lines         214   30204   +29990     
  Branches       25     204     +179     
=========================================
+ Hits          181   20052   +19871     
- Misses         23   10100   +10077     
- Partials       10      52      +42     

Flag	Coverage Δ
integrationtests	63.9% <ø> (?)
unittests	97.4% <100.0%> (+12.8%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...g/src/simcore_service_autoscaling/core/settings.py	97.9% <ø> (ø)
.../simcore_service_clusters_keeper/utils/clusters.py	97.5% <100.0%> (ø)

... and 614 files with indirect coverage changes

[pcrespov]

Amazing!
Perhaps you can add a not in the code about this change? or simply a link to this PR?

[sanderegg]

Amazing! Perhaps you can add a not in the code about this change? or simply a link to this PR?

@pcrespov what note? this is just an empirical value based on the usual time it takes to start an EC2 machine. I started with a conservative value, and now since the latest tooling is in place (using latest ubuntu instead of some obscure AMI-ID), the EC2 startup time was divided by 5