mcollective

Overview
Module Description - What the module does and why it is useful
Setup - The basics of getting started with mcollective
- What the mcollective module affects
- Beginning with mcollective
Usage - Configuration options and additional functionality
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

Overview

The mcollective module installs, configures, and manages the mcollective agents, clients, and middleware of an mcollective cluster.

Module Description

The mcollective module handles installing and configuring mcollective across a range of operating systems and distributions. Where possible we follow the standards laid down by the MCollective Standard Deployment guide.

MCollective Terminology

A quick aside, mcollective's terminology differs a little from what you might be used to in puppet. There are 3 main components, the client (the mco commands you run to control your servers), the server (a daemon that runs on all of your managed nodes and executes the commands), and the middleware (a message broker the servers and agent connect to).

If it helps to map these to puppet concepts you loosely have:

Middleware -> Puppet Master
MCollective Server -> Puppet Agent
MCollective Client -> no direct equivalent

Setup

What the mcollective module affects

On a server

mcollective package
mcollective server configuration file
mcollective service

On a client

mcollective-client package
mcollective client configuration file
optionally user configuration files (~/.mcollective and ~/.mcollective.d)

On a middleware host

broker installation
broker configuration

Beginning with mcollective

Your main entrypoint to the mcollective module is the mcollective class, so assuming you have your middleware configured on a node this is all you need to add a server to mcollective.

class { '::mcollective':
  middleware_hosts => [ 'broker1.example.com' ],
}

Usage

Your primary interaction with the mcollective module will be though the main mcollective class, with secondary configuration managed by the defined types mcollective::user, mcollective::plugin, mcollective::actionpolicy, and mcollective::actionpolicy::rule.

I just want to run it, what's the minimum I need?

node 'broker1.example.com' {
  class { '::mcollective':
    middleware       => true,
    middleware_hosts => [ 'broker1.example.com' ],
  }
}

node 'server1.example.com' {
  class { '::mcollective':
    middleware_hosts => [ 'broker1.example.com' ],
  }
}

node 'control1.example.com' {
  class { '::mcollective':
    client            => true,
    middleware_hosts => [ 'broker1.example.com' ],
  }
}

This default install will be using no TLS, a set of well-known usernames and passwords, and the psk securityprovider. This is against the recommendataion of the standard deploy guide but does save you from having to deal with ssl certificates to begin with.

I'd like to secure the transport channel and authenticate users, how do I do that?

Gather some credentials for the server and users. You'll need the ca certificate, and a keypair for the server to use, and a keypair for each user to allow.

See the standard deploy guide for more information about how to generate these.

node 'broker1.example.com' {
  class { '::mcollective':
    middleware         => true,
    middleware_hosts   => [ 'broker1.example.com' ],
    middleware_ssl     => true,
    securityprovider   => 'ssl',
    ssl_client_certs   => 'puppet:///modules/site_mcollective/client_certs',
    ssl_ca_cert        => 'puppet:///modules/site_mcollective/certs/ca.pem',
    ssl_server_public  => 'puppet:///modules/site_mcollective/certs/server.pem',
    ssl_server_private => 'puppet:///modules/site_mcollective/private_keys/server.pem',
  }
}

node 'server1.example.com' {
  class { '::mcollective':
    middleware_hosts   => [ 'broker1.example.com' ],
    middleware_ssl     => true,
    securityprovider   => 'ssl',
    ssl_client_certs   => 'puppet:///modules/site_mcollective/client_certs',
    ssl_ca_cert        => 'puppet:///modules/site_mcollective/certs/ca.pem',
    ssl_server_public  => 'puppet:///modules/site_mcollective/certs/server.pem',
    ssl_server_private => 'puppet:///modules/site_mcollective/private_keys/server.pem',
  }

  mcollective::actionpolicy { 'nrpe':
    default => 'deny',
  }

  mcollective::actionpolicy::rule { 'vagrant user can use nrpe agent':
    agent    => 'nrpe',
    callerid => 'cert=vagrant',
  }
}

