-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use official SchedMD debian RPMs to install Slurm #8
Conversation
Update config files to accommodate newer version of Slurm.
Update image to ghcr.io.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some general comments and questions.
frontend/munge.key
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we be pushing a key to the repository?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, yes. There is no way to generate it dynamically and distribute it, and it's only used for internal communication between Slurm daemons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
This PR updates the version of Slurm from 19.0.5 to 23.11.7 by switching from the unofficial ubuntu RPMs to officially supported RPMs from SchedMD. SchedMD provides detailed instructions for building official Debian RPMs that allow very new versions of Slurm to be installed and allow easy upgrades of Slurm. The update was a major change, and thus required updates to config files to accommodate the newer version of Slurm. Closes #9
One consequence of this update is that ubuntu 22.04 is now required. This is because the RPM builds of Slurm do not work for Ubuntu 20.04.
Additionally, this update required a complete overhaul of the CI workflow because the builds now take a significant amount of time and emulation mode for ARM is no longer feasible. So, the workflow now uses native ARM runners to build multi-platform images that are pushed to ghcr.io instead of dockerhub.