A quick way to get a mcollective network built for testing or evaluating MCollective.

This consists of a Vagrant file and a few very simple Puppet Modules that does the simplest possible thing to get a MCollective setup going.

This setup uses Redis for the middleware, discovery and registration thus providing a very light weight and fast setup.

This will setup the latest MCollective along with the following plugins:

• Package Agent
• Service Agent
• Puppet Agent
• File Manager Agent
• NRPE Agent

NRPE is installed on all machines with checks check_load, check_disks and check_swap

Additionally there will be a simple Puppet Master deployed on the middleware node which as its site.pp will use the file in deploy/modules/puppet/files/site.pp. By default all this does is sleep a random period, enough to be able to test and demo the MCollective Puppet Agent

Assuming you have a working Vagrant setup on your system it should be real simple to get going:

$ git clone git://github.com/ripienaar/mcollective-vagrant.git
$ cd mcollective-vagrant

You should now edit the Vagrantfile and adjust the constants at the top to your tastes:

$ vi Vagrantfile
$ vagrant up

$ vagrant ssh middleware
$ mco ping
node0.example.net                        time=25.18 ms
middleware.example.net                   time=26.50 ms

---- ping statistics ----
2 replies max: 26.50 min: 25.18 avg: 25.84
$ mco package status mcollective

 * [ ============================================================> ] 2 / 2

        node0.example.net: mcollective-2.2.3-1.el6.noarch
   middleware.example.net: mcollective-2.2.3-1.el6.noarch

Summary of Arch:

   noarch = 2

Summary of Ensure:

   2.2.3-1.el6 = 2


Finished processing 2 / 2 hosts in 523.95 ms

Please read the MCollective CLI Usage documentation to see how it works and what you can do with it. The guide and the links to the modules in the first section of this file will quickly help you explore MCollective.

The Puppet modules used to install the boxen are in the deploy/modules directory. The mcollective module has files/lib and everything in there will just be recursively copied to the nodes. So if you want to test some plugin you're working on just copy it in there and run vagrant provision

The EPEL and Puppet Labs repositories are on the machines and all of the plugins mentioned in the first section of this document are installed from there. Some plugins though like the Redis ones aren't yet available at Puppet Labs so for now they are deployed from the module lib dir.

There is a package repo in deploy/packages with some dependencies and this repo is added to all the nodes, so if you drop a new package in there just run createrepo in that directory and it would be available to all the machines.

I'd love to see the various things like the Puppet setup done using proper modules from the forge so PRs would be appreciated

R.I.Pienaar / [email protected] / @ripienaar / http://devco.net/