node 'control.example.com' {
  class { '::mcollective':
    client             => true,
    middleware_hosts   => [ 'broker1.example.com' ],
    middleware_ssl     => true,
    securityprovider   => 'ssl',
    ssl_client_certs   => 'puppet:///modules/site_mcollective/client_certs',
    ssl_ca_cert        => 'puppet:///modules/site_mcollective/certs/ca.pem',
    ssl_server_public  => 'puppet:///modules/site_mcollective/certs/server.pem',
    ssl_server_private => 'puppet:///modules/site_mcollective/private_keys/server.pem',
  }

  mcollective::user { 'vagrant':
    certificate => 'puppet:///modules/site_mcollective/client_certs/vagrant.pem',
    private_key => 'puppet:///modules/site_mcollective/private_keys/vagrant.pem',
  }
}

The `::mcollective::` class

The mcollective class is the main entry point to the module. From here you can configure the behaviour of your mcollective install of server, client, and middleware.

Parameters

The following parameters are available to the mcollective class:

`server`

Boolean: defaults to true. Whether to install the mcollective server on this node.

`client`

Boolean: defaults to false. Whether to install the mcollective client application on this node.

`middleware`

Boolean: defaults to false. Whether to install middleware that matches $mcollective::connector on this node.

`activemq_template`

String: defaults to 'mcollective/activemq.xml.erb'. Template to use when configuring activemq middleware.

`activemq_console`

Boolean: defaults to false. Whether to enable the jetty admin console when configuring the activemq middleware.

`activemq_config`

String: defaults to undef. If supplied the contents of the activemq.xml configuration file to use when configuring activemq middleware. Bypasses mcollective::activemq_template

`activemq_confdir`

String: default based on distribution. The directory to copy ssl certificates to when configuring activemq middleware with mcollective::middleware_ssl.

`activemq_memoryUsage`

String: default "20 mb". The amount of memory ActiveMQ will take up with actual messages; it doesn't include things like thread management. See ActiveMQ - Memory and Temp Usage for Messages (systemUsage) for further information. String must match '^[0-9]+ [kmg]b$'.

`activemq_storeUsage`

String: default "1 gb". The amount of disk space ActiveMQ will use for stashing non-persisted messages if the memoryUsage is exceeded (e.g. in the event of a sudden flood of messages). See ActiveMQ - Memory and Temp Usage for Messages (systemUsage) for further information. String must match '^[0-9]+ [kmg]b$'.

`activemq_tempUsage`

