VMware Tanzu RabbitMQ for VMs

Note: Pivotal Platform is now part of VMware Tanzu. In v1.20 and later, VMware Tanzu RabbitMQ [VMs] is named VMware Tanzu RabbitMQ for VMs.

About VMware Tanzu RabbitMQ for VMs

Tanzu RabbitMQ enables app developers to provision and use the RabbitMQ message broker with a single command.

Tanzu RabbitMQ supports two types of service, an on-demand service and a pre-provisioned service.

This table summarizes the main differences between the two:

VMs it Runs On How VMs are Created Metrics Name Prefix
On-Demand Service Dedicated VM that serves a single service instance. For more information, see Unlocking the Power of On-Demand VMware Tanzu RabbitMQ for VMs. The BOSH Director creates each VM on-demand when an app developer creates a service instance. p.rabbitmq (with a dot)
Pre-Provisioned Service Multi-tenant VMs shared by apps across your deployment The BOSH Director creates all VMs when operator deploys or updates service p-rabbitmq (with a dash)

Note: For most new apps, VMware recommends that you use on-demand services instead of pre-provisioned services. The on-demand service offering isolates workloads by creating a separate VM for each service instance.

Overview of On-Demand Instances

In Tanzu RabbitMQ versions before v1.8.0, the Tanzu RabbitMQ service instances correspond to a unique RabbitMQ virtual host on the multi-tenant RabbitMQ cluster. Tanzu RabbitMQ v1.8.0 introduced on-demand service broker (ODB) support. That means you can create a new single-tenant cluster and dedicate it to a single app.

For more information, see Unlocking the Power of On-Demand VMware Tanzu RabbitMQ for VMs and 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 Tanzu RabbitMQ.

Element Details
Version 1.20.2
Release date October 21, 2020
Software component version RabbitMQ OSS 3.8.8
Compatible Ops Manager versions 2.10, 2.9, 2.8, and 2.7
Compatible VMware Tanzu Application Service for VMs versions 2.10, 2.9, 2.8, and 2.7
IaaS support AWS, Azure, GCP, OpenStack, and vSphere
IPsec support No

Features

On-Demand

  • Create up to 5 different on-demand Tanzu RabbitMQ plans which can be provisioned through the Marketplace
  • Choose whether a plan has 1, 3, 5, or 7 nodes
  • Default resource sizes in plans to guide selection
  • More control over which Orgs and Spaces have visibility of each configured plan
  • Bind apps to an instance of the plan, providing unique credentials for each binding
  • Management UI access to app developers
  • Deployment into an availability zone (AZ) specified by the plan
  • Enable Transport Layer Security (TLS) for the AMQP protocol
  • Automated upgrades of RabbitMQ for major, minor, and patch releases (see release notes for downtime requirements)
  • Tanzu RabbitMQ syslog forwarding configuration inherited from the pre-provisioned configuration
  • Tanzu RabbitMQ metrics are exposed on the Firehose
  • Run smoke tests for on-demand plans on plan 1
  • Errands are run on co-located VMs to decrease deployment times

For more information, see Unlocking the Power of On-Demand VMware Tanzu RabbitMQ for VMs.

Pre-Provisioned

  • Provision an instance of the RabbitMQ service, which corresponds to a unique RabbitMQ virtual host
  • Bind apps to an instance of the plan, providing unique credentials for each binding
  • Management UI access to operators and app developers
  • Deployment across multiple AZs, with nodes striped across the AZs automatically
  • Enable SSL (Secure Sockets Layer) for the AMQP, MQTT, STOMP protocols
  • HA Proxy 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. For downtime requirements, see Downtime When Upgrading.
  • Configure the end point for the Tanzu RabbitMQ syslog
  • RabbitMQ and HA Proxy metrics are exposed on the Firehose
  • Syslog forwarding on by default
  • Errands are run on co-located VMs to decrease deployment times

Release Notes and Known Issues

Check the release notes for your release version for important information and known issues. To see release notes for another version, select the version from the dropdown at the top of the page.

Tanzu RabbitMQ and Other On-Demand Services

As well as Tanzu RabbitMQ, other services offer on-demand service plans. These plans let developers provision service instances when they want.

These contrast with the older pre-provisioned service plans, which require operators to provision the service instances during installation and configuration through the service tile UI.

The following table lists which service tiles offer on-demand and pre-provisioned service plans:

Service tile Standalone product related to the service Supports on-demand Supports pre-provisioned
VMware Tanzu RabbitMQ for VMs Pivotal RabbitMQ Yes Yes. Only recommended for test environments.
Redis for VMware Tanzu Application Service Redis Yes Yes (shared-VM plan). Only recommended for test environments.
VMware Tanzu SQL with MySQL for VMs MySQL Yes
No
VMware Tanzu GemFire for VMs VMware GemFire Yes No


For services that offer both on-demand and pre-provisioned plans, you can choose the plan you want to use when configuring the tile.

Feedback

Please send any issue reports, feature requests, or questions to the Feedback list.

Was this helpful?
What can we do to improve?