Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autoscaling: When one changes the AMI, then old stopped machines are not removed #7063

Open
Tracked by #1730
sanderegg opened this issue Jan 21, 2025 · 0 comments
Open
Tracked by #1730
Assignees
Labels
a:autoscaling autoscaling service in simcore's stack
Milestone

Comments

@sanderegg
Copy link
Member

When changing the configuration of autoscaling, the service automatically removes old EC2s if the pre-pulled images listing changes.
This mechanism does not work if one changes the AMI-IDs, then it will not update the warm buffers.

The same is true if one changes the custom boot scripts.

This usually results in "lost" warm buffers which could become costly.

@sanderegg sanderegg added the a:autoscaling autoscaling service in simcore's stack label Jan 21, 2025
@sanderegg sanderegg self-assigned this Jan 21, 2025
@sanderegg sanderegg added this to the Singularity milestone Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:autoscaling autoscaling service in simcore's stack
Projects
None yet
Development

No branches or pull requests

1 participant