Forge Home


Manage MCollective client, service and plugins


9,831 latest version

3.5 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

  • 0.0.6 (latest)
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Oct 17th 2013

Start using this module

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

Add this module to your Puppetfile:

mod 'fsalum-mcollective', '0.0.6'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add fsalum-mcollective
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install fsalum-mcollective --version 0.0.6

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.



fsalum/mcollective — version 0.0.6 Oct 17th 2013

MCollective Module

Author: Jeff McCune
Minor changes: Felipe Salum

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,


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.