rabbitmq worker ^#1

Supports: precise

Description

Deploys a rabbitmq worker from a given bzr branch.

Tags:
app-servers ›

Describe the intended usage of this charm and anything unique about how
this charm relates to others here.

This README will be displayed in the Charm Store, it should be either Markdown or RST. Ideal READMEs include instructions on how to use the charm, expected usage, and charm features that your audience might be interested in. For an example of a well written README check out Hadoop: http://jujucharms.com/charms/precise/hadoop

Here's an example you might wish to template off of:

Overview

This charm provides (service) from (service homepage). Add a description here of what the service itself actually does.

Usage

Step by step instructions on using the charm:

juju deploy servicename

and so on. If you're providing a web service or something that the end user needs to go to, tell them here, especially if you're deploying a service that might listen to a non-default port.

You can then browse to http://ip-address to configure the service.

Configuration

The configuration options will be listed on the charm store, however If you're making assumptions or opinionated decisions in the charm (like setting a default administrator password), you should detail that here so the user knows how to change it immediately, etc.

Contact Information

Though this will be listed in the charm store itself don't assume a user will know that, so include that information here:

Author:
Report bugs at: http://bugs.launchpad.net/charms/+source/charmname
Location: http://jujucharms.com/charms/distro/charmname

Be sure to remove the templated parts before submitting to https://launchpad.net/charms for inclusion in the charm store.

Configuration

amqp-user: (string) The user to log into the rabbitMQ server.; workerbee
amqp-vhost: (string) The vhost in the rabbitMQ server.; /
available_code: (string) A list of code deployment URLs to keep around. Any versions found locally not in this list will be removed.
cron_cmd: (string) Allow a command to be run periodically by cron. This can be specified as a relative path to the root directory of your tarball.
cron_schedule: (string) Cron-format schedule interval to run the command (m h dom mon dow); 0 0 * * *
current_code: (string) A URL to a tarball of the code
gid: (string) Group to run service as; nogroup
install_keys: (string) YAML list of GPG keys for installation sources, as a string. For apt repository URLs, use the public key ID used to verify package signatures. For other sources such as PPA, use null. This list must have the same number of elements as install_sources, even if the key items are all empty string. An example to go with the above for install_sources: install_keys: | - null - null - "a1b2c3d4"
install_root: (string) The root directory the service will be installed in; /srv/
install_sources: (string) YAML list of additional installation sources, as a string. The number of install_sources must match the number of install_keys. For example: install_sources: | - "ppa:project1/ppa" - "cloud:precise-proposed/folsom" - "http://example.com/repo precise main"
json_status_port: (int) Optional port a worker might expose for json status checks; 8080
main: (string) The worker script to run as a service. Can include paths relative to root of the local source tree
nagios_check_health_params: (string) The parameters to pass to the nrpe plugin check_health.
nagios_check_http_params: (string) The parameters to pass to the nrpe plugin check_http.
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-postgresql-0 If you\'re running multiple environments with the same services in them this allows you to differentiate between them.; rabbitmq-worker
packages: (string) Packages required for this service
pip-packages: (string) Pip packages required for this service
uid: (string) User to run service as; nobody
unit-config: (string) base64 encoded string to hold configuration information for the unit. The contents will be written to a file named <install_root>/<unit>/unit_config where <unit> is the location the branch is extracted to.