Using PCF Runtime for Windows
This documentation describes how operators install and manage Windows cells in Pivotal Cloud Foundry (PCF) with PCF Runtime for Windows, and how developers push .NET apps to Windows cells.
If you are currently using Windows cells deployed by the BOSH Release for Windows or Diego Windows, consult the list below:
- For customers who are using the BOSH Release for Windows, there is no migration path. To upgrade, you must destroy your deployment of Windows cells with the BOSH CLI and then perform a fresh install of the PCF Runtime for Windows tile.
- For customers who are using Diego Windows, follow the procedures in the Migrating from Diego Windows topic to migrate your applications to Windows cells deployed by the tile.
Operators who want to run Windows cells in PCF in order to enable developers to push .NET apps can deploy the PCF Runtime for Windows tile.
Deploying this tile creates a separate BOSH deployment populated with the Garden Windows release, which runs on a Windows cell built from a Windows stemcell.
Once the Windows cell is running, developers can specify a Windows stack when pushing .NET apps from the command line. PCF passes the app to the Windows cell in the Garden Windows BOSH deployment. The diagram below illustrates the process.
The recommended resource requirements for each Windows cell deployed by PCF Runtime for Windows are as follows:
- Disk size: 64 GB
- Memory: 16 GB
- CPUs: 4
The Elastic Runtime tile handles all of the credentials for PCF Runtime for Windows.
To rotate your credentials in PCF Runtime for Windows, re-deploy Elastic Runtime and PCF Runtime for Windows by navigating to the Ops Manager Installation Dashboard and clicking Apply Changes.