Skip to content
Snippets Groups Projects
Commit da8604a6 authored by Moe Jette's avatar Moe Jette
Browse files

Update documentation regarding authentication plugin. Recommend use of

munge plugin and give pointer to its web page.
parent 2aec4c70
Branches
No related tags found
No related merge requests found
......@@ -9,13 +9,13 @@
<meta http-equiv="keywords" content="Simple Linux Utility for Resource Management, SLURM, resource management,
Linux clusters, high-performance computing, Livermore Computing">
<meta name="LLNLRandR" content="UCRL-WEB-201790">
<meta name="LLNLRandRdate" content="12 January 2004">
<meta name="LLNLRandRdate" content="2 May 2004">
<meta name="distribution" content="global">
<meta name="description" content="Simple Linux Utility for Resource Management">
<meta name="copyright"
content="This document is copyrighted U.S.
Department of Energy under Contract W-7405-Eng-48">
<meta name="Author" content="Moe Jette">
<meta name="Author" content="Morris Jette">
<meta name="email" content="jette@llnl.gov">
<meta name="Classification"
content="DOE:DOE Web sites via organizational
......@@ -64,10 +64,11 @@ The major type must be &quot;auth.&quot; The minor type can be any recognizable
abbreviation for the type of authentication. We recommend, for example:</p>
<ul>
<li><b>none</b>&#151;A plugin that implements the API without providing any actual
authentication service.</li>
authentication service. This may be used for testing purposes, but is not suitable for
production use due to lack of effective security.</li>
<li><b>authd</b>&#151;Brett Chun's Linux authd.</li>
<li><b>munge</b>&#151;LLNL's munge protocol.</li>
<li><b>krb5</b>&#151;Kerberos 5</li>
<li><b>munge</b>&#151;LLNL's munge protocol (recommended plugin for production use).</li>
<li><b>krb5</b>&#151;Kerberos 5 (not implemented as of 2 May 2004).</li>
</ul>
<p>The <span class="commandline">plugin_name</span> and <span class="commandline">plugin_version</span>
symbols required by the SLURM Plugin API require no specialization for authentication.
......@@ -266,7 +267,7 @@ to maintain data format compatibility across different versions of the plugin.</
<td colspan="3"><hr> <p>For information about this page, contact <a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</p>
<p><a href="http://www.llnl.gov/"><img align=middle src="lll.gif" width="32" height="32" border="0"></a></p>
<p class="footer">UCRL-WEB-201790<br>
Last modified January 15, 2004</p></td>
Last modified 2 May 2004</p></td>
</tr>
</table>
</td>
......
......
......@@ -9,13 +9,13 @@
<meta http-equiv="keywords" content="Simple Linux Utility for Resource Management, SLURM, resource management,
Linux clusters, high-performance computing, Livermore Computing">
<meta name="LLNLRandR" content="UCRL-WEB-201790">
<meta name="LLNLRandRdate" content="12 January 2004">
<meta name="LLNLRandRdate" content="2 May 2004">
<meta name="distribution" content="global">
<meta name="description" content="Simple Linux Utility for Resource Management">
<meta name="copyright"
content="This document is copyrighted U.S.
Department of Energy under Contract W-7405-Eng-48">
<meta name="Author" content="Moe Jette">
<meta name="Author" content="Morris Jette">
<meta name="email" content="jette@llnl.gov">
<meta name="Classification"
content="DOE:DOE Web sites via organizational
......@@ -70,8 +70,8 @@ information. APIs are available for all functions.</p>
<p>SLURM has a general-purpose plugin mechanism available to easily support various
infrastructure. These plugins presently include:
<ul>
<li>Authentication of communications: <a href="http://www.cs.berkeley.edu/~bnc/authd">authd</a>,
munge, or none (default).</li>
<li>Authentication of communications: <a href="http://www.theether.org/authd/">authd</a>,
<a href="http://www.llnl.gov/linux/munge/">munge</a>, or none (default).</li>
<li>Job logging: text file or none (default).</li>
<li>Scheduler: <a href="http://supercluster.org/maui">The Maui Scheduler</a>,
backfill, or FIFO (default).</li>
......@@ -96,7 +96,7 @@ of fast bit map manipulations. A sample (partial) SLURM configuration file follo
ControlMachine=linux0001
BackupController=linux0002
#
AuthType=auth/authd
AuthType=auth/munge
Epilog=/usr/local/slurm/sbin/epilog
HeartbeatInterval=60
PluginDir=/usr/local/slurm/lib
......@@ -137,7 +137,7 @@ excellent. The throughput rate of simple 2000 task jobs across 1000 nodes is ove
<td colspan="3"><hr> <p>For information about this page, contact <a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</p>
<p><a href="http://www.llnl.gov/"><img align=middle src="lll.gif" width="32" height="32" border="0"></a></p>
<p class="footer">UCRL-WEB-201790<br>
Last modified January 15, 2004</p></td>
Last modified 2 May 2004</p></td>
</tr>
</table>
</td>
......
......
......@@ -9,13 +9,13 @@
<meta http-equiv="keywords" content="Simple Linux Utility for Resource Management, SLURM, resource management,
Linux clusters, high-performance computing, Livermore Computing">
<meta name="LLNLRandR" content="UCRL-WEB-201790">
<meta name="LLNLRandRdate" content="12 January 2004">
<meta name="LLNLRandRdate" content="2 May 2004">
<meta name="distribution" content="global">
<meta name="description" content="Simple Linux Utility for Resource Management">
<meta name="copyright"
content="This document is copyrighted U.S.
Department of Energy under Contract W-7405-Eng-48">
<meta name="Author" content="Moe Jette">
<meta name="Author" content="Morris Jette">
<meta name="email" content="jette@llnl.gov">
<meta name="Classification"
content="DOE:DOE Web sites via organizational
......@@ -74,10 +74,12 @@ per the SLURM configuration.</p>
<h3>Infrastructure</h3>
<p>All communications between SLURM components are authenticated. The authentication
infrastructure used is specified in the SLURM configuration file and options include:
<a href="http://www.theether.org/authd/">authd</a>, munged and none.
<a href="http://www.theether.org/authd/">authd</a>,
<a href="http://www.llnl.gov/linux/munge/">munge</a>, and none.
The default authentication infrastructure is "none". This permits any user to execute
any job as another user. This may be fine for testing purposes, but certainly not for production
use. <b>Configure some AuthType value other than "none" if you want any security.</b></p>
use. <b>Configure some AuthType value other than "none" if you want any security.</b>
We recommend the use of munge unless you are experience with authd.</p>
<p>Quadrics MPI works directly with SLURM on systems having Quadrics interconnects.
For non-Quadrics interconnect systems, <a href="http://www.lam-mpi.org/">LAM/MPI</a>
is the preferred MPI infrastructure. LAM/MPI uses the command <i>lamboot</i> to
......@@ -150,7 +152,7 @@ minimum configuration values will be considered DOWN and not scheduled.</p>
#
ControlMachine=mcri ControlAddr=emcri
#
AuthType=auth/authd
AuthType=auth/munge
Epilog=/usr/local/slurm/etc/epilog
FastSchedule=1
JobCompLoc=/var/tmp/jette/slurm.job.log
......@@ -199,7 +201,9 @@ You will need to have at least one &quot;auth&quot; plugin. Currently, only thre
authentication plugins are supported: <b>auth/none</b>, <b>auth/authd</b>, and
<b>auth/munge</b>. The auth/none plugin is built and used by default, but either
Brent Chun's <a href="http://www.theether.org/authd/">authd</a>, or Chris Dunlap's
Munge should be installed in order to get properly authenticated communications.
<a href="http://www.llnl.gov/linux/munge/">munge</a> should be installed in order to
get properly authenticated communications.
Unless you are experience with authd, we recommend the use of munge.
The configure script in the top-level directory of this distribution will determine
which authentication plugins may be built. The configuration file specifies which
of the available plugins will be utilized. </p>
......@@ -348,7 +352,7 @@ adev0: scontrol shutdown
<td colspan="3"><hr> <p>For information about this page, contact <a href="mailto:slurm-dev@lists.llnl.gov">slurm-dev@lists.llnl.gov</a>.</p>
<p><a href="http://www.llnl.gov/"><img align=middle src="lll.gif" width="32" height="32" border="0"></a></p>
<p class="footer">UCRL-WEB-201790<br>
Last modified March 19, 2004</p></td>
Last modified 2 May 2004</p></td>
</tr>
</table>
</td>
......
......
.TH "slurm.conf" "5" "April 2004" "Morris Jette" "Slurm configuration file"
.TH "slurm.conf" "5" "May 2004" "Morris Jette" "Slurm configuration file"
.SH "NAME"
slurm.conf \- Slurm configuration file
.SH "DESCRIPTION"
......@@ -21,13 +21,17 @@ The overall configuration parameters available include:
\fBAuthType\fR
Define the authentication method for communications between SLURM
components.
Acceptable values at present include "auth/none" and "auth/authd".
Acceptable values at present include "auth/none", "auth/authd",
and "auth/munge".
The default value is "auth/none", which means the UID included in
communication messages is not verified.
This may be fine for testing purposes, but
\fBdo not use "auth/none" if you desire any security\fR.
"auth/authd" indicates that Brett Chun's authd is to be used (see
"http://www.theether.org/authd/" for more information).
"auth/munge" indicates that Chris Dunlap's munge is to be used
(this is the best supported authentication mechanism for SLURM,
see "http://www.llnl.gov/linux/munge/" for more information).
All SLURM daemons and commands must be terminated prior to changing
the value of \fBAuthType\fR and later restarted (SLURM jobs can be
preserved).
......
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment