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

[FEATURE] Install slurm utilities in NFS area so all machines can see it, no need to recompile for every machine. #233

Closed
gwolski opened this issue May 15, 2024 · 3 comments
Assignees

Comments

@gwolski
Copy link

gwolski commented May 15, 2024

I haven't studied the following completely by reviewing the code, so apologies in advance if it exists.

When I run the ansible playbook to install on my workstation machines so they can all submit to the HeadNode, slurm is being recompiled and installed locally every time.

Is there a way for me to just install the utilities on an NFS mounted area, say an NFS mounted /usr/local/slurm area, and then just reference that? Same for the config files that might be used to tell slurm where/who the HeadNode is?

Or is there some reason for this requirement?

@cartalla
Copy link
Contributor

Let me test this, but it should be storing the compiled binaries on the Slurm head node's NFS export so that all instances can see it.
So, it should only need to be compiled once per OS distribution and architecture.

Let me test and make sure that it is detecting that it has already been done.

@cartalla cartalla self-assigned this May 17, 2024
@gwolski
Copy link
Author

gwolski commented May 17, 2024

As noted, I haven't dug into this, but I do see that the slurm commands are on the mounted head_node..pcluster:/opt/slurm

I have only installed on one "user workstation" so it might be ok and doing the right thing.

@cartalla
Copy link
Contributor

The slurm binaries are only compiles on the submitter if they haven't previously been compiled for the OS and architecture of the submitter. They are compiled locally and then installed at /opt/slurm/ClusterName/config/os/... which is on the cluster's head node.

If you run the configuration script again it will run the ansible playbook, but it won't recompile the binaries because they already exist.

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