Upgrading Pivotal Cloud Foundry
Page last updated:
This topic describes upgrading Pivotal Cloud Foundry (PCF) to v2.4. The upgrade procedure below describes upgrading Pivotal Cloud Foundry Operations Manager (Ops Manager), Pivotal Application Service (PAS), and product tiles.
Warning: Pivotal does not recommend that you skip minor versions when upgrading PCF. Skipping minor versions when upgrading PCF may result in breaking changes. To avoid additional breaking changes, upgrade PCF to the minor version that directly follows your current version of PCF.
The apps in your deployment continue to run during the upgrade. However, you cannot write to your deployment or make changes to apps during the upgrade.
For details about how upgrading PCF impacts individual PAS components, see What Happens During PAS Upgrades.
If you have not already, complete the steps in the Upgrade Preparation Checklist for PCF v2.4.
Follow these steps to upgrade Ops Manager and Installed Products to PCF v2.4.
Download the Ops Manager VM Template v2.4 from the Pivotal Network site.
Record the FQDN address of the existing Ops Manager VM.
To avoid conflicts, power off the existing Ops Manager VM.
Deploy the new Ops Manager VM by following the steps in one of these topics:
When redirected to the Welcome to Ops Manager page, select Import Existing Installation.
When prompted, enter the Decryption Passphrase for this Ops Manager installation. You set this passphrase during your initial installation of Ops Manager.
Note: If lost, the Decryption Passphrase cannot be recovered.
Click Choose File and browse to the installation ZIP file exported in the Export Your Installation step of your upgrade preparation.
Note: Some browsers do not provide feedback on the status of the import process, and might appear to hang.
A Successfully imported installation message appears upon completion.
Import the product file to your Ops Manager Installation Dashboard.
Hover over the product name in Available Products and click Add.
Click the newly-added tile to review any configurable options.
(Optional) If you use other service tiles, you can upgrade them following the same procedure. See the Upgrading PAS and Other Pivotal Cloud Foundry Products topic for more information.
Warning: If the installation fails or returns errors, contact Support. Do not attempt to roll back the upgrade by restarting the previous (v2.3) Ops Manager VM.
Navigate to the Ops Manager Installation Dashboard.
Click Review Pending Changes, then Apply Changes. This immediately imports and applies upgrades to all tiles in a single transaction.
Click each service tile, select the Status tab, and confirm that all VMs appear and are in good health.
After confirming that the new installation functions correctly, remove the Ops Manager v2.3 VM.
During the upgrade, you can do the following to monitor your PCF foundation and help troubleshoot any issues.
Monitor the progress of the upgrade, checking the status of the foundation at various locations.
Pivotal recommends live-monitoring your upgrade with PCF Healthwatch, which monitors and alerts on the current health, performance, and capacity of PCF. Healthwatch captures, calculates, stores, visualizes, and alerts on PCF platform metrics, including:
- BOSH-reported VM metrics
- Runtime component metrics
- Key Performance Indicators and Key Scaling Indicators
- Healthwatch-generated super metrics
For more information, see the PCF Healthwatch documentation.
If you are not using PCF Healthwatch, you can do some or all of the following to monitor upgrade progress:
- Run BOSH CLI status checks:
bosh -e ALIAS task TASK_NUMBER
bosh -e ALIAS vms --vitals, bosh -e ALIAS instances --ps
- Check app availability
- Run cf CLI Commands
- Check the availability of the Ops Manager UI
- Check NAS performance (if using NAS)
- Check vSphere performance (if on vSphere)
See the cfdot documentation on GitHub for details.
Use the CF Diego Operator Toolkit (cfdot) to check Diego component instance count by current state.
Pivotal recommends this if you have a large foundation and have experienced storage issues in the past.
Periodically take snapshots of storage metrics.
This information helps determine the cause of upgrade issues.
If you encounter problems during upgrade, collect the following information:
- All job logs
- Task debug logs for VM upgrade tasks
- Installation log from Ops Manager
After your upgrade, do the following to prepare for use of your new environment, check its health status, and clean up.
Re-create your alias using BOSH:
bosh alias-env ALIAS -e DIRECTOR_IP
- Reason: To log in to BOSH after upgrading PCF, you need to re-create your alias.
- Product/Component: BOSH
Download the version of the Cloud Foundry Command Line Interface (cf CLI) packaged with the PAS tile on Pivotal Network.
Run BOSH CLI commands to check system status:
bosh -e ALIAS -d DEPLOYMENT_NAME instances --ps
bosh -e ALIAS vms --vitals
bosh -e ALIAS -d DEPLOYMENT_NAME cck --report
Note/Reason: To ensure that all jobs and process are running as expected
Product/Component: PCF and all tiles
Push and horizontally scale a test application.
- Reason: This is a performance test for PAS.
- Product/Component: PCF
If you are running PAS MySQL as a cluster, run the
mysql-diagtool to validate health of the cluster.
- Reason: See the BOSH CLI v2 instructions in the Running mysql-diag topic.
- Product/Component: PAS
If you added custom VM Type or Persistent Disk Type options, ensure that these values are correctly set and were not overwritten.
- Note/Reason: Verify that the Ops Manager Resource Config pane still lists your custom options.
- Product/Component: PCF
bosh -e ALIAS clean-up --all to clean up old stemcells, releases, orphaned disks, and other unused resources.
- Product/Component: Tiles
If you have installed any product tiles that use on-demand service brokers, such as MySQL for PCF, Redis for PCF, or RabbitMQ for PCF, then you must restart the broker for each tile. Restarting the broker ensures that the broker can communicate with the new version of CredHub.
To restart the broker for a tile, run the following command:
bosh -d MY-DEPLOYMENT-NAME restart MY-BROKER-NAME
$ bosh -d my-deployment restart redis-on-demand-broker