Yoink slurmhelpers
out of the Slurm snap
#3
NucciTheBoss
started this conversation in
Ideas
Replies: 3 comments
-
Yeah, that sounds like a good idea. The alternatives are a lot more portable overall, and switching to a more portable option will definitely make the snap a lot more robust. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@NucciTheBoss I like the idea of removing it from the snap and putting it into the charm and useing it for generic |
Beta Was this translation helpful? Give feedback.
0 replies
-
Seems like we're in agreement here so I will begin the yoinking process 🛠️ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As the title suggests, I want to drop
slurmhelpers
from the Slurm snap package. What originally started out as "hey this is pretty cool" has proved to be more trouble than it's worth. There's a couple good reasons to consider dropping it:slurmhelpers
is blocking our migration tocore24
which forces us to still rely on the rocm PPA we have set up for Jammy Jellyfish$SNAP_COMMON
. You can edit the slurm.conf file directly and those changes will not be reflected within the snaps configuration.Alternatives
We still need the
.env
file to help configure how the Slurm and MUNGE daemons within the Slurm snap package behave. For this we're using thedotenv
Python package. Tbh I would prefer if we just removed Python entirely, and replaced it with something else. Our options are:godotenv
package.Either way I think we should aim to remove slurmhelpers so it removes current and doesn't cause any future blockers. Would like to know your thoughts @jedel1043, @wolsen, and @jamesbeedy 🤔
Beta Was this translation helpful? Give feedback.
All reactions