LATEST VERSION: 1.8.6 - CHANGELOG
RabbitMQ for PCF v1.6.20

RabbitMQ® for Pivotal Cloud Foundry Documentation

RabbitMQ is a fast and dependable open-source message server that 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, applications and devices, and creates lasting value by enabling rapid development of modern decentralized application and data architectures that can scale with your business needs. The Pivotal Cloud Foundry (PCF) installer enables cloud operators to deploy a RabbitMQ service in PCF. You can deploy the service as a single node or a cluster.

Product snapshot

Current RabbitMQ for PCF Details
Version: v1.6.20
Release Date: May 25th 2017
Software component version: RabbitMQ OSS v3.6.9
Compatible Ops Manager Version(s): v1.7.x, v1.6.x
Compatible Elastic Runtime Version(s): v1.7.x, v1.6.x
vSphere support? Yes
AWS support? Yes
OpenStack support? Yes
IPsec support? No

Upgrading to the Latest Version

Consider the following compatibility information before upgrading RabbitMQ for Pivotal Cloud Foundry.

Note: Upgrading from any version of the tile to v1.6.18+ will incur downtime as the RabbitMQ cluster is taken offline while the version of RabbitMQ is upgraded to v3.6.9.

Note: Upgrading from any v1.5.x tile to v1.6.x will involve taking the RabbitMQ cluster offline while the version of RabbitMQ is upgraded from v3.5.7 to v3.6.5.

Note: Customers will only be able to upgrade to v1.7.7 or later of the tile.

Note: You can not upgrade version v1.5.11 to v1.6.0, so you must use v1.6.1 or later.

Note: You can not upgrade version v1.5.21 to v1.6.13, so you must use v1.6.14 or later.

Note: All customers upgrading from v1.6.x to v1.6.5 or later versions of the tile should read the Additional upgrade steps for customers going from v1.6.x to v1.6.5 document located with the release on https://network.pivotal.io/products/pivotal-rabbitmq-service.

For more information, refer to the full Product Compatibility Matrix.

Ops Manager Version Supported Upgrades from Imported RabbitMQ Installation
v1.6.x and v1.5.x
  • From v1.5.0 through to v1.5.27, v1.6.0 through to v1.6.x
v1.7.x
  • From v1.5.9 through to v1.5.27, v1.6.0 through to v1.6.x

Features

  • Provision an instance of the RabbitMQ service, which corresponds to a unique RabbitMQ Vhost (virtual host)
  • Bind applications to an instance of the plan, providing unique credentials for each binding
  • Management dashboard access to PCF Operators and application developers
  • Deployment across multiple availability zones, with nodes striped across the AZs automatically
  • Enable SSL (Secure Sockets Layer) for the AMQP, MQTT, STOMP protocols
  • 2 node RabbitMQ cluster in a default deployment
  • 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
  • A default configurable queue policy is supplied in Ops Manager, but needs to be enabled on the deployment to take effect.
  • Automated upgrades of RabbitMQ for major, minor and patch releases
  • Configure the end point for the RabbitMQ Syslog
  • RabbitMQ and HAProxy metrics are exposed on the firehose

Install via Pivotal Ops Manager

To install RabbitMQ for PCF, follow the procedure for installing Pivotal Ops Manager tiles:

  1. Download the product file from Pivotal Network.
  2. Upload the product file to your Ops Manager installation.
  3. Click Add next to the uploaded product description in the Ops Manager Available Products view to add this product to your staging area.
  4. Click the newly added tile to review any configurable options.
  5. Click Apply Changes to install the service.

This product requires Ops Manager v1.5.0 or greater.

Using RabbitMQ in your application

RabbitMQ is shown in the services marketplace, either in the Apps Manager or through cf marketplace on the CLI.

Application developers can create an instance of the application with cf create-service p-rabbitmq standard <your name>. For this service an instance equals a Vhost on the RabbitMQ cluster.

Creating a binding gives the user permissions to access this Vhost and associated management dashboard.

Current Limitations

Limitations with the current RabbitMQ for PCF product include:

  • Availability Zone configuration cannot be changed once deployed.

We hope to address all of these limitations in future releases.

Known Issues

  • In versions 1.4.1 and 1.4.2, the manage button for your RabbitMQ instance in Apps Manager will not automatically log you into the RabbitMQ Dashboard. You need to press logout and then login with your username and password which can be obtained from inspecting the environment variables for your instance.
  • In versions 1.5.0 and 1.5.1, when performing a fresh installation or upgrade, if the Elastic Runtime system and application domains are different, then the Broker Registrar errand will fail. To resolve this, disable the errand and redeploy, then register the broker manually using the system domain route pivotal-rabbitmq-broker.system.domain. For more information about registering brokers see the CloudFoundry documentation.
  • In versions 1.5.0, 1.5.1, 1.5.2, 1.5.3, when performing a fresh installation or upgrade, if you have the rabbitmq_jsonrpc_channel or rabbitmq_jsonrpc_channel_examples plugins selected then the RabbitMQ nodes will fail to start. The plugins are no longer distributed with RabbitMQ and plugin validation was introduced in RabbitMQ 3.5.7, causing the nodes to fail to start. To resolve this issue you should install or upgrade to version 1.5.4 or above of the tile.
  • In the 1.5.x and 1.6.x tiles, it is not possible to install the RabbitMQ tile in multiAZ with multi-subnet networks.
  • IPsec will not work with any version of the RabbitMQ tile, and customers wishing to use it are advised to deploy their services to a different subnet.

Feedback

Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.

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