Architecture and Installation Overview

For PCF Architects and Operators

This guide shows you how to design a Pivotal Cloud Foundry (PCF) platform and install it on an IaaS. If you are doing this, you have one or both of the following roles:

  • Architects design a PCF platform. They know the IaaS that they will deploy it to, and what other relevant resources they have. In their design, they consider needs for the platform’s capacity, availability, security, geography, budget, and other factors. If they do not install PCF themselves, they provide the architectural specifications to whoever does.

  • Operators run a PCF platform, keep it up-to-date, monitor its health and performance, and fix any problems. They may also install the platform, or perform “Day 2” configurations that expand its functionality and integrate it with external systems.

This guide helps people in both roles create a PCF platform that does what they want it to. The contents of this guide follow the phases of a typical PCF planning and installation effort.

Note: Elastic Runtime has been renamed Pivotal Application Service.

Planning and Installation Overview

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 brief 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 CloudFormation 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.
  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.
    • 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 2012R2 enables PAS to manage Windows Server 2012 cells hosting .NET apps, and can also be replicated to create multiple isolated resource pools.
      • As with Isolation Segment, Operators replicate and configure a PAS for Windows 2012R2 tile for each new resource pool they want to create.
      • You must install PAS before you can install PAS for Windows 2012R2.
    • Small Footprint PAS is an alternative to PAS that uses far fewer VMs than PAS but has limitations.
  5. 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.
  6. 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.

Guide Contents

This guide has two parts. The first part explains the PCF planning and installation process, and the second describes the main tools that operators use when installing PCF.

Planning and Installation

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.

This guide follows this bottom-up progression:

After installing PCF, Operators install the software services that PCF developers use in their apps. These PCF 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.

The PCF Operator Guide explains how to maintain a running PCF platform, including monitoring, tuning, troubleshooting, and upgrading.

The PCF Security Guide explains how PCF security sytems work and how to keep your PCF platform secure.

Getting Started with PCF gives a high-level overview of how PCF works and explains how you can try a a simple deployment on your own local machine.

See Pivotal Cloud Foundry Documentation for all PCF documentation.

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