Installing and Configuring PASW

This topic describes how to install and configure the Pivotal Application Service for Windows (PASW) tile. The PASW tile installs Windows Diego Cells in your Pivotal Cloud Foundry (PCF) deployment.

If you have the PASW 2012 R2 tile installed, see Migrating from PASW 2012 R2 to PASW for more information about the changes in features and functionality between the two tile versions.

Step 1: Confirm Shared PAS Tile Settings

The PASW tile inherits settings from the Pivotal Application Service (PAS) tile. The PAS tile settings in this section affect the Windows Diego Cells that the PASW tile deploys.

Review the following settings in your PAS tile. If necessary, update PAS settings to fit your intended PASW deployment and click Apply Changes.

System Logging

In the System Logging pane, if you configure an external syslog aggregator, PAS drains logs from Windows Diego Cells as well as non-Windows Diego Cells. For more information, see Logging and Metrics.

Disable SSL Certificate Verification

In the Networking pane, if you select the Disable SSL certificate verification for this environment checkbox, SSL certificate verification is disabled for Windows Diego Cells. For more information, see the Procedure: Terminate SSL/TLS at HAProxy section of Configuring SSL/TLS Termination at HAProxy.

Note: Only disable SSL certificate verification for development and testing environments. Do not select Disable SSL certificate verification for this environment for production environments.

Step 2: Install the Tile

  1. Download the Pivotal Application Service for Windows product file from Pivotal Network.

  2. Within Pivotal Application Service for Windows, download the Windows FS Injector tool for your workstation OS.

    The Injector tool, winfs-injector, is an executable binary that adds the Windows Server container base image into the product file. This step requires internet access and can take up to 20 minutes.

    Note: You need the git and tar executables in your %PATH% to run winfs-injector.exe. For example, copy git.exe and tar.exe to a directory in your %PATH%.

  3. To add the Windows Server container base image to the product file, run the following command:

    winfs-injector --input-tile PASW-DOWNLOAD-PATH --output-tile PASW-IMPORTABLE-PATH
    

    Where:

    • PASW-DOWNLOAD-PATH is the path and filename to the PASW product file you downloaded.
    • PASW-IMPORTABLE-PATH is the desired output path for the importable product file.

    For example:

    C:\Users\admin> winfs-injector --input-tile ^
    c:\temp\pas-windows-2.6.0-build.1.pivotal ^
    --output-tile c:\temp\pas-windows-2.6.0-build.1-INJECTED.pivotal
    

    For information about troubleshooting winfs-injector, see Missing Local Certificates for Windows File System Injector in Troubleshooting Windows Cells.

  4. Navigate to the Ops Manager Installation Dashboard and click Import a Product.

  5. To add the PASW tile to the Import a Product product list, select the importable PASW-IMPORTABLE-PATH file on your workstation.

  6. To add the PASW tile to your staging area, click + under the Pivotal Application Service for Windows product listing.

