LATEST VERSION: 1.9.4 - CHANGELOG
RabbitMQ for PCF v1.9.4

RabbitMQ for PCF

About RabbitMQ for PCF

RabbitMQ for Pivotal Cloud Foundry (PCF) enables PCF app developers to provision and use the RabbitMQ message broker with a single command.

As of version 1.8, RabbitMQ for PCF supports two types of service, an on-demand service and a pre-provisioned service. This table summarizes the main differences between the two:

Available Since VMs it Runs On How VMs are Created Metrics Name Prefix
On-Demand Service v1.8 Dedicated VM that serves a single service instance PCF creates each VM on-demand when app developer creates service instance p.rabbitmq (with a dot) in future versions. As of v1.8.2, emitted asp-rabbitmq, a known issue.
Pre-Provisioned Service v1.2 Multi-tenant VMs shared by apps across PCF deployment PCF creates all VMs when operator deploys or updates service p-rabbitmq (with a dash)

This RabbitMQ for PCF v1.8 documentation describes both service types. Documentation for RabbitMQ for PCF v1.7 and earlier only describes a pre-provisioned service.

What are Dedicated Instances

In RabbitMQ for PCF versions before v1.8.0, the RabbitMQ service instances correspond to a unique RabbitMQ Vhost on the multi-tenant RabbitMQ cluster. RabbitMQ for PCF v1.8.0 introduced On-Demand Broker (ODB) support. That means that a new, single-tenant, cluster can be created and dedicated to a single app.

For more information, see On-Demand Service Architecture.

About RabbitMQ

RabbitMQ is a fast and dependable open-source message server, which supports a wide range of use cases including reliable integration, content-based routing and global data delivery, and high-volume monitoring and data ingestion.

Emerging as the de facto standard for cloud messaging, RabbitMQ is used for efficient communication between servers, apps and devices, and creates lasting value by enabling rapid development of modern decentralized app and data architectures that can scale with your business needs.

Product Snapshot

The following table provides version and version-support information about RabbitMQ for PCF.

Element Details
Version v1.9.4
Release date August 15th, 2017
Software component version RabbitMQ OSS v3.6.10
Compatible Ops Manager version(s) v1.10.x
Compatible Elastic Runtime version(s) v1.10.3 and later
IaaS support AWS, Azure, GCP, OpenStack, and vSphere
IPsec support No

Features

On-Demand

  • Provision on-demand single node dedicated instances of RabbitMQ with a unique RabbitMQ Vhost (virtual host)
  • Bind apps to an instance of the plan, providing unique credentials for each binding
  • Management dashboard access to app developers
  • Deployment into an availability zone specified by the plan
  • Automated upgrades of RabbitMQ for major, minor, and patch releases (see release notes for downtime requirements)
  • RabbitMQ Syslog forwarding configuration inherited from the pre-provisioned configuration
  • RabbitMQ metrics are exposed on the firehose

Pre-Provisioned

  • Provision an instance of the RabbitMQ service, which corresponds to a unique RabbitMQ Vhost (virtual host)
  • Bind apps to an instance of the plan, providing unique credentials for each binding
  • Management dashboard access to PCF Operators and app developers
  • Deployment across multiple availability zones, with nodes striped across the AZs automatically
  • Enable SSL (Secure Sockets Layer) for the AMQP, MQTT, STOMP protocols
  • HAProxy load balancer across all nodes to balance connections
  • Plugin configuration can be easily changed at any time and the cluster redeployed and updated
  • The cluster topology can be changed and easily scaled out
  • Automated upgrades of RabbitMQ for major, minor, and patch releases (see release notes for downtime requirements)
  • Configure the end point for the RabbitMQ Syslog
  • RabbitMQ and HAProxy metrics are exposed on the firehose
  • Syslog forwarding on by default

Known Issues

  • Cannot scale-out if Erlang Cookie is not specified
  • Changing Erlang Cookie value results in failed deployment
  • When errand run rules are set to “When Changed”, Ops Manager may not run the errands when the tile has relevant changes. For more information, see Managing Errands in Ops Manager. Pivotal recommends leaving the default run rule set to On.

Feedback

Please provide any bugs, feature requests, or questions to the PCF Feedback list.

Create a pull request or raise an issue on the source for this page in GitHub