Turning Off the Pre-Provisioned Service
Note: Pivotal Platform is now part of VMware Tanzu. In v1.19 and later, RabbitMQ for Pivotal Platform is named VMware Tanzu RabbitMQ [VMs].
This topic provides instructions on how to turn off the pre-provisioned service. If you are not planning to use the pre-provisioned service, disable it. Disabling the pre-provisioned service broker means that no instances for the pre-provisioned service will be deployed. This, in turn, saves money.
To turn off the pre-provisioned service manually, do the following:
If you are upgrading to VMware Tanzu RabbitMQ [VMs] v1.14, or have previously configured the pre-provisioned service, de-register the pre-provisioned service broker by running the following command:
bosh -d p-rabbitmq-GUID run-errand broker-deregistrar
GUIDis the VMware Tanzu RabbitMQ deployment GUID.
$ bosh -d p-rabbitmq-aeaea3ac-aba5-a6a4-afa7-aba8a0a7a0a9 run-errand broker-deregistrar
The broker-deregistrar errand removes the
p-rabbitmqservice offering from the Marketplace.
From the Ops Manager Installation Dashboard, click the VMware Tanzu RabbitMQ tile.
In the VMware Tanzu RabbitMQ tile, click Settings.
Click Pre-Provisioned RabbitMQ, and click No under the Deploy Pre-Provisioned service offering.
Click Save, and then return to the Ops Manager Installation Dashboard.
Click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.
Click Apply Changes to redeploy and disable the pre-provisioned service.
You can turn off the pre-provisioned service if you are using automation such as scripts or pipelines to configure the VMware Tanzu RabbitMQ tile.
To do this, set the
.properties.multitenant_support property to
For more information about properties, see Configuring products.
When you make this change, Ops Manager automatically sets instance counts to
For instance groups related to the pre-provisioned service, such as
rabbitmq-haproxy, if you modify instance
counts to a non-zero value, BOSH fails to deploy the tile.
Although the fields are inactive in the UI, this does not prevent you
from overwriting instance counts through the API.
Only set instance counts to
0 or do not set them at all.