- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with make_noop
- Usage - Configuration options and additional functionality
- MCO_Usage - How to use the MCO application
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
The module contains a MCollective Application and Agent that enables or disables via the puppet.conf
file for most Puppet agents.
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.
Manages the MCo Agent and Application; restarts the MCollective service on change.
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.
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.
Boolean value to determine if the MCO agent is installed and managed.
A false
value will remove the agent.
Default is true
.
Boolean value to determine if the MCO application is installed and managed.
A false
value will remove the application.
Default is false
.
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
Used and tested on CentOS/RHEL6