Skip to content

rabbitmq-broker job from cf-rabbitmq/84

Github source: 8ef88300 or master branch

Properties

cf

domain

Domain shared by the UAA and CF API, e.g. ‘10.244.0.34.xip.io’

nats

host

Hostname/IP of NATS

password

The password to use when authenticating with NATS

port

Port that NATS listens on

username

The user to use when authenticating with NATS

rabbitmq-broker

cc_endpoint

URL for CC

logging

level

Logging level

Default
info
print_stack_traces

Should boot exception handlers print full stack traces?

Default
false

rabbitmq

administrator
password

The password used to access an admin account of the Rabbit servers

username

The username used to access an admin account of the Rabbit servers

hosts

List of IPs of the Rabbit servers (maybe proxied) upon which to allocate resources

management_domain

Domain that will be used to access RabbitMQ management UI, typically the system CF/CC domain.

mirrored_queues
enabled

Enable mirrored queues as default policy

Default
true
policy_name

Mirrored queues default policy name

Default
mirrored_queues
ssl

Set to true if RabbitMQ cluster is configured to use TLS/SSL

Default
false

service

password

Password used by Cloud Controller for authentication

url

The URL to the service gateway

username

Username used by Cloud Controller for authentication

uaa_client

client_id

Client ID for UAA

password

Services Password

username

Services Username

uaa_endpoint

URL for UAA

route-registrar

target_ip

IP address RabbitMQ management UI requests will be routed to, typically that of RabbitMQ HAproxy VM

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/rabbitmq-broker/ directory (learn more).

  • bin/rabbitmq_broker_ctl (from broker_ctl.erb)
  • bin/route_registrar_ctl (from route_registrar_ctl.erb)
  • config/rabbitmq_broker.yml (from broker_config.yml.erb)
  • config/registrar_settings.yml (from registrar_settings.yml.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.