slurm_providers

pdk
SLURM Puppet types/providers

Trey Dockendorf

treydock

5,413 downloads

293 latest version

5.0 quality score

Version information

  • 0.11.0 (latest)
  • 0.10.0
  • 0.9.0
  • 0.8.0
  • 0.7.3
  • 0.7.2
  • 0.7.1
  • 0.7.0
  • 0.6.1
  • 0.6.0
  • 0.5.0
  • 0.4.2
  • 0.4.1
  • 0.4.0
  • 0.3.0
  • 0.2.0
  • 0.1.1
  • 0.1.0
released Jan 12th 2021
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x
  • Puppet >= 5.0.0 < 7.0.0
  • CentOS
    ,
    OracleLinux
    ,
    RedHat
    ,
    Scientific

Start using this module

Tags: slurm, hpc, batch

Documentation

treydock/slurm_providers — version 0.11.0 Jan 12th 2021

puppet-slurm_providers

Puppet Forge Build Status

Table of Contents

  1. Overview
  2. Setup - The basics of getting started
  3. Reference - An under-the-hood peek at what the module is doing
  4. Limitations - OS compatibility, etc.

Overview

The SLURM providers module lets you manage various SLURM resources with Puppet.

Supported versions of SLURM

Currenlty this module supports version 19.05 of SLURM

Setup

This module requires that sacctmgr be in PATH.

If SLURM binaries are is not in path then then you must configure Puppet with a valid path to sacctmgr and scontrol. Below is an example of configuring Puppet if SLURM install prefix is /opt/slurm.

slurm_config { 'puppet':
  sacctmgr_path => '/opt/slurm/bin/sacctmgr',
  scontrol_path => '/opt/slurm/bin/scontrol',
}

Reference

http://treydock.github.io/puppet-slurm_providers/

Limitations

This module has been tested using the following versions of SLURM

  • 20.02.x
  • 20.11.x

The following operating systems have been tested

  • RHEL/CentOS 7 x86_64

Development

Testing

Install gem dependencies

bundle install

Run unit tests

bundle exec rake spec

The following environment variables can be used to modify the behavior of the beaker tests:

  • SLURM_BEAKER_version - Version of SLURM to install. Defaults to 20.02.3

Example of running beaker tests using an internal repository, and leaving VMs running after the tests.

export BEAKER_destroy=no
export BEAKER_PUPPET_COLLECTION=puppet5
export PUPPET_INSTALL_TYPE=agent
export BEAKER_set=centos-7
bundle exec rake beaker