Description

RabbitMQ is an implementation of AMQP, the emerging standard for high
performance enterprise messaging. The RabbitMQ server is a robust and
scalable implementation of an AMQP broker.

Configuring SSL

Generate an unencrypted RSA private key for the servers and a certificate:

openssl genrsa -out rabbit-server-privkey.pem 2048

Get an X.509 certificate. This can be self-signed, for example:

openssl req -batch -new -x509 -key rabbit-server-privkey.pem -out rabbit-server-cert.pem -days 10000

Deploy the service:

juju deploy rabbitmq-server rabbit

Enable SSL, passing in the key and certificate as configuration settings:

juju set rabbit ssl_enabled=True ssl_key="cat rabbit-server-privkey.pem" ssl_cert="cat rabbit-server-cert.pem"

To change the source that the charm uses for packages:

juju set rabbit source="cloud:precise-icehouse"

This will enable the Icehouse pocket of the Cloud Archive (which contains a new version of RabbitMQ) and upgrade the install to the new version.

The source option can be used in a few different ways:

source="ppa:james-page/testing" - use the testing PPA owned by james-page
source="http://myrepo/ubuntu main" - use the repository located at the provided URL

The charm also supports use of arbitary archive key's for use with private repositories:

juju set rabbit key="C6CEA0C9"

Note that in clustered configurations, the upgrade can be a bit racey as the services restart and re-cluster; this is resolvable using:

juju resolved --retry rabbitmq/1

Configuration

ssl_key
(string) private unencrypted key in base64 PEM format (starts "-----BEGIN RSA PRIVATE KEY-----")
vip_iface
(string) Network Interface where to place the Virtual IP
eth0
ha-vip-only
(boolean) By default, without pairing with hacluster charm, rabbitmq will deploy in active/active/active... HA. When pairied with hacluster charm, it will deploy as active/passive. By enabling this option, pairing with hacluster charm will keep rabbit in active/active setup, but in addition it will deploy a VIP that can be used by services that cannot work with mutiple AMQPs (like Glance in pre-Icehouse).
stats_cron_schedule
(string) Cron schedule used to generate rabbitmq stats. If unset no stats will be generated
*/5 * * * *
access-network
(string) The IP address and netmask of the 'access' network (e.g., 192.168.0.0/24) . This network will be used for access to RabbitMQ messaging services.
vip
(string) Virtual IP to use to front rabbitmq in ha configuration
management_plugin
(boolean) enable the management plugin
use-syslog
(boolean) If True, services that support it will log to syslog instead of their normal log location.
source
(string) Optional configuration to support use of additional sources such as: . - ppa:myteam/ppa - cloud:precise-proposed/folsom - http://my.archive.com/ubuntu main . The last option should be used in conjunction with the key configuration option.
mirroring-queues
(boolean) When set to true the 'ha-mode: all' policy is applied to all the exchages that match the expression '^(?!amq\.).*'
True
ha-mcastport
(int) Default multicast port number that will be used to communicate between HA Cluster nodes.
5406
ssl_port
(int) SSL port
5671
ssl_enabled
(boolean) (DEPRECATED see 'ssl' config option.) enable SSL
prefer-ipv6
(boolean) If True enables IPv6 support. The charm will expect network interfaces to be configured with an IPv6 address. If set to False (default) IPv4 is expected. . NOTE: these charms do not currently support IPv6 privacy extension. In order for this charm to function correctly, the privacy extension must be disabled and a non-temporary address must be configured/available on your network interface.
nagios_servicegroups
(string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
queue_thresholds
(string) List of RabbitMQ queue size check thresholds. Interpreted as YAML in format [<vhost>, <queue>, <warn>, <crit>] - ['/', 'queue1', 10, 20] - ['/', 'queue2', 200, 300] Wildcards '*' are accepted to monitor all vhosts and/or queues
[['\*', '\*', 100, 200]]
ssl
(string) Enable SSL connections on rabbitmq, valid values are 'off', 'on', 'only'. If ssl_key, ssl_cert, ssl_ca are provided then then those values will be used. Otherwise the service will act as its own certificate authority and pass its ca cert to clients. For HA or clustered rabbits ssl key/cert must be provided.
off
key
(string) Key ID to import to the apt keyring to support use with arbitary source configuration from outside of Launchpad archives or PPA's.
ssl_cert
(string) X.509 certificate in base64 PEM format (starts "-----BEGIN CERTIFICATE-----")
ceph-osd-replication-count
(int) This value dictates the number of replicas ceph must make of any object it stores within the rabbitmq rbd pool. Of course, this only applies if using Ceph as a backend store. Note that once the rabbitmq rbd pool has been created, changing this value will not have any effect (although it can be changed in ceph by manually configuring your ceph cluster).
3
rbd-size
(string) Default rbd storage size to create when setting up block storage. This value should be specified in GB (e.g. 100G).
5G
nagios_context
(string) Used by the nrpe-external-master subordinate charm. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
juju
rbd-name
(string) The name that will be used to create the Ceph's RBD image with. If the image name exists in Ceph, it will be re-used and the data will be overwritten.
rabbitmq1
ssl_ca
(string) Certificate authority cert that the cert. Optional if the ssl_cert is signed by a ca recognized by the os. Format is base64 PEM (concatenated certs if needed).
max-cluster-tries
(int) Number of tries to cluster with other units before giving up and throwing a hook error.
3
min-cluster-size
(int) Minimum number of units expected to exist before charm will attempt to form a rabbitmq cluster.
ha-bindiface
(string) Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.
eth0
vip_cidr
(int) Netmask that will be used for the Virtual IP
24