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

PCF Isolation Segment v1.10 Release Notes

Releases

1.10.1

  • Patches an issue with the naming of the router VM. See the note below for more details.
  • Bumps the rootfs to v1.59.0 which provides stack version 1.110.0.

The routers use consul for service discovery and necessarily require that their local consul agent join the larger Elastic Runtime consul cluster to send and receive service discovery updates. Membership in the cluster is managed by name and IP address.

The Elastic Runtime routers will register with a name like “router-1” or “router-4”, indicating their job name and VM index. Unfortunately, the Isolation Segment Tile routers use the same name to register themselves with the cluster and thus result in a naming collision.

This naming collision causes the routers in the Isolation Segment and the routers in the Elastic Runtime to fight for membership in the cluster. This instability can eventually cause the routers to become unavailable.

To resolve this, we have released a new version of the Isolation Segment tile that ensures that the consul members are properly namespaced.

Upgrading from 1.10.0 to 1.10.1 is still supported, although you will experience router downtime while this upgrade occurs. The routers with the conflicting names will be removed, and a new set of routers will be created with a dedicated namespace for the Isolation Segment tile. In the time between the removal of the old routers, and the addition of the new routers, you will not be able to route traffic to the Isolation Segment applications through the dedicated Isolation Segment routers.

If you are only using compute isolation and not deploying the dedicated routing VMs, this issue does not apply to your deployment. The primary, “shared” ERT routing tier will experience no loss of application routing during this upgrade.

Component Version
Stemcell3363.10
cflinuxfs2-rootfs1.59.0
consul152
diego1.7.1
garden-runc1.1.1
loggregator77*
routing0.146.0*
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.10.0

Component Version
Stemcell3363.10
cflinuxfs2-rootfs1.50.0
consul152
diego1.7.1*
garden-runc1.1.1
loggregator77
routing0.146.0*
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

About PCF Isolation Segment

PCF Isolation Segment is a new tile available for installation with PCF v.1.10.

Isolation segments provide dedicated pools of resources where you can deploy apps and isolate workloads. Using isolation segments separates app resources as completely as if they were in different CF deployments but avoids redundant management and network complexity.

For more information on using isolation segments in your deployment, see the Managing Isolation Segments topic.

How to Install

The procedure for installing PCF Isolation Segment v1.10 is documented in the Installing PCF Isolation Segment topic.

To install a PCF Isolation Segment, you must first install PCF v1.10.

About Advanced Features

The Advanced Features section of the PCF Isolation Segment tile includes new functionality that may have certain constraints. Although these features are fully supported, Pivotal recommends caution when using them in production.

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