PAS for Windows v2.3 Release Notes

This topic contains release notes for Pivotal Application Service for Windows (PASW) v2.3.x.

Releases

2.3.4

  • [Security Fix] Rotate diego intermediate CA before current certificate expires
  • [Feature Improvement] Smoke tests for PASW are run as a post-deploy errand
  • Bump hwc-offline-buildpack to version 3.1.1
  • Bump windowsfs-release to version 1.6.0
Component Version
windows1803 stemcell1803.3
consul195
diego2.18.0
event-log0.7.0
garden-runc1.16.1
hwc-offline-buildpack3.1.1
loggregator103.3
winc1.7.0
windows-utilities0.10.0
windowsfs-release1.6.0

2.3.3

  • [Feature Improvement] Operators can specify the Diego executor properties for memory usage and disk capacity in order to enable finer grained resource usage strategies
  • [Bug Fix] Fix issue that could cause application deployments to fail on some infrastructure due to incorrect MTU detection
  • Bump windows1803 stemcell to version 1803.3
  • Bump winc to version 1.7.0
Component Version
windows1803 stemcell1803.3
consul195
diego2.18.0
event-log0.7.0
garden-runc1.16.1
hwc-offline-buildpack3.0.3
loggregator103.3
winc1.7.0
windows-utilities0.10.0
windowsfs-release1.5.0

2.3.2

  • [Bug Fix] Fix issue in loggregator where availability zone (AZ) names with special characters could cause metron agent job to fail
  • Bump hwc-offline-buildpack to version 3.0.3
  • Bump loggregator to version 103.3
  • Bump windowsfs-release to version 1.5.0. This includes Microsoft VS 2017 C++ Redistributable DLLs version 15.
Component Version
windows1803 stemcell1803.2
consul195
diego2.18.0
event-log0.7.0
garden-runc1.16.1
hwc-offline-buildpack3.0.3
loggregator103.3
winc1.5.0
windows-utilities0.10.0
windowsfs-release1.5.0

2.3.1

  • Bump diego to version 2.18.0
  • Bump hwc-offline-buildpack to version 3.0.2
  • Bump windows1803fs to version 1.4.0
  • Bump stemcell windows1803 to version 1803.2
Component Version
stemcell1803.2
consul195
diego2.18.0
event_log0.7.0
garden-runc1.16.1
hwc-offline-buildpack3.0.2
loggregator103.0
winc1.5.0
windows1803fs1.4.0
windows-utilities0.10.0
\* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

2.3.0

Component Version
stemcell1803.1
consul195
diego2.16.0
event_log0.7.0
garden-runc1.16.1
hwc-offline-buildpack3.0.0
loggregator103.0
winc1.5.0
windows-utilities0.10.0
\* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

How to Upgrade

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

New Features in PASW v2.3

PASW v2.3 includes the following major features:

Support for Multiple Buildpacks

PASW v2.3 introduces support for pushing a .NET app with multiple buildpacks.

For more information, see Pushing an Application with Multiple Buildpacks.

Ephemeral Disk Configuration Options

Operators can now use ephemeral disk configuration options for Windows Server cells.

HTTP Compression in the HWC Buildpack

PASW v2.3 enables the HTTP compression module from Internet Information Services (IIS), which enables gzip compression for static assets and dynamic content in the HWC buildpack.

Windows Server version 1803

PASW v2.3 includes the latest version of Windows Server (version 1803). The container image for Windows Server version 1803 is 30% smaller than the previous release (version 1709), reducing the memory footprint required for .NET apps. The release also includes optimizations for containers, improved compatibility, and enhanced debugging tools.

For more information, see What’s New in Windows Server version 1803 in the Microsoft documentation.

Known Issues

This section includes known issues with PASW v2.3.

Update Runtime Config of ClamAV

If you are using the ClamAV Add-on for PCF, you must update your runtime config before upgrading to PASW v2.3.

If you upgrade to PASW v2.3 without first updating the runtime config, then your Windows VMs will not be protected by ClamAV.

For more information about how to update your runtime config, see Updating ClamAV Add-on for PCF to Run with PAS for Windows v2.3 in the ClamAV documentation.

Default DNS Configuration on AWS Does Not Work

On AWS, the default DNS configuration of 169.254.169.253 does not work.

You must configure DNS to use another address, such as 10.0.0.2. For more information, see Step 5: Create Networks Page of Configuring BOSH Director on AWS Using Terraform.

Intermittent Deploy Failure on Azure with Compilation Timeout

When deploying on Azure, the BOSH compilation of some releases may time out and cause the deploy to fail.

To resolve this issue, perform the following steps:

  1. Navigate to the Ops Manager Installation Dashboard and log in.
  2. Click the BOSH Director for Azure tile.
  3. Click Resource Config.
  4. Select a larger VM Type for the BOSH Director job, such as DS5_v2.
  5. Return to the Ops Manager Installation Dashboard and click Review Pending Changes and then Apply Changes to redeploy.
Create a pull request or raise an issue on the source for this page in GitHub