Forge Home

rabbitmq

Minimalistic RabbitMQ module

19,734 downloads

19,231 latest version

3.1 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.1.1 (latest)
  • 0.1.0
released Mar 17th 2015
This version is compatible with:
  • Puppet Enterprise 3.x
  • Puppet >=2.7.20 <4.0.0
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'thias-rabbitmq', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add thias-rabbitmq
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install thias-rabbitmq --version 0.1.1

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.

Download

Documentation

thias/rabbitmq — version 0.1.1 Mar 17th 2015

puppet-rabbitmq

Overview

Install and enable RabbitMQ.

  • rabbitmq : Class to install and enable the server.

If you are looking for a more complete module, check out the official PuppetLabs RabbitMQ module. This module is made to be minimalistic, with few external requirements : stdlib, selinux (optional), nothing more.

It has been initially tested only with Red Hat Enterprise Linux 7.

Examples

include '::rabbitmq'

Once the RabbitMQ server is up and running, it initially needs to be manually configured. This is where other modules might go beyond this basic one. See rabbitmqctl(1) for more information.

If you already have an existing configuration, you should be able to pass it as-is using source or content type parameters, with your own files or templates (here we use an included example cluster template ) :

$cluster_nodes = [ 'rabbit@node1', 'rabbit@node2' ]
class { '::rabbitmq':
  rabbitmq_config_content => template('rabbitmq/rabbitmq.config-cluster.erb'),
  rabbitmq_env            => {
    'NODENAME'     => "rabbit@${::hostname}.example.lan",
    'USE_LONGNAME' => 'true',
  },
  enabled_plugins         => [ 'rabbitmq_management' ],
}