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.

ceph-osd-replication-count | int

Default: 3

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).

cluster-partition-handling | string

Default: ignore

RabbitMQ offers three ways to deal with network partitions automatically. Available modes: ignore - Your network is reliable. All your nodes are in a rack, connected with a switch, and that switch is also the route to the outside world. You don't want to run any risk of any of your cluster shutting down if any other part of it fails (or you have a two node cluster). pause_minority - Your network is maybe less reliable. You have clustered across 3 AZs in EC2, and you assume that only one AZ will fail at once. In that scenario you want the remaining two AZs to continue working and the nodes from the failed AZ to rejoin automatically and without fuss when the AZ comes back. autoheal - Your network may not be reliable. You are more concerned with continuity of service than with data integrity. You may have a two node cluster. For more information see http://www.rabbitmq.com/partitions.html.

ha-bindiface | string

Default: eth0

Default network interface on which HA cluster will bind to communication with the other members of the HA Cluster.

ha-mcastport | int

Default: 5406

Default multicast port number that will be used to communicate between HA Cluster nodes.

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).

harden | string

Apply system hardening. Supports a space-delimited list of modules to run. Supported modules currently include os, ssh, apache and mysql.

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.

management_plugin | boolean

enable the management plugin

max-cluster-tries | int

Default: 3

Number of tries to cluster with other units before giving up and throwing a hook error.

min-cluster-size | int

Minimum number of units expected to exist before charm will attempt to form a rabbitmq cluster.

mirroring-queues | boolean

Default: True

When set to true the 'ha-mode: all' policy is applied to all the exchages that match the expression '^(?!amq\.).*'

nagios_context | string

Default: juju

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.

nagios_servicegroups | string

A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup

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.

queue_thresholds | string

Default: [['\*', '\*', 100, 200]]

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

rbd-name | string

Default: rabbitmq1

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.

rbd-size | string

Default: 5G

Default rbd storage size to create when setting up block storage. This value should be specified in GB (e.g. 100G).

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.

ssl | string

Default: off

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.

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).

ssl_cert | string

X.509 certificate in base64 PEM format (starts "-----BEGIN CERTIFICATE-----")

ssl_enabled | boolean

(DEPRECATED see 'ssl' config option.) enable SSL

ssl_key | string

private unencrypted key in base64 PEM format (starts "-----BEGIN RSA PRIVATE KEY-----")

ssl_port | int

Default: 5671

SSL port

stats_cron_schedule | string

Default: */5 * * * *

Cron schedule used to generate rabbitmq stats. If unset no stats will be generated

use-syslog | boolean

If True, services that support it will log to syslog instead of their normal log location.

vip | string

Virtual IP to use to front rabbitmq in ha configuration

vip_cidr | int

Default: 24

Netmask that will be used for the Virtual IP

vip_iface | string

Default: eth0

Network Interface where to place the Virtual IP

James Page Rabbitmq Server Bug1590085