LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.9

Deploying BOSH Release for Windows

This topic describes how to deploy the BOSH Release for Windows to install Windows cells on your Pivotal Cloud Foundry (PCF) deployment.

Note: The BOSH Release for Windows is currently in beta.

Requirements

To deploy the BOSH Release for Windows, you must have PCF 1.8 or later deployed to vSphere or Amazon Web Services (AWS).

  • If your PCF deployment runs on vSphere, you must build your own stemcell by following the steps in the Building a Windows Stemcell topic before performing the procedures below.
  • If your PCF deployment runs on AWS, you can use the stemcell included in the BOSH Release for Windows, but your deployment must be in us-east-1, us-west-2, or eu-west-1.

Note: Once your Windows cell is running, you must disable FIPS as a Group Policy setting. If you fail to disable FIPS as a Group Policy setting, Garden Windows will not work.

Step 1: Prepare to Deploy

  1. Ensure that you created a service network during your Ops Manager installation. A service network specifies a CIDR range within which Ops Manager does not provision VMs. You create a service network by selecting a checkbox in the Create Networks section of Ops Manager. See your IaaS-specific topic for configuring Ops Manager from the Installing Pivotal Cloud Foundry topic for more information.

  2. Download all of the BOSH Release for Windows files from Pivotal Network to a single directory.

  3. Prepare to SCP onto your Ops Manager VM.

    • For AWS, perform the following steps:
      1. In the EC2 instances page of your AWS Console, locate the FQDN of the Ops Manager VM.
      2. Locate the ops_mgr.pem private key file you used when installing Ops Manager, and ensure that you have added it to your list of private keys with the following terminal command:
        $ ssh-add ops_mgr.pem
        
    • For vSphere, perform the following steps:
      1. In vCenter, locate the FQDN of the Ops Manager VM.
      2. Locate the credentials you used to import the PCF .ova or .ovf file into your virtualization system.

Step 2: Deploy BOSH Release for Windows

  1. In a terminal window, navigate to the directory where you downloaded the BOSH Release for Windows files. For example, if you downloaded the files to the ~/bosh-windows directory, run the following command:

    $ cd ~/bosh-windows
    

  2. Securely copy garden-windows-0.x.tgz, generate_manifest.rb, and your stemcell file to your Ops Manager VM as ubuntu@OPS-MANAGER-FQDN.

    Note: For AWS, use the stemcell included in the BOSH Release for Windows. For vSphere, use the stemcell you built in the Building a Windows Stemcell topic.

    The following example securely copies an AWS stemcell:

    $ scp garden-windows-0.0.6.tgz generate_manifest.rb 
    light-bosh-stemcell-0.0.46-aws-xen-hvm-windows2012R2-go_agent.tgz 
    ubuntu@pcf.example.com:~
    

    For vSphere, enter the password that you set during the .ova deployment into vCenter when prompted.

  3. Follow the steps in the Log into BOSH section of the Advanced Troubleshooting with the BOSH CLI topic to target and log in to the BOSH Director. The steps vary slightly depending on whether your PCF deployment uses internal authentication or an external user store.

  4. After you successfully log in to the BOSH Director, use the bosh upload stemcell YOUR-WINDOWS-STEMCELL.tgz command to upload the Windows stemcell to BOSH. Replace YOUR-WINDOWS-STEMCELL.tgz with the name of your Windows stemcell.

    $ bosh upload stemcell YOUR-WINDOWS-STEMCELL.tgz
    

    Note: For AWS, your deployment must be in us-east-1, us-west-2, or eu-west-1 to upload the stemcell to BOSH successfully.

  5. Use the bosh download manifest YOUR-PCF-DEPLOYMENT YOUR-PCF-MANIFEST.yml command to download the manifest of your PCF deployment. Replace YOUR-PCF-DEPLOYMENT with the name of your PCF deployment, and YOUR-PCF-MANIFEST.yml with a manifest name to use to later steps.

    $ bosh download manifest YOUR-PCF-DEPLOYMENT YOUR-PCF-MANIFEST.yml
    

    Note: You must know the name of your PCF deployment to download the manifest. To retrieve it, run bosh deployments to list your deployments and locate the name of your PCF deployment.

  6. Use the manifest generation script included in the BOSH Release for Windows to generate a manifest for your deployment. You must specify either vsphere or aws depending on your IaaS. The following example uses AWS:

    $ ./generate-manifest YOUR-PCF-MANIFEST.yml aws > garden-windows.yml
    
  7. In a text editor, modify the generated manifest to replace the network name with the name of your service network.

  8. Upload the Garden Windows release to BOSH:

    $ bosh upload release garden-windows-y-x.tgz 
    

  9. Deploy Garden Windows:

    $ bosh -d garden-windows.yml deploy
    

Was this helpful?
What can we do to improve?
View the source for this page in GitHub