MCollective Server and Client Puppet Module
Ruby Puppet
Pull request Compare This branch is 15 commits ahead, 399 commits behind voxpupuli:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
files/plugins
manifests
spec
templates
tests
.gitignore
CHANGELOG
LICENSE
Modulefile
README.markdown

README.markdown

MCollective Module

Author: Jeff McCune jeff@puppetlabs.com
Minor changes: Felipe Salum fsalum@gmail.com

This module manages MCollective from within Puppet.

Related Work

This is a fork from puppetlabs-mcollective with some minor changes, check CHANGELOG.

Quick Start

Manage both the mcollective server and client. Connect to the stomp server named "stomp."

node default {
  class { 'mcollective': }
}

Change the pre-shared key for both the client and the server:

node default {
  class { 'mcollective':
    mc_security_psk => 'abc123',
  }
}

Main parameters to specify:

node default {
  class { 'mcollective':
    mc_security_psk => 'abc123',
    stomp_server    => 'puppet.domain',
    stomp_user      => 'marionette',
    stomp_passwd    => 'mcollective',
    manage_plugins  => true,
    server          => true,
    client          => true,
  }
}

Registration

MCollective servers will automatically register themselves with the default behavior of this module. For more information about registration please see:

The out of box behavior is for all nodes to deploy a simple agent named 'registration' that writes information about the registering node to /var/tmp/mcollective This agent may be disabled to prevent all nodes from filling up their disks, but this is only an issue for extremely large sites.