Deploying PCF Runtime for Windows
This topic describes how to install and configure the Pivotal Cloud Foundry (PCF) Runtime for Windows v1.12 tile. The PCF Runtime for Windows tile installs Windows cells on your PCF deployment.
To install the PCF Runtime for Windows v1.12 tile, you must have Ops Manager v1.12.0 or later and Elastic Runtime v1.12.0 or later deployed to vSphere, Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure.
There are two settings in the Elastic Runtime tile that affect the Windows cells installed by the PCF Runtime for Windows tile. Configure these settings as desired:
- In the Networking section, if you select the Disable SSL certificate verification for this environment checkbox, SSL certificate verification is disabled for Windows cells.
- In the System Logging section, if you configure an external syslog aggregator, logs are drained from Windows cells as well as non-Windows cells.
Download the product file from the Pivotal Cloud Foundry Runtime for Windows section of Pivotal Network.
Navigate to the Ops Manager Installation Dashboard and click Import a Product to upload the product file.
Click + under the uploaded PCF Windows Runtime tile to add it to your staging area.
Click the newly added PCF Runtime for Windows tile.
Click Assign AZs and Networks or Assign Networks. The name of the section varies depending on your IaaS.
Assign your AZs and networks and click Save.
Click VM Options.
Specify how you would like to manage the administrator password for your Windows VMs. The default option is to Use the Windows default password.
(Optional) Select the BETA: Enable BOSH-native SSH support on all VMs checkbox to start the Microsoft beta port of the OpenSSH daemon on port 22 on all VMs. Users will be able to SSH onto Windows VMs with the
bosh sshcommand, and enter a CMD terminal as an administrator user. They can then run
powershell.exeto start a PowerShell session.
Note: This feature is beta and not considered production-ready.
(Optional) If you want your PCF Runtime for Windows application workloads to be deployed to an isolation segment, perform the following steps:
Click Application Containers.
Under Segment Name, enter a name for your isolation segment. Ensure that this name is unique across your PCF deployment.
Perform the steps in the Create an Isolation Segment section of the Managing Isolation Segments topic to create the isolation segment in the Cloud Controller Database (CCDB).
Click Errands. Pivotal recommends that you set the Install HWC Buildpack Errand to On. This ensures that you receive the most up-to-date HWC Buildpack.
Click Resource Config and adjust the number and VM types of your Windows cells as needed.
Click Stemcell. Record the stemcell version number required by the tile.
Retrieve the stemcell by following the steps below for your IaaS.
Return to the Ops Manager Installation Dashboard and click Apply Changes to install the PCF Runtime for Windows tile.
After you have deployed the PCF Runtime for Windows tile, developers can then push .NET applications to Windows cells. For more information, see the Deploying .NET Apps to Windows Cells topic.
If you want to create multiple isolation segments for the Windows tile, perform the following steps to copy the PCF Runtime for Windows tile with the Replicator tool:
Download the Replicator tool from the Pivotal Cloud Foundry Runtime for Windows section of Pivotal Network.
Navigate to the directory where you downloaded the Replicator tool.
Replicate the tile:
./replicator \ -name "YOUR-NAME" \ -path /PATH/TO/ORIGINAL.pivotal \ -output /PATH/TO/COPY.pivotal
Replace the values above with the following:
YOUR-NAME: Provide a unique name for the new PCF Runtime for Windows tile. The name must be ten characters or less and only contain alphanumeric characters, dashes, underscores, and spaces.
/PATH/TO/ORIGINAL: Provide the absolute path to the original PCF Runtime for Windows tile you downloaded from Pivotal Network.
/PATH/TO/COPY: Provide the absolute path for the copy of the PCF Runtime for Windows tile that the Replicator tool produces.
Follow the procedures in this topic using the new
.pivotalfile, starting with Step 1.