This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
cluster:217 [2022/06/21 13:38] hmeij07 [Slurm #2] |
cluster:217 [2022/06/24 13:53] (current) hmeij07 [Slurm #3] |
||
---|---|---|---|
Line 59: | Line 59: | ||
==== Slurm #1 ==== | ==== Slurm #1 ==== | ||
- | First thought was to install OHPC v1.3 CentOS7 slurmd client on the node, then join that to OHPC v2.4 slurmctld. To do that first '' | + | First Idea: |
* http:// | * http:// | ||
Line 114: | Line 114: | ||
==== Slurm #2 ==== | ==== Slurm #2 ==== | ||
- | I downloaded | + | Second Idea: download |
< | < | ||
Line 152: | Line 152: | ||
==== Slurm #3 ==== | ==== Slurm #3 ==== | ||
- | Just a mental note. There is a warning on Slurm web page re the older versions archives page | + | There is a warning on Slurm web page re the older versions archives page |
* https:// | * https:// | ||
- | Due to a security vulnerability (CVE-2022-29500), | + | "Due to a security vulnerability (CVE-2022-29500), |
- | Once we're fully deployed I may go to latest Slurm version, run on different ports with maybe newer munge version (although that should not matter, why does this scheduler even need munge? | + | Third Idea: once we're fully deployed I may go to latest Slurm version, run on different ports with maybe newer munge version (although that should not matter, why does this scheduler even need munge?) |
+ | Run Slurm outside of openhpc via local compile in ''/ | ||
+ | Decided to go this route v22.05.02 standalone version (with ohpc v1.3 or v2.4 munge packages). You need all three packages (munge, munge-libs and munge-devel) on host where you compile slurm (note: cottontail2 for rocky8.5, node n90 for centos7). Then just copy. | ||
+ | |||
+ | |||
+ | --- // | ||
==== Deploy ==== | ==== Deploy ==== | ||