LATEST VERSION: 2.0 - RELEASE NOTES

Upgrading Redis for PCF

Page last updated:

This section contains the upgrade procedure and upgrade paths for Redis for PCF.

Compatible Upgrade Paths

Before upgrading Redis for PCF, for compatibility information, see the Product Version Matrix.

Upgrade to Redis for PCF v2.0

Breaking Change: Dedicated VMs are absent from Redis for PCF v2.0. As of Redis for PCF v1.11, the on-demand service is at feature parity with the dedicated-VM service. Dedicated VMs are marked as deprecated in Redis for PCF v1.14. Pivotal recommends that you migrate to the on-demand service plan or back up data before upgrading to Redis for PCF v2.0 to prevent data loss in Redis deployments used as persistent storage. For information about migrating to on-demand service plans, see Migrating from dedicated-vm service plans to on-demand service plans in the Pivotal Support knowledge base.

This product enables a reliable upgrade experience between versions of the product deployed through Ops Manager.

For information on the upgrade paths for each released version, see Compatible Upgrade Paths above.

To upgrade Redis for PCF v2.0, do the following:

  1. Download the latest version of the product from Pivotal Network.

  2. Upload the new .pivotal file to Ops Manager.

  3. If required, upload the stemcell associated with the update.

  4. Select the deprecation warning checkbox in the WARNING - DEPRECATED INSTANCES tab. This removes any dedicated-VM instances in your deployment.

    Note: This checkbox is mandatory when upgrading to Redis for PCF v2.0. Ensure that you have backed up or migrated data to on-demand instances before upgrading to Redis for PCF v2.0.

  5. If required, update any new mandatory configuration parameters.

  6. Click Apply changes. The rest of the process is automated.

During the upgrade each Redis instance experiences a small period of downtime as each instance is updated with the new software components. This downtime is because Redis instances are single VMs operating in a non high availability (HA) setup.

The length of downtime depends on whether there is a stemcell update to replace the operating system image, or whether the Redis software is updated the on the existing VM. 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.

Downtime During Upgrades and Redeploys

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.

PAS (or Elastic Runtime) Changes

In the Pivotal Application Service (PAS) or 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 PAS (or 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 PAS (or Elastic Runtime), downtime is triggered for the following:

  • Redis On-Demand Broker in Redis for PCF v1.8 and later

  • 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-instances BOSH 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 upgrade-all-service-instances errand.

Network Changes after Deployment

This section explains how changing the network after deploying Redis for PCF affects instances and apps.

Shared VMs

To change the network for shared-VM services, click Assign AZs and Networks in the Redis for PCF tile configuration and use the Network dropdown.

You can also change the network by altering the CIDR in the BOSH Director tile.

Pivotal discourages changing the network that a pre-existing shared-VM deployment works with.

If the network is changed, app bindings for existing shared-VM instances might stop working.

On-Demand Service Instances

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 BOSH 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.

Release Policy

When a new version of Redis is released, a new version of Redis for PCF is released soon after.

For more information about the PCF release policy, see Release Policy.

Create a pull request or raise an issue on the source for this page in GitHub