PCF Planning and Installation

This topic provides an overview of how to install and configure Pivotal Cloud Foundry (PCF).

PCF Installation Sequence

PCF is a suite of products that runs on multiple IaaSes. Planning and installing PCF means building layers from the bottom up, starting with the details of your IaaS and ending with “Day 2” configurations that you perform on a installed and running PCF deployment.

Here’s the typical PCF planning and installation process:

  1. Plan

    • Review the Requirements for your IaaS (AWS, Azure, GCP, OpenStack, vSphere).
    • Refer to the Reference Architecture for your IaaS.
    • Assess your platform needs, including capacity, availability, container support, host OS, resource isolation, and geographical distribution. Discuss with your Pivotal contact.
  2. Deploy BOSH and Ops Manager

    • 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 with BOSH for a description of the BOSH deployment process.
    • Ops Manager is a GUI application deployed by BOSH that streamlines deploying subsequent software to the cloud via BOSH.
      • 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.
      • 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 a Terraform template. On Azure Government Cloud and Azure Germany, you can only deploy Ops Manager manually.
  3. Deploy BOSH Add-ons (Optional)

    • BOSH add-ons include the IPsec, ClamAV, and File Integrity Monitoring, which enhance PCF platform security and security logging.
    • You deploy these add-ons via BOSH rather than installing them with Ops Manager tiles.
  4. Install Runtimes

    • PAS (Pivotal Application Service) lets developers develop and manage cloud-native apps and software services.
      • PAS is based on the Cloud Foundry Foundation’s open-source Application Runtime (formerly Elastic Runtime) project.
    • PKS (Pivotal Container Service) uses BOSH to run and manage Kubernetes container clusters.
      • PKS is based on the Cloud Foundry Foundation’s open-source Container Runtime (formerly Kubo) project.
    • PCF Isolation Segment lets a single PAS deployment run apps from separate, isolated pools of computing, routing, and logging resources.
      • Operators replicate and configure an Isolation Segment tile for each new resource pool they want to create.
      • You must install PAS before you can install Isolation Segment.
    • PAS for Windows enables PAS to manage Windows Server 2016 (1709) cells hosting .NET apps, and can also be replicated to create multiple isolated resource pools.
      • Operators replicate and configure a PAS for Windows tile for each new resource pool they want to create.
      • You must install PAS before you can install PAS for Windows.
    • Small Footprint PAS is an alternative to PAS that uses far fewer VMs than PAS but has limitations.
  5. Day 2 Configurations

    • Day 2 configurations set up internal operations and external integrations on a running PCF platform.
      • Examples include front-end configuration, user accounts, logging and monitoring, internal security, and container and stemcell images.
  6. Install Services

    • Install software services for PCF developers to use in their apps.
      • Services include the databases, caches, and message brokers that stateless cloud apps rely on to save information.
      • Installing and managing software services on PCF is an ongoing process, and is covered in the PCF Operator Guide.

Deploying with BOSH

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

  1. To use BOSH, you create a manifest .yml file that specifies your software system’s component processes, the VMs they run on, how they communicate, and anything else they need.

  2. The BOSH command-line interface (CLI) or API sends the manifest to the Director, BOSH’s executive process.

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

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

Backing Up

Monitoring, Logging, and Troubleshooting

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