Forge Home


Puppet type/provider for triggering MCollective


9,843 latest version

3.8 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.4.0 (latest)
  • 0.3.0
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.0
released Jan 22nd 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'fiddyspence-mcoresource', '0.4.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add fiddyspence-mcoresource
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install fiddyspence-mcoresource --version 0.4.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.



fiddyspence/mcoresource — version 0.4.0 Jan 22nd 2014

This is the mcoresource module. It provides a core type and provider for triggering mcollective agent actions from a Puppet Catalog during a Catalog apply action on an agent...

Consider the following resource chain:

exec { '/bin/true': }
mco { 'the thing':
  agent      => 'package',
  action     => 'upgrade',
  filter     => { 
                   'identity' => ['node1','node2','/somenodeswithacommonname/'],
                   'compound' => 'sysctl("vm.swappiness").value=50',
                   'class'    => ['aclass::withasubclass'],
  configfile => '/var/lib/peadmin/.mcollective',
  wait       => true,
  parameters => { 'package' => 'openssl' }

The mco resource is set to refreshonly => true by default, so unless it's triggered by a refresh event from another resource nothing will happen.

If triggered, the mcollective RPC agent puppet, with the action runonce will be triggered (filtering works for classes and identity - watch for magic later - maybe version 0.0.2) using the configuration file at configfile

Other parameters:

wait: whether to hold for RPC responses
parameters: other options to send the mcollective agent (e.g. the status action on the package agent requires package=foo)
optionhash: other mcollective client options - will override any defaults (e.g. optionshash => { 'theoption' => 'thevalue' })


Apache 2.0