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

Add Slurm autoscaling #18

Draft
wants to merge 175 commits into
base: refactor/review-helm
Choose a base branch
from
Draft

Add Slurm autoscaling #18

wants to merge 175 commits into from

Conversation

sjpb
Copy link
Collaborator

@sjpb sjpb commented Jul 25, 2023

Requires KUBECONFIG to be defined in the shell used to run helm. This is injected as a secret to use to create pods on demand.

Uses host network for slurmd pods. These pods have a hostPort defined (for slurmd) which means they don't get scheduled onto the same k-node.

Note there's no ResumeFailProgram defined; assuming the slurmd pod definition is ok the the most likely reason for "resume failure" from slurm's PoV is the pod pending beyond ResumeTimeout, due to e.g. not enough k-nodes. While the s-node does then show DOWN, if k-resources become available later the pod will launch, at which time the s-node changes from DOWN to IDLE (this has been tested). Note this is different from e.g. autoscale on openstack, where a failed VM launch due to cloud resources will not keep retrying and the s-node state needs to be reset to allow slurm to try to launch it again. So really leaving the s-node showing as DOWN accurately reflects the state of cloud resources here.

@sd109 sd109 changed the title Add autoscale Add Slurm autoscaling Aug 18, 2023
@sjpb
Copy link
Collaborator Author

sjpb commented Aug 18, 2023

NB: this CANNOT make use of #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants