Forge Home

rhn_register

Register a server with RHN, Spacewalk, or Satellite.

57,814 downloads

4,226 latest version

5.0 quality score

Version information

  • 1.6.1 (latest)
  • 1.6.0
  • 1.5.0
  • 1.0.0
  • 0.1.0
released Sep 25th 2019
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, 2017.2.x, 2016.4.x
  • Puppet >= 4.10.0 < 7.0.0

Start using this module

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

Add this module to your Puppetfile:

mod 'pcfens-rhn_register', '1.6.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add pcfens-rhn_register
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install pcfens-rhn_register --version 1.6.1

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.

Download

Documentation

pcfens/rhn_register — version 1.6.1 Sep 25th 2019

puppet-rhn_register

Build Status

Overview

Version 1.5 of this module is a fairly major overhaul, but should still be backwards compatible (but you should still test things first).

Registers a machine with RHN or a satellite server. If a machine is already registered then nothing happens, unless the force parameter is set to true.

Parameter names mostly match those used in the command itself, but are changed in some places to both preserve backwards compatibility, and to follow the puppet parameter naming conventions. Names will all conform to the puppet style guide when we move to 2.0 (probably the same time support for puppet 3.x will be dropped)

class rhn_register

rhn_register can use the more classic rhnreg_ks method of registering with a satellite server, or the newer subscription-manager register method. A username and password, or activation key are required regardless of the method used. The use_classic parameter (default is true for backwards compatibility) selects the method used (classic uses rhnreg_ks).

Using the classic (rhnreg_ks) method, available parameters are

  • username (string)
  • password (string)
  • activationkey (string)
  • proxy (string)
  • serverurl (string)
  • proxyuser (string)
  • proxypass (string)
  • sslca (string)
  • profilename (string)
  • hardware (boolean, default: true)
  • packages (boolean, default: true)
  • virtinfo (boolean, default: true)
  • rhnsd (boolean, default: true)
  • force (boolean, default: false)

Examples:

    class { 'rhn_register':
      sslca         => '/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT',
      serverurl     => 'https://my-satellite-server.example.com/XMLRPC',
      activationkey => '1-activationkeyiwanttouse',
    }

    class { 'rhn_register':
      activationkey => '1-activationkeyiwanttouseforrhn',
    }

The newer subscription-manager register method accepts

  • system_name (string, defaults to undefined, which RH defaults to the hostname)
  • username (string)
  • password (string)
  • activationkey (string)
  • serverurl (string)
  • proxy (string)
  • proxyuser (string)
  • proxypass (string)
  • insecure (boolean, default: false)
  • base_url (string)
  • unit_type (string, maps to type argument)
  • org (string)
  • consumer_id (string)
  • environment (string)
  • release (string)
  • auto_attach (boolean, default: true)
  • auto_subscribe (boolean, default: false)
  • service_level (string)

This method has not yet been fully tested for idempotency.

Supported Platforms

This class has only been tested on RHEL6.