Allow multiple RabbitMQ clusters per CF about cf-rabbitmq-release

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/98229744.

[benlaplanche]

Hi Rick,

To confirm the scenario in which you are experiencing the issue.
It sounds like you want to deploy this cf-rabbitmq-release multiple times against a single CF, to achieve having multiple RabbitMQ clusters?

Is that correct?
Thanks
Ben

[rickfarmer]

Thanks for the response, Ben. Yes, that is exactly the scenario the client would like to achieve.

[michaelklishin]

Does #10 resolve this? or only partially address?

[davidehringer]

This is something we are very interested in as well (as PCF users).

[davidehringer]

Let me clarify our interest here as we don't necessarily need this specific solution but have a need that this could address. What we are really looking for is to be able to provide some form of dedicated service instances that can be used by apps that need to have a guarantee that won't be affected by a noisy neighbor. This is one way that could be done. Having a dedicated plan option would be another.

[avade]

Thanks for the context David, I am the product manager for the PCF RabbitMQ tile at Pivotal.

The BOSH release now supports multiple cf-rabbitmq deployments running in the same CF / BOSH environment. This is not recommended or supported but has helped out some of the OSS users. This is not supported in PCF.

We are currently investigating how best to support 'dedicated' cluster instances provisioned via the same broker in a PCF environment.

[iamralch]

@davidehringer:

We exposed the following properties:

rabbitmq-broker.service.name:
    description: "Name of the service"
    default: "p-rabbitmq"
  rabbitmq-broker.service.display_name:
    description: "Service offering display name in Apps Manager"
    default: "RabbitMQ"
  rabbitmq-broker.service.offering_description:
    description: "Service offering long description"
    default: "RabbitMQ is a robust and scalable high-performance multi-protocol messaging broker."
  rabbitmq-broker.service.uuid:
    description: "UUID of the service"
    default: "163b47c6-a2f3-43b1-97f7-b83b37ec8ad3"
  rabbitmq-broker.service.plan_uuid:
    description: "UUID of the plan"
    default: "4e816145-4e71-4e24-a402-0c686b868e2d"

That allows deploying multiple RabbitMQ clusters. I am closing this issue.