Forge Home

remaster

Module for managing the process of moving agent nodes to point to a new master

15,896 downloads

14,435 latest version

4.6 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

  • 1.0.0 (latest)
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Oct 13th 2014
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 'opentable-remaster', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add opentable-remaster
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install opentable-remaster --version 1.0.0

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
Tags: puppet, master

Documentation

opentable/remaster — version 1.0.0 Oct 13th 2014

puppet-remaster

####Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with remaster
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module

##Overview

The remaster module for managing the transition of a puppet agent between masters

Build Status

##Module Description

This module manages the server agent settings on a given puppet node. The intention of doing this is that it allows you to transition your node from one puppet master to another during an upgrade process.

##Setup

###What remaster affects

  • The server and ca_server settings in the /etc/puppet.conf file.

###Beginning with remaster

Assign a node to a particular master:


   remaster { 'puppetmaster':
      puppetmaster => 'puppetmaster.corp.company.com'
   }

##Usage

###Classes and Defined Types

####Class: remaster The remaster module primary type, remaster, guides the remastering of your nodes from one puppet master to another

Parameters within remaster: #####puppetmaster The fqdn of the master that you want your nodes to point to.

##Reference

###Classes ####Public Classes

  • remaster: Remaster your node from one master to another ####Private Classes
  • remaster::service: Ensure that the puppet service is up and running

##Limitations

This module is tested on the following platforms:

  • CentOS 5
  • CentOS 6
  • Ubuntu 12.04
  • Ubuntu 14.04

It is tested with the OSS version of Puppet only.

##Development

###Contributing

Please read CONTRIBUTING.md for full details on contributing to this project.