PCF Runtime for Windows v1.11 Release Notes

Releases

1.11.6

  • Bumps stemcell to v1200.4.

Component Version
Stemcell1200.4
consul167
diego1.23.2
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator89*
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.11.5

  • [Bug Fix] Loggregator API counters will now include a correct delta.
  • Removes the “Advanced Features” section as these features do not have any impact on Diego functionality.

Component Version
Stemcell1200.0
consul167
diego1.23.2
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator89*
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.11.4

  • [Bug Fix] Bumps diego-release to v1.23.2 to resolve a number of issues including:
    • improving locket stability during MySQL updates
    • reporting the correct result of running tasks on Windows cells
    • resolution of a race condition in the process launching code that could cause process failures
    • improvements to the healthcheck error messaging
    • removing the extraneous “cancelled” message in logs when applications crash
    • prefixing process errors with their log source
    • removing exit codes from healthcheck output when an application fails its healthcheck

Component Version
Stemcell1200.0
consul167
diego1.23.2
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator89
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.11.3

  • Bumps garden-windows-release to v0.7.0. Release Notes.
  • [Bug Fix] Bumps hwc-offline-buildpack-release to v2.3.8. Resolves a stack overflow bug in .Net applications.

Component Version
Stemcell1200.0
consul167
diego1.18.1
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator89
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.11.2

  • Bumps the stemcell to v1200.0. Release Notes
  • Sets the default max-in-flight value for the Diego Cells to 4%. Operators can still use the Ops Manager API to configure this setting to fit their needs. The max-in-flight percentage for the Diego Cell job in the Elastic Runtime has been set to 10% since 1.9.0, but we’ve seen especially in larger environments that having the percentage this high can cause some problems:
    • Many simultaneous VM creates/deletes and BOSH blob updates can place significant stress on the underlying infrastructure, especially on vSphere which has a greater probability of being under-provisioned.
    • The cells that are draining are no longer available for allocation, resulting in a 10% decrease in total memory and disk capacity during the deployment. This can cause deployments to no longer have sufficient total capacity to run all the work, or to have insufficient headroom to place larger workloads successfully.

Component Version
Stemcell1200.0
consul167
diego1.18.1
garden-windows0.4.0
hwc-offline-buildpack2.3.4
loggregator89
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.11.1

  • Bumps the diego-release to v1.18.1.

Component Version
Stemcell1079.0
consul167
diego1.18.1
garden-windows0.4.0
hwc-offline-buildpack2.3.4
loggregator89
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.11.0

Component Version
Stemcell1079.0
consul167
diego1.16.1
garden-windows0.4.0
hwc-offline-buildpack2.3.4
loggregator89
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

Operators can install PCF Runtime for Windows on vSphere, Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure. See the Deploying PCF Runtime for Windows topic for more information.

How to Upgrade

The PCF Runtime for Windows v1.11 tile is available with the release of Pivotal Cloud Foundry (PCF) version v1.11. To use the PCF Runtime for Windows tile, you need Ops Manager v1.11.0 or later and Elastic Runtime v1.11.0 or later.

For information about upgrading to PCF Runtime for Windows v1.11.0, see the Upgrading Windows Cells topic in the PCF Runtime for Windows documentation.

About Advanced Features

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

New Features in PCF Runtime for Windows v1.11

SHA2 Checksum

Operators can verify the data integrity of the PCF Runtime for Windows tile using the SHA2 checksum of the file, rather than the MD5 checksum used in previous releases.

Isolation Segment

Operators can follow these steps to deploy their PCF Runtime for Windows app workloads to an isolation segment:

  1. Enter a Segment Name in the Application Containers pane of the Windows Runtime tile.
  2. Complete the procedure in the Create an Isolation Segment section of the Managing Isolation Segments topic to create the isolation segment in the Cloud Controller Database (CCDB).

Cell-local Route Emitters

The Route Emitter is now co-located on the Diego Cell for which it emits app routes. This improves the availability of the Route Emitter and reduces the impact of downtime from this component.

In previous versions of the PCF Runtime for Windows tile, Diego Cells relied on the Route Emitter component on the Diego Brain in the Elastic Runtime tile to notify the Router of application routes. If the Route Emitter became unavailable, routes could be lost from the Router route table.

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