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: settings for AMI and Custom boot script shall be linked and made into a list #4781

Closed
Tracked by #950
sanderegg opened this issue Sep 21, 2023 · 1 comment · Fixed by #5033
Closed
Tracked by #950
Assignees
Labels
a:autoscaling autoscaling service in simcore's stack

Comments

@sanderegg
Copy link
Member

sanderegg commented Sep 21, 2023

Use-case: in a computational cluster I send jobs of different kind.

On the computational cluster manager we have:

  • dask-scheduler
  • autoscaling

When sending jobs there, we will probably pass as resource the EC2 instance type that we want.

For each type, we might want:

  • a different AMI
  • a different boot script

One way of allowing this, is to make the autoscaling service there have a list of entries:
EC2_INSTANCES_ALLOWED_TYPES would become an object with:

EC2_INSTANCES_ALLOWED_TYPES
EC2_INSTANCES_ALLOWED_AMI_ID
EC2_INSTANCES_CUSTOM_BOOT_SCRIPTS

At least these ENVs should be linked together.

@sanderegg sanderegg transferred this issue from ITISFoundation/osparc-issues Sep 21, 2023
@sanderegg sanderegg self-assigned this Sep 21, 2023
@sanderegg sanderegg added the a:autoscaling autoscaling service in simcore's stack label Sep 21, 2023
@sanderegg sanderegg changed the title Autoscaling: settings for AMI and Custome bootscript shall be linked and made into a list Autoscaling: settings for AMI and Custom boot script shall be linked and made into a list Sep 21, 2023
@sanderegg
Copy link
Member Author

fixed by #5033

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

Successfully merging a pull request may close this issue.

1 participant