Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Slurm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tud-zih-energy
Slurm
Commits
bc1d4c0d
Commit
bc1d4c0d
authored
21 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Fix typos reported by "spell".
parent
4c7a0efd
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/pubdesign/report.tex
+9
-9
9 additions, 9 deletions
doc/pubdesign/report.tex
with
9 additions
and
9 deletions
doc/pubdesign/report.tex
+
9
−
9
View file @
bc1d4c0d
...
...
@@ -406,7 +406,7 @@ with access to those resources.
In order to simplify the use of different infrastructures,
SLURM uses a general purpose plugin mechanism. A SLURM plugin is a
dynamically linked code object which is loaded explicitly at run time
by the SLURM libraries. A plugin provides a customized implemenation
by the SLURM libraries. A plugin provides a customized implemen
t
ation
of a well-defined API connected to tasks such as authentication,
interconnect fabric, task scheduling, etc. A common set of functions is defined
for use by all of the different infrastructures of a particular variety.
...
...
@@ -469,12 +469,12 @@ source port of a request to ensure that it is less than a certain value,
and thus only accessible by
{
\tt
root
}
. The communications over that
connection are then implicitly trusted. Since reserved ports are a very
limited resource and set-uid programs are a possible security concern,
we have
strived to
employ a credential based authentication scheme which
we have employ
ed
a credential based authentication scheme which
does not depend on reserved ports. In this design, a SLURM authentication
credential is attached to every message and author
a
tatively verifies the
credential is attached to every message and author
i
tatively verifies the
uid and gid of the message originator. Once recipients of SLURM messages
verify the validity of the authentication credential, they can use the uid
and gid from the credential as the author
a
tative identity of the sender.
and gid from the credential as the author
i
tative identity of the sender.
The actual implementation of the SLURM authentication credential is
relegated to an ``auth'' plugin. We presently have implemented three
...
...
@@ -483,7 +483,7 @@ functional authentication plugins: {\tt authd}~\cite{Authd2002},
credential and is only suitable for testing and networks where security
is not a concern. Both the
{
\tt
authd
}
and Munge implementations employ
cryptography to generate a credential for the requesting user that
may then be author
a
tatively verified on any remote nodes. However,
{
\tt
may then be author
i
tatively verified on any remote nodes. However,
{
\tt
authd
}
assumes a secure network and Munge does not. Other authentication
implementations, such as a credential based on Kerberos, should be easy
to develop using the ``auth'' plugin API.
...
...
@@ -1043,7 +1043,7 @@ ID associated with each task, and user associated with the job. In the
event of
\slurmd\
failure, this information is recovered from disk in
order to identify active jobs.
When
\slurmd\
rec
i
eves a job termination request from the SLURM
When
\slurmd\
rece
i
ves a job termination request from the SLURM
controller, it sends SIGTERM to all running tasks in the job,
waits for
{
\tt
KillWait
}
seconds (as specified in the configuration
file), then sends SIGKILL. If the processes do not terminate
\slurmd\
...
...
@@ -1266,7 +1266,7 @@ takes the necessary steps to initiate the user's executable on the node,
initializing environment, current working directory, and interconnect
resources if needed.
Each
\slurmd\
forks a copy of itself which is resposible for the job
Each
\slurmd\
forks a copy of itself which is respo
n
sible for the job
step on this node. This local ``job manager'' process then creates an
IO thread which initializes stdout, stdin, and stderr streams for each
local task and connects these streams to the remote
\srun
. Meanwhile,
...
...
@@ -1367,10 +1367,10 @@ general method as described in the section on interactive job initiation.
When the user exits the allocate sub-shell, the original
\srun\
receives
exit status, notifies
\slurmctld\
that the job is complete, and exits.
The controller runs the epilog on each of the allocated nodes, returning
nodes to the partition as they succ
c
essfully complete the epilog.
nodes to the partition as they successfully complete the epilog.
%
% Information in this section seems like it should be somplace else
% Information in this section seems like it should be som
e
place else
% (Some of it is incorrect as well)
% -mark
%
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment