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
83b6d625
Commit
83b6d625
authored
20 years ago
by
Moe Jette
Browse files
Options
Downloads
Patches
Plain Diff
Update bluegene info.
parent
f13a427a
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/html/bluegene.html
+22
-16
22 additions, 16 deletions
doc/html/bluegene.html
with
22 additions
and
16 deletions
doc/html/bluegene.html
+
22
−
16
View file @
83b6d625
...
...
@@ -9,7 +9,7 @@
<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-204324"
>
<meta
name=
"LLNLRandRdate"
content=
"
11 November
200
4
"
>
<meta
name=
"LLNLRandRdate"
content=
"
7 February
200
5
"
>
<meta
name=
"distribution"
content=
"global"
>
<meta
name=
"description"
content=
"Simple Linux Utility for Resource Management"
>
<meta
name=
"copyright"
...
...
@@ -146,10 +146,13 @@ a a a a . . . # Z
program locating some expected files. You should see "#define HAVE_BGL 1" and
"#define HAVE_FRONT_END 1" in the "config.h" file before making SLURM.
</p>
<p>
The slurmctld daemon should execute on the system's service node with
an optional backup daemon on one of the front end nodes.
<p>
The slurmctld daemon should execute on the system's service node.
If an optional backup daemon is used, it must be in some location where
it is capable of writing to MMCS.
One slurmd daemon should be configured to execute on one of the front end nodes.
That one slurmd daemon represents communications channel for every base partition.
A future release of SLURM will support multiple slurmd daemons on multiple
front end nodes.
You can use the scontrol command to drain individual nodes as desired and
return them to service.
</p>
...
...
@@ -185,31 +188,34 @@ If large numbers of job steps are initiated by slurmd, expect the daemon to
fail due to lack of memory.
</p>
<p>
Presently the system administrator must explicitly define each of the
Blue Gene
job
partitions available to execute jobs.
(
<b>
NOTE:
</b>
Blue Gene
job
partitions are unrelated to SLURM partitions.)
Jobs must then execute in one of these pre-defined
Blue Gene job partition
s.
Blue Gene partitions
(or bglblocks)
available to execute jobs.
(
<b>
NOTE:
</b>
Blue Gene partitions are unrelated to SLURM partitions.)
Jobs must then execute in one of these pre-defined
bglblock
s.
This is known as
<i>
static partitioning
</i>
.
Each of these Blue Gene job partitions is explicitly configured with
either a mesh or torus interconnect and either coprocessor or virtual
c-node usage.
Each of these bglblocks are explicitly configured with either a mesh or
torus interconnect.
In addition to the normal
<i>
slurm.conf
</i>
file, a new
<i>
bluegene.conf
</i>
configuration file is required with this information.
Put
<i>
bluegene.conf
</i>
into the SLURM configuration directory with
<i>
slurm.conf
</i>
.
System administrators should use the smap tool to build appropriate
configuration files for static partitioning.
See the smap man page for more information.
</p>
configuration file for static partitioning.
See the smap man page for more information.
Note that in addition to the bglblocks defined in blugene.conf, an
additional block containing all resources is created.
Make use of the SLURM partition mechanism to control access to these
bglblocks.
</p>
<p>
Two other changes are required to support SLURM interactions with
the DB2 database.
The
<i>
db2profile
</i>
script must be executed prior to the execution
of the slurmctld daemon.
This may be accomplished by
copy
ing the
approriate file into
<i>
/etc/sysconfig/slurm
</i>
, which
will be
executed by
This may be accomplished by
execut
ing the
script from
<i>
/etc/sysconfig/slurm
</i>
, which
is
executed by
<i>
/etc/init.d/slurm
</i>
.
The second required file is
<i>
db.properties
</i>
, which should
be copied into the SLURM configuration directory with
<i>
slurm.conf
</i>
.
</p>
be copied into the SLURM configuration directory with
<i>
slurm.conf
</i>
.
Again, this can be accomplished using /etc/sysconfig/slurm.
</p>
<p>
At some time in the future, we expect SLURM to support
<i>
dynamic
partitioning
</i>
in which Blue Gene job partitions are created and destroyed
...
...
@@ -225,7 +231,7 @@ rebooting of c-nodes and I/O nodes.</p>
<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-207187
<br>
Last modified
11 November
200
4
</p></td>
Last modified
7 February
200
</p></td>
</tr>
</table>
</td>
...
...
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