rabbitmq-server job from cf-rabbitmq/230.0.0
Github source:
65fa7ac
or
master branch
Properties¶
rabbitmq-server
¶
administrators
¶
broker
¶
password
¶RabbitMQ admin password for broker
username
¶RabbitMQ admin username for broker
management
¶
password
¶RabbitMQ admin password for operator
username
¶RabbitMQ admin username for operator
cluster_partition_handling
¶Cluster partition recover mode property. Valid values are: pause_minority, autoheal
- Default
pause_minority
config
¶RabbitMQ configuration (base64 encoded)
- Default
W10u
cookie
¶Erlang cookie used by RabbitMQ nodes and rabbitmqctl
disk_alarm_threshold
¶The threshold in bytes of free disk space at which rabbitmq will raise an alarm
- Default
'{mem_relative,0.4}'
fd_limit
¶The file descriptor limit for the RabbitMQ process
- Default
300000
force-unsafe-upgrade
¶
disable-version-checking
¶This property is for support cases only. Leave as false unless you are prepared to get your cluster in an unrecoverable state, including complete data loss.
- Default
false
ips
¶List of IPs of all RabbitMQ nodes. Attention! This overrides the ips provided by the bosh links.
load_definitions
¶Definitions to be loaded by RabbitMQ at startup
plugins
¶List of RabbitMQ plugins
ports
¶List of ports on which the RabbitMQ cluster accepts connections
restart_statsdb_cron_schedule
¶Schedule of when to restart the RabbitMQ StatsDB.
ssl
¶
cacert
¶RabbitMQ server CA certificate
cert
¶RabbitMQ server certificate
fail_if_no_peer_cert
¶Should RabbitMQ server reject connection if there is no peer cert
- Default
false
key
¶RabbitMQ server private key
security_options
¶SSL security options (currently only ‘enable_tls1_0’)
- Default
[]
verification_depth
¶Peer verification depth used by RabbitMQ server
- Default
5
verify
¶Peer verification method used by RabbitMQ server
- Default
false
use_native_clustering_formation
¶Should RabbitMQ server use the native clustering intead of clusterer plugin
- Default
true
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-server/
directory
(learn more).
bin/add-rabbitmqctl-to-path
(fromadd-rabbitmqctl-to-path.bash
)bin/cleanup-http-logs
(fromcleanup-http-logs.bash
)bin/cluster-check
(fromcluster-check.bash
)bin/drain
(fromdrain.bash
)bin/ensure-rabbitmq-statsdb-restart-cron
(fromensure-rabbitmq-statsdb-restart-cron.erb
)bin/kill-with-fire
(fromkill-with-fire.bash
)bin/node-check
(fromnode-check.bash.erb
)bin/node_name_migration.sh
(fromnode_name_migration.sh
)bin/plugins.sh
(fromplugins.sh.erb
)bin/post-deploy
(frompost-deploy.bash
)bin/pre-start
(frompre-start.bash
)bin/rabbitmq-server.init
(fromrabbitmq-server.init.bash
)bin/setup.sh
(fromsetup.sh.erb
)etc/cacert.pem
(fromcacert.pem.erb
)etc/cert.pem
(fromcert.pem.erb
)etc/config
(fromconfig.erb
)etc/definitions.json
(fromdefinitions.json.erb
)etc/key.pem
(fromkey.pem.erb
)etc/rabbitmq.config
(fromrabbitmq.config.erb
)etc/users
(fromusers.erb
)lib/delete_old_files.bash
(fromdelete_old_files.bash
)lib/prepare-for-upgrade.bash
(fromprepare-for-upgrade.bash
)lib/rabbitmq-config-vars.bash
(fromrabbitmq-config-vars.bash.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.