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:
There are 3 steps to determine if the tile is Supported. (see Resolution)
Three steps to qualify if the tile is Supported:
1.) Confirm the users Rabbit-MQ Software Component Version that is actively being used/deployed. This can be verified by running the collect-env script/KB from Rabbit-MQ deployment and server.
2.) Does the users deployed Software Component Version of Rabbit-MQ (confirmed by step 1 output) match any of the compatible versions mentioned in the users deployed Rabbit-MQ Tile release notes? Example below:
3.) Does the users Software Component Version that is included in their tile fall 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 Supported.
* If the RMQ tile version is EOGS (End of General Support), but the tiles Software Component Version is within Support life (according to official RMQ release info) and meets the above criteria, then the tile is eligible for Support.
Real World Examples: