Differences

This shows you the differences between two versions of the page.

--- cluster:217 [2022/06/21 13:03] – [Slurm #2] hmeij07
+++ cluster:217 [2022/06/24 13:53] (current) – [Slurm #3] hmeij07
@@ Line 59: / Line 59: @@
 ==== 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 ''yum install'' the ohpc-release from this location
+First Idea:  install OHPC v1.3 CentOS7 slurmd client on the node, then join that to OHPC v2.4 slurmctld. To do that first ''yum install'' the ohpc-release from this location
   * http://repos.openhpc.community/ohpc-1.3/1.3.9/base/CentOS_7/x86_64/ohpc-release-1.3-1.el7.x86_64.rpm
@@ Line 114: / Line 114: @@
 ==== Slurm #2 ====
-I downloaded Slurm source the closest version just above ohpc v2.4 version. Next compile 20.11.9 slurm and see if it is accepted on ohpc v2.4 slurm 20.11.8
+Second Idea: download Slurm source the closest version just above ohpc v2.4 version. Next compile 20.11.9 slurm and see if it is accepted on ohpc v2.4 slurm 20.11.8 to register ....
 <code>
@@ Line 148: / Line 148: @@
 Do **NOT** mount ''/opt/intel'' and ''/opt/ohpc/pub'' from SMS, that's all Rocky8.5 stuff.
 ==== 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://www.schedmd.com/archives.php
-Due to a security vulnerability (CVE-2022-29500), all versions of Slurm prior to 21.08.8 or 20.11.9 are no longer available for download...so why is openhpc v2.4 running such an old slurm version?
+"Due to a security vulnerability (CVE-2022-29500), all versions of Slurm prior to 21.08.8 or 20.11.9 are no longer available for download"  ... so why is openhpc v2.4 running such an old slurm version?
+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 ''/usr/local/''. A standalone version, the most recent version.
-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?) and run Slurm outside of openhpc. A standalone version.
+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.
+ --- //[[hmeij@wesleyan.edu|Henk]] 2022/06/23 19:07//
 ==== Deploy ====