PAS for Windows v2.4 Release Notes

This topic contains release notes for Pivotal Application Service (PAS) for Windows.

Releases

2.4.1

  • [Feature Improvement] Enable SMB net use-style mounting for IP-address based UNC paths on Windows 2016 cells
  • Bump hwc-offline-buildpack to version 3.1.2
  • Bump windowsfs-release to version 1.8.0
Component Version
windows1803 stemcell1803.4
cf-windows-smoke-tests40.0.40
diego2.22.0
event-log0.7.0
garden-runc1.16.7
hwc-offline-buildpack3.1.2
loggregator-agent2.2
loggregator103.3
winc1.7.0
windows-utilities0.11.0
windowsfs-release1.8.0

2.4.0

See also:

  • Breaking Changes

  • [Feature] Enable fetching logs and metrics via gRPC

  • Add new release loggregator-agent at version 2.2

  • Removed consul release

  • Bump cf-windows-smoke-tests to version 40.0.40

  • Bump hwc-offline-buildpack to version 3.1.1

  • Bump windowsfs-release to version 1.7.0

  • Bump windows1803 stemcell to version 1803.4

  • HWC buildpack supports http compression for arbitrary MIME types

Component Version
windows1803 stemcell1803.4
cf-windows-smoke-tests40.0.40
diego2.22.0
event-log0.7.0
garden-runc1.16.7
hwc-offline-buildpack3.1.1
loggregator-agent2.2
loggregator103.3
winc1.7.0
windows-utilities0.11.0
windowsfs-release1.7.0

How to Upgrade

The Pivotal Application Service (PAS) for Windows v2.4 tile is available with the release of Pivotal Cloud Foundry (PCF) version v2.4. To use the PAS for Windows tile, you need Ops Manager v2.4 or later and PAS v2.4 or later.

New Features in PAS for Windows v2.4

PAS for Windows v2.4 includes the following major features:

About Advanced Features

The Advanced Features pane of the PAS 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.

Memory and Disk Overcommit for Diego Cells

You can now enable memory and disk overcommit for Diego cells. If you want to configure this feature, use the Cell Memory Capacity (MB) and Cell Disk Capacity (MB) fields on the Advanced Features pane of the PAS for Windows tile.

Note: Due to the risk of app failure and the deployment-specific nature of disk and memory use, Pivotal has no recommendation about how much, if any, memory or disk space to overcommit.

For more information, see the Configure the Tile section of Installing and Configuring PAS for Windows.

Uniquely Identify Metrics from PAS for Windows

Metrics emitted from PAS for Windows are now tagged with the BOSH deployment name of your PAS for Windows tile. For example, pas-windows-GUID. With a GUID, you can uniquely identify your metrics by tile. In PAS for Windows v2.3 and earlier, metrics use the cf tag as the deployment name.

This feature is enabled by default in new deployments of PAS for Windows v2.4. For upgrades to PAS for Windows v2.4, the feature is disabled by default. You can configure this setting in the Advanced Features pane of the PAS for Windows tile:

  • If the Use “cf” as deployment name in emitted metrics instead of unique name checkbox is disabled, PAS for Windows metrics are tagged with the BOSH deployment name of your PAS for Windows tile.
  • If the Use “cf” as deployment name in emitted metrics instead of unique name checkbox is enabled, PAS for Windows metrics are tagged with cf as the deployment name.

Note: Enable the cf value only if it is required for backward compatibility with previous versions of PCF or if you have scripts that rely on metrics with cf as the value for deployment. Pivotal does not recommend enabling the cf value as a permanent solution.

Smoke Tests are Available

Smoke Tests are available in PAS for Windows v2.4 to verify cf push and app routability at deploy time. You have the option of choosing a temporary or specified organization and space for smoke tests. The Smoke Test Errand can be configured within the PAS for Windows Tile. Smoke Tests are turned off by default.

For more information on Smoke Tests, see Step 3: Configure the Tile in Installing and Configuring PAS for Windows.

Developers Can Push with Default Windows Stack

Developers can push apps using cf push -s windows. Pushing apps with this command ensures that you are pushing with the Windows stack with the latest rootfs.

For more information, see Step 2: Push App to PAS for Windows Cells in Migrating Apps to PAS for Windows.

SMB Support for Windows Containers (Beta)

SMB mounting allows developers to bind existing SMB shares to their containerized apps. Previously, SMB shares were only accessible by using the SharpCIFS library. PASW v2.4.0 natively supports SMB mounting.

This enables usage of the net use command. This is currently limited to IP address-based UNC paths.

For more information, see SMB (WINDOWS) FILE SHARES in the .NET on Pivotal Cloud Foundry cookbook.

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