Skip to content

Latest commit

 

History

History
84 lines (58 loc) · 8.07 KB

updating-scaling.md

File metadata and controls

84 lines (58 loc) · 8.07 KB
copyright lastupdated
years
2018
2019-01-31

{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tip: .tip}

Updating and scaling

{: #update-scale}

Update the {{site.data.keyword.cfee_full_notm}} service instance to the latest version to get the latest CFEE functions and fixes. Updates of CFEE can include new versions of Cloud Foundry and CFEE supporting services (Kubernetes, Cloud Object Storage or Compose for PostgreSQL). However, not every CFEE update will include a new version of Cloud Foundry and CFEE supporting services.

The CFEE version updates take place on the control plane containing the CFEE components and on the cells. You can also scale the capacity of your CFEE instance by adding or deleting application cells.

Note: During a version update or while cells are being added or deleted, some metrics (e.g., Memory and CPU) shown in the Overview, Resource Usage and Update and Scaling pages may not be available.

Updating the CFEE version

{: #update}

Users need the following permissions to be able to update a CFEE instance to a new version:

  • Editor role or higher to a CFEE instance.
  • Operator role or higher to the Kubernetes cluster into which the CFEE is provisioned.

Updating the CFEE version of your CFEE instance is a two-step process. First, update the control plane that hosts the CFEE componentry. Then, update the cells that host your applications.

The following rules and constraints apply when updating a CFEE to a new version:

  • The control plane must be updated first. Once the control plane has been updated the cells can be updated.
  • Application cells can be updated only to the version of the control plane. That is, the control plane can be at a higher CFEE version level than application cells, but not viceversa.

To update the CFEE version of your CFEE instance:

  1. Go to the {{site.data.keyword.Bluemix_notm}} dashboard and open the {{site.data.keyword.cfee_full_notm}} that you want to update.
  2. Go to the Updates and Scaling page under the Operations entry in the navigation pane.
  3. (optional) In the Control Plane table you can expand the row to see the worker nodes in the control plane.
  4. Click Update.
  5. In the Update Control Plane dialog, select one of the available CFEE versions and click Update.The update takes about 45 minutes. The version description details the versions of the components included in the selected CFEE version package, along with a link to the What's New document describing the content delivered in that version.
  6. The Nodes Status column shows the progress of the update. Once the update is complete, the Version column reflects the new CFEE version.
  7. Once the update of the control plane cells is complete, find the Cells table and click Update.
  8. In the Update Control Plane dialog select the CFEE version and click Update. There is only available version for the cells to update because cells can be updated only to the version of the control plane. A single update action updates all cells.
  9. Cells are updated sequentially. The Nodes Status column indicates the progress of the update for each cell. As cells are updated, their new version is reflected in the Version column.

Disruptions during version update

{: #update-disruption}

Updating the Cloud Foundry control plane is not disruptive. However, updating Cloud Foundry cells to a new CFEE version may disrupt the operation of the CFEE environment. The updated is performed one cell at a time, so that application instances running in a cell are brought back up once the update is completed while the other cells are down during their update. Nevertheless, some applications and services running in the CFEE may become unavailable under some circumstances. For example, if the CFEE has two Cloud Foundry cells to full capacity, an application with only one instance will be down during the version update because the application instance cannot be moved to another cell while the cell is being updated and, consequently, the application will be unavailable. Even with three cells and three instances per application, there can be transient disruption in application availability during a version update.

During the version update there may be a discrepancy in the Memory and CPU metrics reported in the Cell Nodes gauges shown in the CFEE Overview page (which are generated by the Kubernetes cluster) and the same metrics shown in the Nodes dashboard in Grafana (which are generated a the operating system level).

The status of CFEE components while the updating is in progress will be reflected in the Health Check page. The restart takes approximately 45 minutes.

Version cycle and support policy

{: #version-cycle}

The Cloud Foundry Enterprise Environment service typically releases a new version on a regulary basis. The service's version follows the semantic versioning format Major.Minor.Patch (https://semver.org/)

The minor version is incremented regularly (typically, monthly). The major version is also incremented also, but less frequently, typically when there is a significant change. Updating to a Major version may result in some disruption during upgrade. Patches deliver a fix and are applied to the latest available version.

To prevent system downtime, CFEE instances are only allowed to update up to 2 major versions ahead of its current version. Using the previous example, if the CFEE instance current version is 3.1.2, and the target version is 7.0.0, the CFEE instance would need to be updated first to version 5.x.x, and then to the target version 7.0.0 .

New capabilities and enhancements to existing capabilities delivered regularly become available only in the latest version. Critical fixes are delivered in the latest release within only the latest 3 major versions (the latest version and the two previous versions). For example, if versions 4.x.x, 3.x.x and 2.x.x are available, versions 1.x.x will not be supported (i.e., patches will not be delivered with fixes for versions 1.x.x).

Patches are delivered on the latest available version of a given major. For example, if a CFEE instance is running version 3.1.2 but the latest available version in the 3.x.x major is version 3.3.4, any patches will be delivered on the code base of version 3.3.x, which means that the patch will be delivered in a (new) version 3.3.5. The CFEE instance with version 3.1.2 would need to be updated to version 3.3.5 in order to receive the new patch (i.e., udating just to version 3.3.4 will not solve the provlem fixed in the patch, which is delivered only in version 3.3.5).

Scaling the CFEE infrastructure

{: #scale}

Users need the following permissions to be able to add or remove Cloud Foundry cells to a CFEE instance:

  • Administrator role or higher to a CFEE instance.
  • Operator role or higher to the Kubernetes cluster into which the CFEE is provisioned.

To add application cells in your CFEE instance:

  1. Go to the {{site.data.keyword.Bluemix_notm}} dashboard and open the {{site.data.keyword.cfee_full_notm}} where you want add cells.
  2. Click Change Cloud Foundry cell count near the Cells table, which opens the Add Cloud Foundry Cells page.
  3. In the Change Cloud Foundry cell count page, select the total number of cells in the Target cell count field. The page also shows the Geography and Location of the CFEE instance where they cells will be added. It also shows the current number of cells in the Current Cell count field and the capacity of the cells to be added (which is the same as the capacity of the current cells) in the Node size filed. The page's right pane shows the estimated cost of the added cells along with the new total estimated cost of the environment.
  4. Click Add cells. In the Add Cells dialog, click Add
  5. Go back to the Updates and Scaling page. A new row is added in the Cell Nodes table for each new Cell node. The Node Status column indicates the progress of adding and deploying the cell to your CFEE environment.