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

Understanding the Effects of Single Components on a Pivotal Cloud Foundry Upgrade

Page last updated:

The Resource Config page of Pivotal Elastic Runtime tile in the Pivotal Cloud Foundry (PCF) Ops Manager shows the components that the Ops Manager Director installs. You can specify the number of instances for some of the components. We deliver the remaining resources as single components, meaning that they have a preconfigured and unchangeable value of one instance.

In a single-component environment, upgrading can cause the deployment to experience downtime and other limitations because there is no instance redundancy. Although this behavior might be acceptable for a test environment, you should configure the scalable components with editable instance values, such as HAProxy, Router, and Diego cells, for optimal performance in a production environment.

Note: A full Ops Manager upgrade may take close to two hours, and you will have limited ability to deploy an application during this time.

Summary of Component Limitations

The table lists components in the order that Ops Manager upgrades each component and includes the following columns:

  • Scalable?: Indicates whether the component has an editable value or a preconfigured and unchangeable value of one instance.

    Note: For components marked with a checkmark in this column, we recommend that you change the preconfigured instance value of 1 to a value that best supports your production environment. For more information about scaling a deployment, refer to the Scaling Cloud Foundry topic.

  • Extended Downtime?: Indicates that if there is only one instance of the component, that component is unavailable for up to five minutes during an Ops Manager upgrade.
  • Other Limitations and Information: Provides the following information:
    • Component availability, behavior, and usage during an upgrade
    • Guidance on disabling the component before an upgrade

Note: The table does not include the Run Smoke Tests and Run CF Acceptance Tests errands and the Compilation job. Ops Manager runs the errands after it upgrades the components and creates compilation VMs as needed during the upgrade process.

Component Scalable? Extended Downtime? Other Limitations and Information
HAProxy
NATS
etcd
NFS Server You cannot push, stage, or restart an app when an upgrade affects the NFS Server.
Cloud Controller Database
Cloud Controller Your ability to manage an app when an upgrade affects the Cloud Controller depends on the number of instances that you specify for the Cloud Controller and Diego components. If either of these components are single components, you cannot push, stage, or restart an app during the upgrade.
Clock Global
Cloud Controller Worker
Router
Pivotal Ops Metrics Collector The Pivotal Ops Metrics tool is a JMX extension for Elastic Runtime that you can install. If you install this tool, Ops Manager operators may experience a 5 minute delay in metrics collection during an upgrade.
You can disable this component before an upgrade to reduce the overall system downtime.
UAA Database
UAA If a user has an active authorization token prior to performing an upgrade, the user can still log in using either a UI or the CLI.
Login
Apps Manager Database You can disable this component before an upgrade to reduce the overall system downtime.
MySQL Server
Diego Cells Your ability to manage an app when an upgrade affects Diego Cells depends on the number of instances that you specify for the Diego Cells, Cloud Controller, and other Diego components. If any of these components have only one instance, you may fail to push, stage, or restart an app during the upgrade.
If you only have one Diego Cell, upgrading it causes downtime for the apps that run on it, including the Apps Manager app and the App Usage Service.
Diego BBS Your ability to manage an app when an upgrade affects the Diego BBS depends on the number of instances that you specify for the Diego BBS, Cloud Controller, and other Diego components. If any of these components have only one instance, you may fail to push, stage, or restart an app during the upgrade.
Diego Brain Your ability to manage an app when an upgrade affects the Diego Brain depends on the number of instances that you specify for the Diego Brain, Cloud Controller, and other Diego components. If any of these components have only one instance, you may fail to push, stage, or restart an app during the upgrade.
Doppler Server Ops Manager operators experience 2-5 minute gaps in logging.
Loggregator Traffic Controller Ops Manager operators experience 2-5 minute gaps in logging.
Push Apps Manager and Push App Usage Service errands These errands run scripts that connect the Apps Manager app and the App Usage Service components to the Apps Manager Database.
The Apps Manager app and App Usage Service components run in a single Diego Cell instance and the Apps Manager Database is a single component. If there is an upgrade issue with either the Apps Manager Database instance or the Diego Cell instance, the upgrade fails and Ops Manager does not run the Apps Manager deployment errand again.
Create a pull request or raise an issue on the source for this page in GitHub