LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.7

Upgrading Elastic Runtime and Other Pivotal Cloud Foundry Products

Page last updated:

Note: Pivotal Cloud Foundry (PCF) for vCloud Air and vCloud Director is deprecated and availability is restricted to existing customers. Contact Support for more information.

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

The topic Upgrading Pivotal Cloud Foundry describes how to perform a complete upgrade of PCF, including Ops Manager, ERT and other installed products.

WARNING: Before you upgrade to Elastic Runtime 1.7, you must migrate all apps that are currently running on DEA architecture to run on Diego architecture. All apps that do not already run on Diego will terminate during an upgrade from 1.6 to 1.7.

Note: 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.

Refer to the Product Compatibility Matrix before upgrading Elastic Runtime for Pivotal Cloud Foundry.

Elastic Runtime Snapshot

Current Pivotal Cloud Foundry Elastic Runtime Details
Version: 1.7.0
Release Date: 29 April 2016
Software component version: Cloud Foundry 235
Compatible Ops Manager Version(s): 1.7.x
vSphere support? Yes
AWS support? Yes
OpenStack support? Yes

Upgrading Elastic Runtime

Refer to the Product Version Matrix before upgrading Elastic Runtime for Pivotal Cloud Foundry.

Note: Before you upgrade to Ops Manager 1.7.x, you must first upgrade PCF Elastic Runtime to version 1.6.9 or higher.

Install using the Pivotal Operations Manager

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

  1. Download the product file from Pivotal Network.
  2. Upload the product file to your Ops Manager installation.
  3. Click Add next to the uploaded product description in the Available Products view 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.

Before You Upgrade

Before you upgrade to Elastic Runtime 1.7, you must migrate all apps that are currently running on DEA architecture to run on Diego architecture. Pivotal does not support DEA architecture in Pivotal Cloud Foundry 1.7. See the Migrating Apps to Diego topic for information.

Upgrading PCF Products

Important: Read the Known Issues section of the Pivotal Cloud Foundry Release Notes before getting started.

This section describes how to upgrade individual products like Pivotal Cloud Foundry Elastic Runtime, Pivotal MySQL, or RabbitMQ in your Pivotal Cloud Foundry (PCF) deployment.

Note: In Ops Manager 1.7, all product tiles use floating stemcells by default. This increases the security of your deployment by enabling tiles to automatically use the latest patched version of a stemcell, but it may significantly increase the amount of time required by a tile upgrade. Review the Understanding Floating Stemcells topic for more information.

Note: To upgrade your PCF product to a target release, you must install all releases from your currently deployed version to the target version in sequential order. For example, if your deployment uses Elastic Runtime release 1.5 and you are upgrading to 1.7, you must sequentially install 1.6 and 1.7.

Note: The Single Sign-On service tile operates in lockstep with Pivotal Elastic Runtime.
  • The SSO v1.0.x tiles are compatible with PCF v1.6.x
  • The SSO v1.1.x tiles are compatible with PCF v1.7.x
If you are upgrading from PCF 1.6 to PCF 1.7 and you are using SSO v1.0.x, you must update SSO v1.1.0 service tile at the same time as you update the ERT upgrade.
  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. From your Installation Dashboard, select the Ops Manager Director tile. Select Status. If you need more space to handle your upgrades, select Settings > Resource Config. Increase your persistent disk space to 100 GB, or enough to handle the size of the resources.

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

    Import

    Note: As of release 1.4.0.0, Pivotal Ops Manager no longer supports older versions of PCF products. You must update all products to at least version 1.2 (except for RabbitMQ, which must be updated to at least version 1.3.4.0) before importing them into Ops Manager 1.4.0.0.

  5. Upload the new version of a product you want to upgrade.

  6. Under Available Products, click Upgrade for the uploaded product.

  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 version 1.1 to 1.2, you must configure the product to trust the self-signed certificate.

    To do this:

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

After You Upgrade

  • Advise your application developers about the Diego architecture. See the Migrating Apps to Diego and the Diego Architecture topics for more information.

  • Ops Manager 1.7 defines specific instance types instead of custom sizes for vSphere or vCloud. Each instance adopts an instance type that is the closest match to its previous custom size for CPU, memory, and disk space. You can modify the automatically selected instance size by selecting a different type under Resource Config for each of your installed tiles.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub