LATEST VERSION: 1.7 - RELEASE NOTES
Pivotal Cloud Cache for PCF v1.6

Upgrading Pivotal Cloud Cache

Upgrade minor release versions from your currently deployed version to the target version in sequential order. For example, PCC v1.2 must be upgraded to PCC v1.3 prior to upgrading to PCC v1.4. Note that each PCC release is compatible with two Pivotal Application Service (PAS) and Ops Manager versions, as specified in the Product Snapshot. Incorporate those upgrades to PAS and Ops Manager in your upgrade process as required to maintain compatibility, as described in Upgrading Pivotal Cloud Foundry.

WARNING: To work around a race condition, follow a different procedure as detailed in Special Upgrade Procedure for Dev and Small Footprint Plans to upgrade to PCC v1.6.2 for plans that colocate system components on a single VM.

Upgrade Procedure

Follow the steps below to upgrade PCC:

  1. Download the new version of the tile from the Pivotal Network.
  2. Upload the product to Ops Manager.
  3. Click Add next to the uploaded product.
  4. Click on the Cloud Cache tile and configure the upgrade options.

    • To try the upgrade on a small number of service instances first, set the quantity of canary service instances as described in Service Instance Upgrades.
    • Set the number of instances that are to be upgraded in parallel as described in Service Instance Upgrades.
    • Make sure that under the Errands section, the Upgrade All Service Instances Post-Deploy Errand is Default (On). Save the change.
  5. Click Review Pending Changes (see Reviewing Pending Product Changes).

  6. Click Apply Changes.

Special Upgrade Procedure for Dev and Small Footprint Plans

This upgrade procedure applies to upgrades to PCC v1.6.2 for plans that colocate system components on a single VM. Those plans are the dev plan and the small footprint plan. This special upgrade procedure exists to work around a race condition that exists in the timing of bringing down and restarting the two components that communicate with each other and are both located within a single VM.

Use this procedure for upgrades from 1.5.x, 1.6.0, or 1.6.1 to 1.6.2.

Follow the steps below to upgrade PCC:

  1. Download the new version of the tile from the Pivotal Network.
  2. Upload the product to Ops Manager.
  3. Click Add next to the uploaded product.
  4. Click on the Cloud Cache tile and configure the upgrade options.

    • To try the upgrade on a small number of service instances first, set the quantity of canary service instances as described in Service Instance Upgrades.
    • Set the number of instances that are to be upgraded in parallel as described in Service Instance Upgrades. Save the change.
  5. Click Review Pending Changes (see Reviewing Pending Product Changes).

  6. At the bottom of the Review Pending Changes page within the Pivotal CloudCache specification, uncheck the box labeled Upgrade All Service Instances, as in this view: Special Upgrade Review

  7. Click Apply Changes.

  8. Once the upgrade is applied (without the upgrade of all service instances), the BOSH upgrade-all-service-instances errand must be successfully completed to finish the upgrade. This is the errand that is subject to the race condition. Therefore, the errand must be run an indeterminate number of times, as there is no way to predict whether or not the errand will hit the race condition. Sequentially run this errand until it succeeds:

    bosh -e ENV -d DEPLOYMENT run-errand upgrade-all-service-instances
    

    Acquire the broker’s DEPLOYMENT name:

    $ bosh -e my-pcf deployments | grep p-cloudcache
    

    This is an example of running the errand:

    $ bosh -e my-pcf -d p-cloudcache_1fd2850e-b754-4c5e-aa5c-ddb54ee301e6 run-errand upgrade-all-service-instances
    

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