Deploying BOSH and Ops Manager

This documentation explains how to deploy BOSH and Ops Manager, the foundation of a Pivotal Cloud Foundry (PCF) platform.


BOSH and Ops Manager provide the foundation for PCF, you install them first when you install PCF.

  • BOSH is an open-source tool that lets you run software systems in the cloud.

    • BOSH and its IaaS-specific Cloud Provider Interfaces (CPIs) are what enable PCF to run on multiple IaaSes.
    • See Deploying Software with BOSH for a mini overview of how you use BOSH to run software in the cloud.
  • Ops Manager is a GUI application deployed by BOSH that streamlines deploying subsequent software to the cloud via BOSH.

    • For routine tasks, operators can use the Ops Manager interface instead of the BOSH command-line interface (CLI) or BOSH API.
    • Ops Manager represents PCF products as tiles with multiple configuration panes that let you input or select configuration values needed for the product.
    • Ops Manager generates BOSH manifests containing the user-supplied configuration values, and sends them to the Director.
    • After you install Ops Manager and BOSH, you use Ops Manager to deploy almost all PCF products.
  • Deploying Ops Manager deploys both BOSH and Ops Manager with a single procedure.

    • You deploy BOSH and Ops Manager by logging into your IaaS and allocating the network addresses, VMs, user accounts, and other resources needed to support PCF.
    • On AWS, you can deploy Ops Manager manually, or automatically with a Terraform template.
    • On Azure, you can deploy Ops Manager manually, or automatically with an Azure Resource Manager (ARM) template. On Azure Government Cloud and Azure Germany, you can only deploy Ops Manager manually.

For all of the above, the specifics depend on the IaaS that you are deploying PCF to. So the contents of this documentation are organized by IaaS.


Deploying Software with BOSH

The following describes how you can use BOSH to run software in the cloud:

  1. You create a BOSH release, a directory that contains your software and anything that it depends on or needs to run on generic, empty VMs.

  2. You create a manifest .yml file that identifies the component processes in the BOSH release, specifies the VMs they run on, how they communicate, how to start them up and shut them down, and any other configuration specifics that they need.

  3. Using the BOSH command-line interface (CLI) or API, you upload the BOSH release and send the manifest to the Director, BOSH’s executive process.

  4. The Director provisions what it needs from the IaaS, deploys your software to run in the cloud, and heals automatically when VMs go down.

  5. BOSH CLI and API commands let you control BOSH-managed processes and allocate or release IaaS resources.

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