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
Asg offhours fixes #3875
base: main
Are you sure you want to change the base?
Asg offhours fixes #3875
Conversation
gleework
commented
Apr 24, 2019
- EC2 instances have eligibility requirements before they can be stopped/started.
- When ASG suspends/resumes, it should only stop/start eligible instances.
Thanks for the pull request! Much appreciated, If you don't mind could you sign the CLA at the bottom of the README? Direct link here: https://docs.google.com/forms/d/e/1FAIpQLSfwtl1s6KmpLhCY6CjiY8nFZshDwf_wrmNYx1ahpsNFXXmHKw/viewform |
Glad to be able to contribute back in some small way! I think that I'm supposed to be covered by a Corporate CLA submitted by Gil Yehuda on 1/2/19. It should have covered me and some teammates from Oath (now Verizon Media). Would the Individual CLA be equivalent for me? |
we typically ask folks to do both, on the corp (if their doing as part of a corporate activity) and on the individual as teams/groups change membership. if you cover on the individual we're good to go. thanks! |
…e of ec2 resource manager.
is this something that would be better handled with the use of a launch-filter? ie are the asgs here homongenous or are they being patched with spot and ephemeral instances at runtime ? i'm concerned about the additional api calls here and the implicit filtering, better would be an explicit filter on launch-config or adding in a new instance filter. but thats on the basis that the asgs are mostly homogenous. The only common use tool i'm aware of that does a lot of live patching of instances into asgs is something like https://github.com/AutoSpotting/AutoSpotting.. in which case we should probably just avoid the asg, buts thats easily done via adding a filter for the auto spot tag. |
This is biting us now ... what code changes are required to get this merged? FWIW, when stopping instances and ASGs with spot, we get the following error:
So, ideally we'd be able to detect the difference between one-time spot instances and persistent ones and still stop persistent ones. |
Hello, we are also facing the issue described above. Can we help to get this merged ? |