Upgrading Redis for PCF
Page last updated:
This section contains the upgrade procedure and upgrade paths for Redis for PCF.
Consider the following compatibility information before upgrading Redis for PCF.
For more information, see the Product Version Matrix.
|Ops Manager Version||Supported Upgrades for Redis Installations|
|v1.5.x, v1.6.x||v1.4.0 – v1.4.3||v1.4.4 – latest v1.4.x|
|v1.5.0 – v1.5.7|
|v1.4.4 – latest v1.4.x||Next v1.4.x – latest v1.4.x|
|v1.5.0 – latest v1.5.x|
|v1.5.0 – latest v1.5.x||Next v1.5.x – latest v1.5.x|
|v1.7.x||v1.5.0 – latest version||v1.5.1 – latest version|
|v1.8.x||v1.5.17 – latest version||v1.6.0 – latest version|
|v1.9.x – latest version||v1.6.0 – latest version||v1.8.0 – latest version|
|v1.10.0 – v1.10.2||v1.7.2 – latest version||v1.8.0 – latest version|
|v1.10.9 – latest version||v1.7.2 – latest version||v1.9.0 – latest version|
|v1.11.x||v1.9.0 – latest version||1.10.0 – latest version|
|v1.12.x||v1.10.0 – latest version|
This product enables a reliable upgrade experience between versions of the product that is deployed through Ops Manager.
For information on the upgrade paths for each released version, see the above table.
To upgrade Redis for PCF, do the following:
- Download the latest version of the product from Pivotal Network.
- Upload the new
.pivotalfile to Ops Manager.
- If required, upload the stemcell associated with the update.
- If required, update any new mandatory configuration parameters.
- Click Apply changes. The rest of the process is automated.
During the upgrade deployment each Redis instance experiences a small period of downtime as each Redis instance is updated with the new software components. This downtime is because the Redis instances are single VMs operating in a non HA setup.
The length of the downtime depends on whether there is a stemcell update to replace the operating system image, or whether the existing VM can simply have the redis software updated. Stemcell updates incur additional downtime while the IaaS creates the new VM, whereas updates without a stemcell update are faster.
Ops Manager ensures the instances are updated with the new packages and any configuration changes are applied automatically.
Upgrading to a newer version of the product does not cause any loss of data or configuration.
A redeploy causes downtime of the Redis for PCF tile. This section clarifies what events trigger a redeploy.
Ops Manager Changes
In Ops Manager, any field that changes the manifest causes a redeploy of the Redis for PCF tile.
Elastic Runtime Changes
In Elastic Runtime, changes to any of the following properties can trigger downtime:
..cf.consul_server.ips—Consul Server Resource Config
$runtime.system_domain—Runtime System Domain
..cf.ha_proxy.skip_cert_verify.value—Disable SSL certificate verification for this environment in Elastic Runtime
$runtime.apps_domain—Runtime Apps Domain
..cf.nats.ips—NATS Resource Config
$self.service_network—Service Networks in Ops Manager
When the operator applies any of the above changes to Elastic Runtime, downtime is triggered for the following:
Redis On-Demand Broker in Redis for PCF v1.8 and later
Dedicated-VM and Shared-VM Services in Redis for PCF v1.9 and earlier
Upgrading all Service Instances
For Redis for PCF v1.8 and later, downtime for service instances occurs only after the operator runs the
upgrade-all-service-instancesBOSH errand, after all tile upgrades are completed successfully.
Any change to a field on the Redis for PCF tile causes BOSH to redeploy both the legacy and the On-Demand Redis Brokers after the operator runs the
This section explains how changing the network after deploying Redis for PCF affects instances and apps.
To change the network for dedicated-VM and shared-VM services, click Assign AZs and Networks in the Redis for PCF tile configuration and use the Network dropdown. The network applies to both shared-VM and dedicated-VM services.
You can also change the network by altering the CIDR in the Ops Manager Director tile.
Pivotal discourages changing the network that a pre-existing dedicated-VM deployment or shared-VM deployment works with.
If the network is changed, app bindings for existing dedicated-VM and shared-VM instances might stop working. Dedicated-VMs might also be reallocated as new service instances without their data being cleaned, resulting in a data leak between apps.
To change the service network for on-demand service instances, click Assign AZs and Networks in the Redis tile configuration and use the Service Network dropdown. The service network applies to on-demand service instances.
You can also change the service network by altering the CIDR in the Ops Manager Director tile.
If you change the service network, you must unbind and rebind existing apps to the on-demand Redis instance.
New on-demand service instances are placed into the new service network, but existing on-demand service instances are not moved. If you need to move the data in on-demand Redis instances to a new service network, you must create a new instance, migrate the data manually, and delete the old instance.
Similarly, changing the availability zone for an on-demand plan only applies to new on-demand instances and does not alter existing instances.
When a new version of Redis is released, Pivotal aims to release a new version of Redis for PCF containing the new Redis version soon after.
When a new version of Redis or another dependent software component, such as the stemcell, is released due to a critical CVE, Pivotal’s goal is to release a new version of the Redis for PCF within 48 hours.