Forge Home


Configuration of a single system administrator account (localadmin by default) attached to (potentially) several users


561 latest version

3.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.8.7 (latest)
  • 0.8.6
  • 0.8.5
  • 0.8.4
  • 0.8.3
  • 0.8.2
  • 0.8.1
  • 0.8.0
  • 0.7.4
  • 0.7.3
released Apr 27th 2022
This version is compatible with:

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'ULHPC-sysadmins', '0.8.7'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ULHPC-sysadmins
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ULHPC-sysadmins --version 0.8.7

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



ULHPC/sysadmins — version 0.8.7 Apr 27th 2022

-- mode: markdown; mode: visual-line; --

Sysadmins Puppet Module

Puppet Forge License Supported Platforms Documentation Status

Configuration of a single system administrator account (localadmin by default) attached to (potentially) several users

  Copyright (c) 2019 UL HPC Team <>

| Project Page | Sources | Documentation | Issues |


Configuration of a single system administrator account (localadmin by default) attached to (potentially) several users.

This module implements the following elements:

  • Puppet classes:

    • sysadmins
    • sysadmins::common
    • sysadmins::common::debian
    • sysadmins::common::redhat
    • sysadmins::params
  • Puppet definitions:

All these components are configured through a set of variables you will find in manifests/params.pp.

Note: the various operations that can be conducted from this repository are piloted from a Rakefile and assumes you have a running Ruby installation. See docs/ for more details on the steps you shall follow to have this Rakefile working properly.


See metadata.json. In particular, this module depends on

Overview and Usage

Class sysadmins

This is the main class defined in this module. It accepts the following parameters:

  • $ensure: default to 'present', can be 'absent'

  • $login: the actual login used for the local sysadmin account

    • Default: localadmin
  • $email: redirect all mails sent to the sysadmin account to this email address

  • $purge_ssh_keys: whether to purge the authorized_keys files or not

  • $filter_access: whether or not to prevent access to the sysadmin account for non-registered users (via ~<login>/.sysadminrc)

    • Default: true
  • $users: hash of the users authorized to connect to the local sysadmin account i.e. the real users (system administrators). The format of each entry is as follows:

         firstname: <firstname>
       lastname: <lastname>
       email: <email>
       office: <address>
  • $groups: Additonnal groups the sysadmin user is member of

  • $ssh_keys: Hash of the SSH keys -- each entry should be prefixed by the appropriate login defined in sysadmins::users as follows:

           type: <key_type>
           public: <public_key>

Use it as follows:

  class { 'sysadmins':
      ensure         => 'present',
      groups         => [ 'vagrant' ],   # can be a string
      users          => hiera_hash('sysadmins::users', {}),
      ssh_keys       => hiera_hash('sysadmins::ssh_keys', {}),
      purge_ssh_keys => true,

Example hiera YAML file (see also tests/hiera/common.yaml):

# Example of Users definitions
    firstname: Sébastien
    lastname: Varrette
    office: Campus Kirchberg, E-007
    firstname: Hyacinthe
    lastname: Cartiaux
    office: Campus Kirchberg, E-008
# SSH keys -- should be prefixed by the appropriate login defined in sysadmins::users
#   Format: <login>[@<comment>]:
#               type:
#               public:
    type: ssh-dss
    public: AAAAB3NzaC1kc3MA...
    type: ssh-rsa
    public: 5reQfxIMsEU/4336qUHY0wAAAIBFs...
    type: ssh-dss
    public: MAAACBAKQMf834bHh4TFMecBKK...
    type: ssh-dss
    public: QMf834bHh4T...
    type: ssh-rsa
    public: HY0wAAAIBF...

See also tests/init.pp

This will create the localadmin account. In the example above, the ~localadmin/.ssh/authorized_keys holds the SSH keys of only svarrette and hcartiaux users as they are the ones listed in sysadmins::users. Example:

   $> cat ~localadmin/.ssh/authorized_keys
   # HEADER: This file was autogenerated at 2015-06-02 20:40:46 +0000
   # HEADER: by puppet.  While it can still be managed manually, it
   # HEADER: is definitely not recommended.
   environment="SYSADMIN_USER=svarrette" ssh-rsa 5reQfxIMsEU/4336qUHY0wAAAIBFs... svarrette@debugkey-on-localadmin
   environment="SYSADMIN_USER=hcartiaux" ssh-dss MAAACBAKQMf834bHh4TFMecBKK... hcartiaux-on-localadmin
   environment="SYSADMIN_USER=svarrette" ssh-dss AAAAB3NzaC1kc3MA... svarrette@falkor.uni.lux-on-localadmin

As you can notice, the special environment variable SYSADMIN_USER is set. It is used to eventually restrict the access to the localadmin account (see ~localadmin/.sysadminrc).

Librarian-Puppet / R10K Setup

You can of course configure the sysadmins module in your Puppetfile to make it available with Librarian puppet or r10k by adding the following entry:

 # Modules from the Puppet Forge
 mod "ULHPC/sysadmins"

or, if you prefer to work on the git version:

 mod "ULHPC/sysadmins", 
     :git => '',
     :ref => 'production' 

Issues / Feature request

You can submit bug / issues / feature request using the ULHPC/sysadmins Puppet Module Tracker.

Developments / Contributing to the code

If you want to contribute to the code, you shall be aware of the way this module is organized. These elements are detailed on docs/

You are more than welcome to contribute to its development by sending a pull request.

Puppet modules tests within a Vagrant box

The best way to test this module in a non-intrusive way is to rely on Vagrant. The Vagrantfile at the root of the repository pilot the provisioning various vagrant boxes available on Vagrant cloud you can use to test this module.

See docs/ for more details.

Online Documentation

Read the Docs aka RTFD hosts documentation for the open source community and the ULHPC/sysadmins puppet module has its documentation (see the docs/ directly) hosted on readthedocs.

See docs/ for more details.


This project and the sources proposed within this repository are released under the terms of the GPL-3.0 licence.