Upgrading Elastic Runtime and Other Pivotal Cloud Foundry Products

Page last updated:

This topic describes how to upgrade to a point release of Elastic Runtime (ERT) and other product tiles without upgrading Ops Manager. For example, use this topic to upgrade from ERT 1.9.0 to 1.9.1. You might need to perform this upgrade if a security update for ERT is released, or if new features are introduced in a point release of a product tile.

For Elastic Runtime component and version information, see the Elastic Runtime release notes.

Before You Upgrade to Point Releases

Upgrading Elastic Runtime

Note: If you are using the Pivotal Network API, the latest product versions will automatically appear in your Installation Dashboard.

To upgrade Elastic Runtime for PCF without upgrading Ops Manager, follow the procedure for installing PCF products:

  1. Download the product file from Pivotal Network.
  2. Import the product file to your Ops Manager Installation Dashboard.
  3. Click the plus icon next to the uploaded product description to add this product to your staging area.
  4. Click the newly added tile to review any configurable options.
  5. Click Apply Changes to install the service.

Rolling Back ERT in the Event of a Failed Upgrade

If you have previously backed up PCF using BOSH Backup and Restore, you can roll back Elastic Runtime (ERT) to an earlier deployment if the ERT upgrade fails. For instructions about rolling back the ERT deployment, see Rolling Back ERT Deployment to an Earlier Backup with BBR.

Upgrading PCF Products

Note: If you are using the Pivotal Network API, the latest product versions will automatically appear in your Installation Dashboard.

This section describes how to upgrade individual products like Single Sign-On for PCF, MySQL for PCF, RabbitMQ® for PCF, and Metrics for PCF in your Pivotal Cloud Foundry (PCF) deployment. Ensure you review the individual product upgrade procedure for each tile.

  1. Browse to Pivotal Network and sign in.

  2. Download the latest PCF release for the product or products you want to upgrade. Every product is tied to exactly one stemcell. Download the stemcell that matches your product and version.

  3. Confirm that you have adequate disk space for your upgrades. You need at least 20 GB of free disk space to upgrade PCF Ops Manager and Elastic Runtime. If you plan to upgrade other products, the amount of disk space required depends on how many tiles you plan to deploy to your upgraded PCF deployment.

    To check current persistent disk usage, select the Ops Manager Director tile from the Installation Dashboard. Select Status and review the value of the PERS. DISK column. If persistent disk usage is higher than 50%, select Settings > Resource Config, and increase your persistent disk space to handle the size of the resources. If you do not know how much disk space to allocate, set the value to at least 100 GB.

  4. Browse to the Pivotal Cloud Foundry Operations Manager web interface and click Import a Product.

    Import

  5. Select the .pivotal file that you downloaded from Pivotal Network or received from your software distributor, then click Open. If the product is successfully added, it appears in the your product list. If the product you selected is not the latest version, the most up-to-date version will appear on your product list.

  6. Click the plus icon next to the product description to add the product tile to the Installation Dashboard.

  7. Repeat the import, upload, and upgrade steps for each product you downloaded.

  8. If you are upgrading a product that uses a self-signed certificate from v1.1 to v1.2, you must configure the product to trust the self-signed certificate.

    Follow the steps below to configure a product to trust the self-signed certificate:

    1. Click the product tile.
    2. In the left-hand column, select the setting page containing the SSL certificate configuration. For example, for Elastic Runtime, select the HAProxy page.
    3. Check the Trust Self-Signed Certificates box.
    4. Click Save.
  9. Click Apply changes.

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