Hello, I would like to have more than one tile installation for Redis in the OpsManager -- say for instance one for development and test purposes and other for Production. Could you kindly provide the documentations related to this? Thank you!

[Yashaswini Raj]

 

[Daniel Mikusa]

When you look on Pivotal Network at a service, some services will have a download option for a "replicator" tool. This tool can be used to replicate the tile, so that you can upload to Ops Manager multiple times. One example of a tile that supports this is RabbitMQ. I do not see this option for the Pivotal Redis tile though, sorry.

 

What you might be able to do is to create separate service plans, one for dev/test and one for prod. You could then selectively make those service plans available to specific orgs & spaces. It's not exactly the same as having multiple tiles, but it might work well enough.

 

@Stephen Carter​ - Do you happen to know if there's any way to have multiple copies of the Redis tile? or what other similar options might be available?

[Daniel Mikusa]

>When you say “separate service plans”, do I understand it right that you refer to having different configurations, say for instance, the on-demand services, and enabling it for specific orgs and spaces?

 

Yes that's right. You can configure up to three different on-demand service plans. See step #6 here.

 

https://docs.pivotal.io/redis/1-13/installing.html#on-demand-config

 

You can then use `cf enable-service-access` to enable/disable those plans for specific orgs & spaces.

 

Again, it's not the same as having two copies of the tile, but it's an option that's available now and it would let you have different plans for say your dev & prod users.

 

[Yashaswini Raj]

Hi Daniel, Thanks for the quick response and interesting information! When you say “separate service plans”, do I understand it right that you refer to having different configurations, say for instance, the on-demand services, and enabling it for specific orgs and spaces? If so, as you rightly mention, it is not exactly the same as having multiple tiles! Please correct me here if my understanding regarding the service plans you mentioned is wrong. Best Regards, Yashaswini Raj

[Stephen Carter]

Hi Dan, regarding the Tile Replicator, that was only designed for RabbitMQ because we had many customers who were in need of multiple separate clusters.

But now On Demand (ODB) is the recommended way to deploy multiple separate servers/cluster.

The Tile Replicator will be retired.

 

Hi Yashaswini, you should not need separate instances of the tile in order to achieve what you want.

The tile uses the ODB so each time a user creates a new service instance it a completely new VM will be created. There is no sharing of the resources.

 

Is there another reason why you feel like you need separate tiles?

 

 

Kind regards,

Stephen

[Yashaswini Raj]

Hi Daniel, Hi Stephen, That should serve the purpose ideally then. We were also thinking of having multiple tiles for testing purposes in the same opsmanager during upgrades, for example. But that was the added benefit that we thought of, for multiple tiles ☺ Thanks very much for the information! Best Regards, Yashaswini Raj