String: default "100 mb". The amount of disk space dedicated to persistent messages (which MCollective doesn't use directly, but which may be used in networks of brokers to avoid duplicates). See ActiveMQ - Memory and Temp Usage for Messages (systemUsage) for further information. String must match '^[0-9]+ [kmg]b$'.

`rabbitmq_confdir`

String: defaults to '/etc/rabbitmq'. The directory to copy ssl certificates to when configuring rabbitmq middleware with mcollective::middleware_ssl.

`rabbitmq_vhost`

String: defaults to '/mcollective'. The vhost to connect to/manage when using rabbitmq middleware.

`delete_guest_user`

Boolean: defaults to 'false'. Whether to delete the rabbitmq guest user when setting up rabbitmq middleware.

`manage_packages`

Boolean: defaults to true. Whether to install mcollective and mcollective- client packages when installing the server and client components.

`version`

String: defaults to 'present'. What version of packages to ensure when mcollective::manage_packages is true.

`ruby_stomp_ensure`

String: defaults to 'installed'. What version of the ruby-stomp package to ensure when mcollective::manage_packages is true. Only relevant on the Debian OS family.

`main_collective`

String: defaults to 'mcollective'. The name of the main collective for this client/server.

`collectives`

String: defaults to 'mcollective'. Comma seperated list of collectives this server should join.

`connector`

String: defaults to 'activemq'. Name of the connector plugin to use.

Currently supported are activemq, rabbitmq, and redis

`securityprovider`

String: defaults to 'psk'. Name of the security provider plugin to use. 'ssl' is recommended but requires some additional setup.

`psk`

String: defaults to 'changemeplease'. Used by the 'psk' security provider as the pre-shared key to secure the collective with.

`factsource`

String: defaults to 'yaml'. Name of the factsource plugin to use on the server.

`yaml_fact_path`

String: defaults to '/etc/mcollective/facts.yaml'. Name of the file the 'yaml' factsource plugin should load facts from.

`excluded_facts`

Array: defaults to []. List of facts to exclude from facts.yaml when factsource is 'yaml'. This is useful for preventing dynamic facts (that change on each Puppet run) from ending up in facts.yaml, which would trigger restarts of Mcollective. A default list of facts to ignore is managed internally: uptime.*, rubysitedir, _timestamp, memoryfree.*, swapfree.* and last_run. Note that the fact names can be Ruby regular expressions.

`classesfile`

String: defaults to '/var/lib/puppet/state/classes.txt'. Name of the file the server will load the configuration management class for filtering.

`rpcauthprovider`

String: defaults to 'action_policy'. Name of the RPC Auth Provider to use on the server.

`rpcauditprovider`

String: defaults to 'logfile'. Name of the RPC Audit Provider to use on the server.

`registration`

String: defaults to undef. Name of the registration plugin to use on the server.

`core_libdir`

String: default is based on platform. Path to the core plugins that are installed by the mcollective-common package.

`site_libdir`

String: default is based on platform. Path to the site-specific plugins that the mcollective::plugin type will install with its source parameter.

This path will be managed and purged by puppet, so don't point it at core_libdir or any other non-dedicated path.

`middleware_hosts`

Array of strings: defaults to []. Where the middleware servers this client/server should talk to are.

`middleware_user`

String: defaults to 'mcollective'. Username to use when connecting to the middleware.

`middleware_password`

String: defaults to 'marionette'. Password to use when connecting to the middleware.

`middleware_port`

String: defaults to '61613'. Port number to use when connecting to the middleware over an unencrypted connection.

`middleware_ssl_port`

String: defaults to '61614'. Port number to use when connecting to the middleware over a ssl connection.

`middleware_ssl`

Boolean: defaults to false. Whether to talk to the middleware over a ssl protected channel. Highly recommended. Requires mcollective::ssl_ca_cert, mcollective::ssl_server_public, mcollective::ssl_server_private parameters for the server/client install.

`middleware_admin_user`

String: defaults to 'admin'. Username for the middleware admin user.

`middleware_admin_password`

String: defaults to 'secret'. Password to for the middleware admin user.

`server_config_file`

String: default is '/etc/mcollective/server.cfg'. Path to the server configuration file.

`server_logfile`

String: defaults to '/var/log/mcollective.log'. Logfile the mcollective server should log to.

`server_loglevel`

String: defaults to 'info'. Level the mcollective server should log at.

`server_daemonize`

String: defaults to '1'. Should the mcollective server daemonize when started.

`client_config_file`

String: defaults to '/etc/mcollective/client.cfg'. Path to the client configuration file.

`client_logger_type`

String: defaults to 'console'. What type of logger the client should use.

`client_loglevel`

String: defaults to 'warn'. Level the mcollective client should log at.

`ssl_ca_cert`

String: defaults to undef. A file source that points to the ca certificate used to manage the ssl keys of the mcollective install.

`ssl_server_public`

String: defaults to undef. A file source that points to the public key or certificate of the server keypair.

`ssl_server_private`

String: defaults to undef. A file source that points to the private key of the server keypair.

`ssl_client_certs`

String: defaults to 'puppet:///modules/mcollective/empty'. A file source that contains a directory of user certificates which are used by the ssl security provider in authenticating user requests.

`mcollective::user` defined type

mcollective::user installs a client configuration and any needed client certificates in a users home directory.

Parameters

`username`

String: defaults to $name. The username of the user to install for.

`group`

String: defaults to $name. The group of the user to install for.

`homedir`

String: defaults to "/home/${name}". The home directory of the user to install for.

`certificate`

String: defaults to undef. A file source for the certificate of the user. Used by the 'ssl' securityprovider to set the identity of the user.

`private_key`

String: defaults to undef. A file source for the private key of the user. Used when mcollective::middleware_ssl is true to connect to the middleware and by the 'ssl' securityprovider to sign messages as from this user.

`mcollective::plugin` defined type

mcollective::plugin installs a plugin from a source uri or a package. When installing from a source uri the plugin will be copied to mcollective::site_libdir

mcollective::plugin { 'puppet':
  package => true,
}

When installing a plugin from source you need to create the correct directory structure for it to work.

For example if you wish to sync an agent for apt which ships with apt.ddl and apt.rb you need to create the following structure:

site_mcollective/files/plugins/apt/
                               └── mcollective
                                   └── agent
                                       ├── apt.ddl
                                       └── apt.rb

Now you can then point the source attribute of the defined type to the apt folder in your plugins directory.

mcollective::plugin { 'apt':
  source => 'puppet:///modules/site_mcollective/plugins/apt',
}

For more examples have a look at the directory structure in files/plugins of this module.

Parameters

`name`

String: the resource title. The base name of the plugin to install.

`source`

String: will default to "puppet:///modules/mcollective/plugins/${name}". The source uri that will be copied to mcollective::site_libdir

`package`

Boolean: defaults to false. Whether to install the plugin from a file copy or a package install.

`type`

String: defaults to 'agent'. The type of the plugin package to install.

`has_client`

Boolean: defaults to true. When installing from a package, whether to attempt to install mcollective-${name}-client on the client node.

`mcollective::actionpolicy` defined type

mcollective::actionpolicy configures an agent for use with actionpolicy in conjunction with mcollective::actionpolicy::rule.

Parameters

`name`

String: the resource title. The name of the agent to set up an actionpolicy for.

`default`

String: defaults to 'deny'. The default actionpolicy to apply to the agent.

`mcollective::actionpolicy::rule` defined type

mcollective::actionpolicy::rule represents a single actionpolicy policy entry.

Parameters

`name`

String: the resource title. A descriptive name for the rule you are adding.

`agent`

String: required, no default. The name of the agent you are adding a rule for.

`action`

String: defaults to 'allow'. What to do when the other conditions of this line are matched.

`callerid`

Reference

Configuration merging

The configuration of the server and client are built up from the various calls to mcollective::common::setting, mcollective::server::setting, mcollective::client::setting, and mcollective::user::setting.

Settings for the server will be a merge of mcollective::common::setting and mcollective::server::setting, highest order of the setting wins.

Settings for the client will be a merge of mcollective::common::setting, and mcollective::client::setting, highest order of the setting wins.

Settings for a specific user will be a merge of mcollective::common::setting, mcollective::client::setting and mcollective::user::setting for that specific user, highest order of setting wins.

Overriding existing options

You can override an existing server setting from outside of the module by simply specifying that setting again with a higher order than the default of that type, for example to make a server's loglevel be debug (without simply setting mcollective::server_loglevel) you could write:

mcollective::server::setting { 'override loglevel':
  setting => 'loglevel',
  value   => 'debug',
  order   => '50',
}

Troubleshooting

Why do I have no client.cfg?

I said to install the client, so why when I run mco ping am I seeing this:

$ mco ping
Failed to generate application list: RuntimeError: Cannot find config file '/etc/mcollective/client.cfg'

You've enabled the ssl security provider, which implies each user will have their own ssl credentials to use in the collective. In order to avoid incomplete configuration of clients in this mode we delete the system-wide /etc/mcollective/client.cfg and only generate user configuration files with the mcollective::user definition.

Limitations

This module has been built on and tested against Puppet 3.0 and higher.

The module has been tested on:

CentOS 6
Ubuntu 12.04

Testing on other platforms has been light and cannot be guaranteed.

Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can’t access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

You can read the complete module contribution guide on the Puppet Labs wiki.

Current build status is:

Name		Name	Last commit message	Last commit date
Latest commit History 230 Commits
files		files
manifests		manifests
spec		spec
templates		templates
.fixtures.yml		.fixtures.yml
.gitignore		.gitignore
.nodeset.yml		.nodeset.yml
.rspec		.rspec
.rubocop.yml		.rubocop.yml
.travis.yml		.travis.yml
CHANGELOG		CHANGELOG
Gemfile		Gemfile
LICENSE		LICENSE
Modulefile		Modulefile
README.md		README.md
Rakefile		Rakefile
metadata.json		metadata.json

License

jwoffindin/puppetlabs-mcollective

Folders and files

Latest commit

History

Repository files navigation

mcollective

Table of Contents

Overview

Module Description

MCollective Terminology

Setup

What the mcollective module affects

Beginning with mcollective

Usage

I just want to run it, what's the minimum I need?

I'd like to secure the transport channel and authenticate users, how do I do that?

The ::mcollective:: class

Parameters

server

client

middleware

activemq_template

activemq_console

activemq_config

activemq_confdir

activemq_memoryUsage

activemq_storeUsage

activemq_tempUsage

rabbitmq_confdir

rabbitmq_vhost

delete_guest_user

manage_packages

version

ruby_stomp_ensure

main_collective

collectives

connector

securityprovider

psk

factsource

yaml_fact_path

excluded_facts

classesfile

rpcauthprovider

rpcauditprovider

registration

core_libdir

site_libdir

middleware_hosts

middleware_user

middleware_password

middleware_port

middleware_ssl_port

middleware_ssl

middleware_admin_user

middleware_admin_password

server_config_file

server_logfile

server_loglevel

server_daemonize

client_config_file

client_logger_type

client_loglevel

ssl_ca_cert

ssl_server_public

ssl_server_private

ssl_client_certs

mcollective::user defined type

Parameters

username

group

homedir

certificate

private_key

mcollective::plugin defined type

Parameters

name

source

package

The `::mcollective::` class

`server`

`client`

`middleware`

`activemq_template`

`activemq_console`

`activemq_config`

`activemq_confdir`

`activemq_memoryUsage`

`activemq_storeUsage`

`activemq_tempUsage`

`rabbitmq_confdir`

`rabbitmq_vhost`

`delete_guest_user`

`manage_packages`

`version`

`ruby_stomp_ensure`

`main_collective`

`collectives`

`connector`

`securityprovider`

`psk`

`factsource`

`yaml_fact_path`

`excluded_facts`

`classesfile`

`rpcauthprovider`

`rpcauditprovider`

`registration`

`core_libdir`

`site_libdir`

`middleware_hosts`

`middleware_user`

`middleware_password`

`middleware_port`

`middleware_ssl_port`

`middleware_ssl`

`middleware_admin_user`

`middleware_admin_password`

`server_config_file`

`server_logfile`

`server_loglevel`

`server_daemonize`

`client_config_file`

`client_logger_type`

`client_loglevel`

`ssl_ca_cert`

`ssl_server_public`

`ssl_server_private`

`ssl_client_certs`

`mcollective::user` defined type

`username`

`group`

`homedir`

`certificate`

`private_key`

`mcollective::plugin` defined type

`name`

`source`

`package`

`type`

`has_client`

`mcollective::actionpolicy` defined type

`name`

`default`

`mcollective::actionpolicy::rule` defined type

`name`

`agent`

`action`

`callerid`

`actions`

`facts`

`classes`

`mcollective::common::setting` defined type

`setting`

`value`

`order`

`mcollective::server::setting` defined type

`setting`

`value`