Forge Home

make_noop

A module with a MCO agent and application to enable or disable noop

beergeek

beergeek

6,289 downloads

5,044 latest version

3.5 quality score

Version information

  • 0.2.5 (latest)
  • 0.2.4
  • 0.2.3
  • 0.2.2
released Jul 12th 2017
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 4.0.0 < 5.0.0
  • Debian
    ,
    RedHat
    ,
    CentOS
    ,
    Solaris
    ,
    Windows

Start using this module

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

Add this module to your Puppetfile:

mod 'beergeek-make_noop', '0.2.5'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add beergeek-make_noop
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install beergeek-make_noop --version 0.2.5

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

beergeek/make_noop — version 0.2.5 Jul 12th 2017

make_noop

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 make_noop
  4. Usage - Configuration options and additional functionality
  5. MCO_Usage - How to use the MCO application
  6. Reference - An under-the-hood peek at what the module is doing and how
  7. Limitations - OS compatibility, etc.
  8. Development - Guide for contributing to the module

Overview

The module contains a MCollective Application and Agent that enables or disables via the puppet.conf file for most Puppet agents.

Module Description

Manages MCollective Agent and Application. The MCO Agent should be on most Puppet nodes. The MCO Application should be on the node driving the 'noop' selection.

Setup

Manages the MCo Agent and Application; restarts the MCollective service on change.

Setup Requirements

Does not use pluginsync as we do not want all nodes to have these agents or applications, and needs to restart the MCollective service on change.

Beginning with make_noop

By defaul the MCO Agent is created, but the MCO Application is not.

The can be part of a Profile, such as a SOE profile.

Usage

Reference

Classes

make_noop

include_agent

Boolean value to determine if the MCO agent is installed and managed. A false value will remove the agent. Default is true.

include_app

Boolean value to determine if the MCO application is installed and managed. A false value will remove the application. Default is false.

MCO Usage

To enable noop for all Puppet nodes in an environment perform the following with a MCO client:

  mco enable_noop

To disable noop for all Puppet nodes in an environment perform the following with a MCO client:

  mco disable_noop

Limitations

Used and tested on CentOS/RHEL6

Development

Release Notes/Contributors/Etc