Upgrading MySQL for Pivotal Platform

Page last updated:

This topic explains how to upgrade the MySQL for Pivotal Platform 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.

Upgrade MySQL for Pivotal Platform

To upgrade the MySQL for Pivotal Platform service, follow the Pivotal 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 Pivotal Platform. This adds the tile to your staging area.

  6. Click the newly-added MySQL for Pivotal Platform 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. Click Review Pending Changes. For more information about this Ops Manager page, see Reviewing Pending Product Changes.

    2. Click Apply Changes.
  8. After the upgrade completes, upgrade all of the MySQL service instances to the new version, as described in Upgrade MySQL Instances below.

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

Upgrade MySQL Instances

After upgrading the MySQL for Pivotal Platform service, operators must upgrade existing service instances to run 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 Pivotal Platform 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 Pivotal Platform.

  • Impact: Apps lose access to the MySQL service while Pivotal Platform 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 Pivotal Platform 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.