Scope of Support for TANZU Rabbit-MQ tile
search cancel

Scope of Support for TANZU Rabbit-MQ tile

book

Article ID: 384206

calendar_today

Updated On: 02-21-2025

Products

Support Only for OpenSource RabbitMQ VMware RabbitMQ VMware Tanzu RabbitMQ Pivotal RabbitMQ Operations Manager VMware Tanzu Platform VMware Tanzu Application Service for VMs

Issue/Introduction

Rabbit-MQ (RMQ) is a messaging broker/service owned and supported by VMware/Broadcom that is compiled of 3 different offerings, each serving distinct use cases and deployment scenarios:

  1. The open-source RabbitMQ messaging broker
  2. Tanzu RabbitMQ
  3. RabbitMQ tile for Tanzu Platform Cloud Foundry / TAS. This article is specific to Rabbit-MQ tile , which is designed for ease of integration with Tanzu Platform for Cloud Foundry (formly known as TAS/Tanzu Application Service)

There are 2 steps to determine if the tile is Supported. (see Resolution)

Resolution

Steps to qualify if the tile is Supported:

 

1.)  Confirm the users Rabbit-MQ Software Component Version is listed as a compatible version on Rabbit-MQ Tile release notes? Example below:

 

 

2.)  Check if the users Software Component Version falls within the Support life from the official Rabbit-MQ.  This can be confirmed by checking the Release Information on Rabbits official site/docs.  

 

---------------------------------------------------------------------------------------------------------------------------------------

 

*If "no" to any of the above, then it is not supported. Forked, modified or custom compiled versions of tiles, stemcells, buildpacks and Bosh releases are not eligible for support (see links below).

 

*If "yes" to all of the above, then the RMQ tile version is within Scope of Support (TANZU).

 

 

Additional Information

  1. Note: 'modification/customization of the tile' is unsupported.  This type of practice (Modifying Tile/Code) falls outside of TAS Scope of Support and Tanzu Official Terms and Conditions.
  2. To collect detailed additional details of rmq, users can see the steps mentioned in the collect-env script/KB.