Redis for PCF
Page last updated:
This is documentation for the Redis for Pivotal Cloud Foundry (PCF) service tile. This tile can be downloaded from Pivotal Network.
- Describes the features and architecture of Redis for PCF.
- Instructs the PCF operator on how to install, configure, maintain, and backup Redis for PCF.
- Instructs the app developer on how to choose a service plan, create and delete Redis service instances, and bind an app.
|Release date||March 7, 2018|
|Software component version||Redis OSS v3.2.11|
|Compatible Ops Manager version(s)||v1.10.9+, v1.11.0*|
|Compatible Elastic Runtime version(s)||v1.10.9+, v1.11.0|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
* Ops Manager v1.9+ have support for securing metrics and logs through loggregator with TLS — this is enabled in Redis for PCF v1.9.
Redis is an easy to use, high speed key-value store that can be used as a database, cache, and message broker. It supports a range of data structures including strings, lists, hashes, sets, bitmaps, hyperloglogs, and geospatial indexes. It is easy to install and configure and is popular with engineers as a straightforward NoSQL data store. It is used for everything from a quick way to store data for development and testing through to enterprise-scale apps like Twitter.
Redis for PCF packages Redis for easy deployment and operability on PCF. Redis for PCF can be used as a datastore or cache. Metrics and logging enable operators to monitor Redis health. Operators can configure scheduled backups to a variety of destinations. There are manual backup and restore scripts for individual service instances. New features are regularly introduced. Upgrading Redis for PCF is straightforward and preserves configuration and data.
Redis for PCF v1.8 and later includes on-demand provisioning of Redis instances based on the On-Demand Services SDK.
This enables an app developer to create a Redis instance as needed from the CF CLI through the
cf create-service command.
The Operator configures the plan options available to the app developers.
For more information, see On-Demand Service Offering.
Redis for PCF still offers Dedicated-VM and Shared-VM plans. With these plans, an Operator specifies at install time how many dedicated VM Redis instances to create.
For more information about the dedicated-VM and shared-VM service, see Dedicated-VM and Shared-VM Service Offerings.
As of v1.9, Redis for PCF supports configuring multiple AZs. However, assigning multiple AZs to Redis jobs does not guarantee high availability.
- On-Demand plans can be assigned to any of the configured availability zones. However, each instance still operates as a single node with no clustering.
- Shared-VM instances run on a single node in just one of the configured availability zones and are therefore not highly available.
- Dedicated-VM instances can be assigned to any of the configured availability zones. However, each instance still operates as a single node with no clustering. This separation over availability zones provides no high availability.
For information on how to upgrade and the supported upgrade paths, see Upgrading Redis for PCF.
Review the following table to determine if Redis for PCF has the features needed to support your enterprise.
|Plans and Instances||More Information|
|On-Demand, Dedicated-VM and Shared-VM plans||Redis for PCF provides On-Demand, dedicated VM and shared VM service plans.||Plans|
|Customizable plans||For the On-Demand Plan and Dedicated-VM plan, the operator can customize the VM and disk size.||Configuring|
|Installation and Upgrades||More Information|
|Product upgrades||Redis for PCF can be upgraded from v1.7 tiles||Upgrading Redis for PCF|
|Deployment Smoke Tests||Redis for PCF installation and upgrade runs a post deployment BOSH errand that validates basic Redis operations||Smoke Tests|
|Maintenance and Backups||More Information|
|Operational Monitoring and Logging||Redis for PCF v1.9 provides metrics for monitoring On-Demand plan usage and quotas and syslog redirection to external log ingestors.||Monitoring Redis for PCF|
|Backup and Restore||Redis for PCF v1.9 includes automatic backups on a configurable schedule to a variety of destinations for Dedicated-VM and Shared-VM plans, as well as scripts for backup and restore of service instances. The On-Demand plan does not offer this.||Manual Backup and Restore of Redis for PCF|
|Scale and Availability||More Information|
|Scale||Redis for PCF has been tested with 60 GB of data|
|On-Demand Plan||Redis for PCF provides up to 50 on-demand instances across plans|
|Ability to Scale Up / Down||Operators can scale VMs up, but not down||Configuring|
|Rolling Deployments||Redis for PCF does not support rolling deployments because it is single node; the service is unavailable during upgrades.||Upgrades|
|AZ Support||Assigning multiple AZs to Redis jobs does not guarantee high availability.||About Multiple AZs in Redis for PCF|
|Encrypted Communication in Transit||Redis for PCF has been tested successfully with the BOSH IPsec Add-on||Securing Data in Transit with the IPsec Add-on|
The following table lists where you can find topics related to the information on this page:
|For more information about…||See…|
|Is Redis for PCF right for you?||Enterprise-Ready Checklist|
|Product compatibility||Product Version Matrix|
|How to upgrade Redis for PCF||Upgrading Redis for PCF|
|How to use Redis||Redis Documentation|
Some PCF services offer on-demand service plans. These plans let developers provision service instances when they want.
These contrast with the more common pre-provisioned service plans, which require operators to provision the service instances during installation and configuration through the service tile UI.
The following PCF services offer on-demand service plans:
MySQL for PCF v2.0 and later
RabbitMQ for PCF
Redis for PCF
Pivotal Cloud Cache (PCC)
These services package and deliver their on-demand service offerings differently. For example, some services, like Redis for PCF, have one tile, and you configure the tile differently depending on whether you want on-demand service plans or pre-provisioned service plans.
For other services, like PCC, you install one tile for on-demand service plans and a different tile for pre-provisioned service plans.
The following table lists and contrasts the different ways that PCF services package on-demand and pre-provisioned service offerings.
|PCF service tile||Standalone product related to the service||Versions supporting on demand||Versions supporting pre-provisioned|
|RabbitMQ for PCF||Pivotal RabbitMQ||v1.8 and later||All versions|
|Redis for PCF||Redis||v1.8 and later||All versions|
|MySQL for PCF||MySQL||v2.x
(based on Percona Server)
(based on MariaDB and Galera)
|PCC||Pivotal GemFire||All versions||NA|
|GemFire for PCF||Pivotal GemFire||NA||All versions|
Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.