Version information
released Jul 23rd 2017
This version is compatible with:
- ,
Start using this module
Add this module to your Puppetfile:
mod 'chwilk-slurm', '0.1.3'Learn more about managing modules with a PuppetfileDocumentation
chwilk/slurm — version 0.1.3 Jul 23rd 2017
slurm
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with slurm
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Overview
The Slurm Workload Manager is an open source project designed to manage compute resources on computational clusters of various sizes.
Module Description
This module is intended for the automated provisioning and management of compute nodes in a RedHat/CentOS based SLURM cluster.
For simplicity, some key configuration decisions have been assumed, namely:
- MUNGE will be used for shared key authentication, and the shared key can be provided to puppet via a URI.
- Standard MUNGE and SLURM packages have been compiled and made available to compute nodes via their installation repository of choice.
- slurm.conf is present on a shared file system, and that directory may be provided to the module as a parameter. /etc/slurm will be symlinked to it.
Setup
What slurm affects
- MUNGE packages will be installed (optional)
- The shared MUNGE key will be installed from a URI passed as a parameter to the module
- /etc/slurm will be removed and recreated as a symbolic link to the shared file system passed as a parameter to the module.
- munge and slurmd services will be kept alive
- The PAM stack will be (optionally) edited to insert SLURM PAM controls to meter access to the node only to users running jobs on said node.
- Optionally, the Warewulf Node Health Check will be installed and configured.
Setup Requirements
This module requires SLURM packages be made available by repo to the local node, and a shared file system with the SLURM configuration file be mounted already.
Beginning with slurm
The slurm module requires some parameters to be functional.
The most basic example, using munge with a provided munge key:
class slurm: {
munge_key_filename => '/shared/secret/munge.key',
slurm_conf_location => '/shared/slurm/etc',
}
Alternatively, if sharing the munge key over NFS is undesireable, you could set it up on the puppet file server as documented here
and then pass the puppet URI as the munge_key_filename.
Usage
The slurm module is intended to be modular for use in differently managed clusters. For instance:
We use something other than MUNGE to authenticate
class slurm: {
disable_munge => true,
slurm_conf_location => '/shared/slurm/etc',
}
We don't want users logging into compute nodes whether or not they have jobs there.
class slurm: {
munge_key_filename => '/shared/secret/munge.key',
slurm_conf_location => '/shared/slurm/etc',
disable_pam => true,
}
Reference
The style of this module has been borrowed heavily from the puppetlabs-ntp module.
Classes
Public Classes
- slurm: Main class, includes all other classes
Private Classes
-
slurm::install: Handles Package resources
-
slurm::config: Handles editing configuration files, symbolic link of /etc/slurm, and the munge key.
-
slurm::service: Handles slurmd and munge services
Parameters
Booleans
Some features of the slurm module can be turned on or off through the use of boolean switches:
#####disable_munge
Turns off all handling of munge keys or services. This may be used in case munge is to be handled separately, or if another authentication system is desired altogether.
Defaults to false
#####disable_pam
Turns off all editing of the PAM stack. PAM will no longer meter access by users running jobs.
Defaults to false
#####disable_slurmd
Turns off slurm daemon service (might be useful on login nodes, for instance)
Defaults to false
#####force_munge
Turns on the munged option --force which causes the munge server to attempt to run even if it is unhappy with its environment.
Defaults to false
#####package_manage
Turns off package installation, in case SLURM and/or MUNGE are to be handled in a different way.
Defaults to true
Strings
#####munge_key_filename
File or Puppet file server path to munge-key accessible by compute node.
#####munge_service_name
Which service to manage for munge.
Defaults to munge for most OS's
#####package_ensure
Set to 'present' by default, you could change this to 'latest' to force Puppet to automatically keep SLURM/MUNGE packages updated.
#####slurm_conf_location
Directory on compute node that contains the shared slurm.conf
Set to undef by default.
#####slurm_service_name
Which service to manage for the local slurmd daemon.
Varies based on distribution.
#####sysconfigdir
Where SLURM expects to find daemon config files on this distro.
Varies based on distribution.
Arrays
#####munge_packages
Set of packages to be maintained for munge.
#####pam_packages
Set of packages to be maintained for SLURM PAM integration.
#####slurm_packages
Set of packages to be maintained for SLURM itself.
Limitations
This module is being developed on Red Hat Enterprise Linux (RHEL) version 6. Contributions helping to port to other distributions or operating systems are welcome. I've tried to leave it in a state that will be considerate of porting efforts.
Development
I would be happy to review bug reports and pull requests via GitHub.
Release Notes/Contributors/Etc
- Fri Feb 5 2016 Chandler Wilkerson chwilk@gmail.com 0.1.2
- Updating
disable_slurmdparameter toensure_slurmd
- Wed Feb 3 2016 Chandler Wilkerson chwilk@gmail.com 0.1.1
- Added
disable_slurmdparameter
- Mon Feb 1 2016 Chandler Wilkerson chwilk@gmail.com 0.1.0
- Packaged and uploaded 0.1.0 release to Puppet Forge
Dependencies
- puppetlabs-stdlib (>= 4.13.1 <5.0.0)
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "{}"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright {yyyy} {name of copyright owner}
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.