On-Demand Service Offering
Note: Pivotal Platform is now part of VMware Tanzu. In v2.4 and later, Redis for Pivotal Platform is named Redis for VMware Tanzu Application Service.
Page last updated:
Redis for VMware Tanzu Application Service offers on-demand and shared-VM service plans. This section describes the architecture, lifecycle, and configurations of the on-demand plan, as well as networking information for the on-demand service. For similar information for the Shared-VM plans, see Shared-VM Service Offering.
This diagram shows the architecture of the service broker and on-demand plans and how the user’s app binds to a Redis instance.
You can enable TLS to secure traffic between apps and service instances. In Redis for Tanzu Application Service, the available options are Optional and Not Configured.
When setting TLS to Optional within On-Demand Service Settings, both TLS and non-TLS connections are accepted. TLS traffic goes through a proxy as shown in the diagram below. Enabling TLS is not expected to noticeably reduce performance. This depends, however, on network infrastructure, application architecture, and other such resources being in good shape.
VMware recommends setting TLS as Optional, because it allows app developers to migrate to TLS connections regardless of whether traffic is restricted to just TLS connections.
Note: The option to enforce TLS only is not supported in Redis for Tanzu Application Service.
Steeltoe and Spring apps use the TLS port by default, if it is available. Other apps might require further configuration to make use of the correct port.
The diagram below shows how apps communicate with on-demand Redis instances when you set TLS to Optional.
When setting TLS to Not Configured within the On-Demand Service Settings, the communication with service instances remains unchanged from Redis for Pivotal Cloud Foundry v2.1 and earlier.
The diagram below shows how apps communicate with on-demand Redis instances when you set TLS to Not Configured.
Redis for Tanzu Application Service offers on-demand plans as the
p.redis service within the tile.
On-demand plans are best suited to caching.
Redis for Tanzu Application Service has tailored the default configuration to this use case.
The default on-demand plan is the On-Demand Cache Plan. Service instances of this plan are deployed to a dedicated VM. VMware recommends that you configure these VMs to have 2.5 times more persistent disk than memory.
Operators can customize service plans by configuring the Plan name, Plan description, Server VM type, and Server Disk type. You can add and configure as many service plans as required.
- Each on-demand service instance is deployed to its own VM and is suitable for production workloads.
- The service plans are operator-configured and enabled. When enabled, app developers can view the available plans in the Marketplace and provision a Redis instance from that plan.
- Operators can update the cache plan settings, including the VM size and disk size, after the plans have been created.
- Operators and app developers can change certain Redis configurations from the default. For more information, see Configuration for On-Demand Service Plans below.
- The default
allkeys-lruand can be updated for other cache policies.
- On-Demand Redis supports Redis Database Backup (RDB) snapshots, but not Append-Only File (AOF) persistence. For more information, see Redis Persistence in the Redis documentation.
- The maximum number of instances is managed by a per-plan and global quota. For information about setting quotas, see Setting Limits for On-Demand Service Instances.
For on-demand plans, certain Redis configurations can be set by the operator during plan configuration, and by the app developer during instance provisioning. Other Redis configurations cannot be changed from the default.
The Redis settings that an operator can configure in the tile UI include:
- Redis Client Timeout
- Redis TCP Keepalive
- Max Clients
- Lua Scripting
- Plan Quota
For more information, see Configure On-Demand Plan Settings.
The Redis settings that an app developer can configure include:
For more information, see Customize an On-Demand Service Instance.
- Instances of the on-demand plan can be deployed until their number reaches either an operator-set per-plan quota or a global quota. For information about setting quotas, see Setting Limits for On-Demand Service Instances.
- Instances are provisioned based on the On-Demand Services SDK and service broker adapter associated with this plan.
redis.confis set to 45% of the system memory.
- Any on-demand plan can be disabled from the plan page in Ops Manager.
Limitations for the on-demand service include:
Operators must not downsize the VMs or disk size as this can cause data loss in pre-existing instances.
Operators can update certain plan settings after the plans have been created. To ensure upgrades happen across all instances, set the upgrade instances errand to On.
If the operator updates the VM size, disk size, or the Redis configuration settings, thereby enabling Lua Scripting, max-clients, timeout, and TCP keepalive, then these settings are implemented in all existing instances.
Here is the lifecycle of Redis for Tanzu Application Service, from an operator installing the tile through an app developer using the service then an operator deleting the tile.