LATEST VERSION: 2.5 - RELEASE NOTES

Upgrading MySQL for PCF

Page last updated:

This topic explains how to upgrade the MySQL for Pivotal Cloud Foundry (PCF) service and existing service instances. It also explains the service interruptions that can result from service changes and upgrades and from failures at the process, VM, and IaaS level.

Prerequisites

Before you upgrade MySQL for PCF you must complete the procedures in Preparing for Upgrading MySQL for PCF.

Upgrade MySQL for PCF

Note: Before upgrading to the next version of MySQL for PCF, run the upgrade-all-service-instances errand to make sure that all your service instances are upgraded to your current version.
For more information, see Upgrade Service Instances.

To upgrade the MySQL for PCF service, you follow the same Ops Manager process that you use to install the service for the first time. Your configuration settings migrate to the new version automatically. To perform an upgrade:

  1. Review the Release Notes for the version you are upgrading to.

  2. Download the Ubuntu Xenial stemcell from Pivotal Network, and import it into the Ops Manager Stemcell Library. For instructions, see Verify Stemcell Version and Apply All Changes.

  3. Download the desired version of the product from Pivotal Network.

  4. Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.

  5. Under the Import a Product button, click + next to MySQL for PCF. This adds the tile to your staging area.

  6. Click the newly-added MySQL for PCF tile to review its configuration panes. Click Save on any panes where you make changes.

  7. Return to the Ops Manager Dashboard and do the following to complete the installation:

    1. If you are using Ops Manager v2.3 or later, click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.

    2. Click Apply Changes.

Upgrading the MySQL for PCF service and service instances can temporarily interrupt the service. For more information, see Service Interruptions below.

Upgrade MySQL Instances

After upgrading the MySQL for PCF service, operators must upgrade existing service instances to be in sync with the new version of the service. Developers cannot create new bindings to a service instance that has not been upgraded.

To upgrade existing service instances, operators run the following command:

bosh -d BROKER-NAME run-errand upgrade-all-service-instances

Where BROKER-NAME is the deployment name of the broker.

For more information about the upgrade-all-service-instances errand, see upgrade-all-service-instances.

Service Interruptions

Service changes and upgrades and failures at the process, VM, and IaaS level can cause outages in the MySQL for PCF service, as described below.

Read this section if:

  • You are experiencing a service interruption and are wondering why.
  • You are planning to update or change a service instance and want to know if it might cause a service interruption.

Stemcell or Service Update

An operator updates a stemcell version or their version of MySQL for PCF.

  • Impact: Apps lose access to the MySQL service while PCF updates the service instance they are bound to. The service should resume within 10–15 minutes.
  • Required Actions: None. If the update deploys successfully, apps reconnect automatically.

Plan Change

A developer changes their service instance to provide a different service plan, using cf update-service or Apps Manager.

  • Impact: Apps lose access to the MySQL service while PCF updates the service instance they are bound to. The service should resume within 10–15 minutes.
  • Required Actions: None. If the plan change deploys successfully, apps reconnect automatically.
Create a pull request or raise an issue on the source for this page in GitHub