PAS for Windows v2.4 Release Notes
This topic contains release notes for Pivotal Application Service (PAS) for Windows.
- [Feature Improvement] Enable SMB
net use-style mounting for IP-address based UNC paths on Windows 2016 cells
- Bump hwc-offline-buildpack to version
- Bump windowsfs-release to version
[Feature] Enable fetching logs and metrics via gRPC
Add new release loggregator-agent at version
Removed consul release
Bump cf-windows-smoke-tests to version
Bump hwc-offline-buildpack to version
Bump windowsfs-release to version
Bump windows1803 stemcell to version
HWC buildpack supports http compression for arbitrary MIME types
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.
PAS for Windows v2.4 includes the following major 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.
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.
Metrics emitted from PAS for Windows are now tagged with the BOSH deployment name of your PAS for Windows tile.
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
cfas the deployment name.
Note: Enable the
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
Pivotal does not recommend enabling the
cf value as a permanent solution.
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 apps using
cf push -s windows. Pushing apps with this command ensures that you are pushing with the Windows stack with the latest
For more information, see Step 2: Push App to PAS for Windows Cells in Migrating Apps to PAS for Windows.
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.