Step 3: Configure the Tile

  1. Click the newly added Pivotal Application Service for Windows tile.

    Pcf windows tile orange

  2. Select Assign AZs and Networks or Assign Networks. The name of the pane varies depending on your IaaS.

  3. Assign your AZs and networks and click Save.

  4. Select VM Options.

    Vm options

  5. Select one of the following for Manage Administrator Password:

    • To randomize the admin password, select Use random password. If you select this option, the admin password is not retrievable by an operator. This is the default selection.
    • To set the same admin password for every Windows Diego Cell, select Set the password. If you select this option, this password can be used to access any Windows Diego Cell. For example, you can use this password to open Remote Desktop Protocol (RDP) sessions.
  6. (Optional) To start the Microsoft beta port of the OpenSSH daemon on port 22 on all VMs, select the BETA: Enable BOSH-native SSH support on all VMs checkbox. If you select this option, users can SSH into Windows VMs with the bosh ssh command, and enter a CMD terminal as an admin user. They can then run powershell.exe to start a PowerShell session.

    Note: This feature is in beta and not considered production-ready.

  7. (Optional) To enable all VMs to support connection through RDP, select Enable Remote Desktop Protocol.

  8. (Optional) To configure a Key Management Service (KMS) that your volume-licensed Windows Diego Cell can register with, do the following:

    1. Select Enable.
    2. For the Host field, enter the KMS hostname.
    3. For the Port field, enter the port number. The default port number is 1688.

    The enable KMS text fields: host and port

  9. Click Save.

  10. (Optional) To deploy your PASW app workloads to an isolation segment, select Application Containers and perform the steps in the Assign a Tile to an Isolation Segment section of Windows Cells in Isolation Segments.

  11. (Optional) To configure Windows Diego Cells to send Windows Event logs to an external syslog server, select System Logging and perform the steps in the Send Cell Logs to a Syslog Server section of Troubleshooting Windows Cells.

  12. Select Smoke Tests. The smoke tests radio buttons: Temporary space within the system organization and Specified org and space

  13. Select one of the following locations for smoke tests to run:

    • To run smoke tests in a temporary space in the default org, select Temporary space within the system organization. PASW deletes the space after smoke tests finish.
    • To specify the org and space where smoke tests run, select Specified org and space. You must enter a domain available for routing and that domain must be accessible to the org. Enter the following:
      • In the Organization field, enter the Application Service org to use when running tests.
      • In the Space field, enter the Application Service space to use when running tests.
      • In the Domain field, enter the domain that the org has access to for running smoke tests.
  14. (Optional) To configure memory and disk overcommit for your Windows Diego Cells, select Advanced Features and do the following:

    1. Enter the total desired amount of Diego Cell memory in the Cell Memory Capacity (MB) field. For the current cell memory capacity settings, see the Windows Diego Cell row on the Resource Config pane.
    2. Enter the total desired amount of Diego Cell disk capacity in the Cell Disk Capacity (MB) field. For the current cell disk capacity settings, see the Windows Diego Cell row on the Resource Config pane.

      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.

      Advanced features
    3. Click Save.
  15. Select Errands.

    1. To ensure that you receive the most up-to-date HWC buildpack, set the Install HWC Buildpack Errand to On.
    2. To ensure that a smoke test is run against your Application Service installation, set the Smoke Test Errand to On.

    Post deploy errands

  16. Click Save.

Step 4: Configure Tile Resources

To configure your tile resources, do the following:

  1. Navigate to the Resource Config pane of the PASW tile.
  2. Use the dropdown menus to configure Windows Diego Cell. For more information, see Disk Size of Windows Diego Cells below.
  3. Click Save.

Note: Provision your Master Compilation Job with at least 100 GB of disk space.

Disk Size of Windows Diego Cells

Windows stemcells in the v2019.x line support ephemeral disks.

See the following table for the recommended Windows Diego Cell disk size for your IaaS:

IaaS Recommended Windows Diego Cell Disk Size
AWS 100 GB
Azure 150 GB
GCP 150 GB
vSphere 100 GB

Note: If you use vSphere, you must create your own stemcell. The default root disk size of Windows stemcells v2019.x line is 30 GB. Pivotal recommends setting the root disk size of your Windows stemcell for vSphere to 30 GB. For more information, see Creating a Windows Stemcell for vSphere Manually or Creating a Windows Stemcell for vSphere Using stembuild (Beta).

Step 5: Upload the Stemcell

  1. Go to Stemcell Library.

  2. Retrieve the stemcell that you downloaded or created in Downloading or Creating a Windows Stemcell.

  3. Follow the steps in Importing and Managing Stemcells to upload the Windows stemcell to Pivotal Application Service for Windows.

Step 6: Deploy the Tile

  1. Return to the Ops Manager Installation Dashboard.
  2. Select Review Pending Changes.
  3. Select the PASW tile and review the changes. For more information, see Reviewing Pending Product Changes.
  4. Select Apply Changes to install the Pivotal Application Service for Windows tile.

Step 7: (Optional) Create More Tiles

To run Windows Diego Cells in multiple isolation segments, you must create and configure additional PASW tiles. For more information, see Windows Cells in Isolation Segments.

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