Installing Pivotal Platform on vSphere

Page last updated:

This guide describes how to install Pivotal Platform on vSphere.

If you experience a problem while following the steps below, see Diagnosing Problems in Pivotal Platform or the Known Issues sections of the following topics:

• Ops Manager v2.8 Release Notes in the Ops Manager documentation

• Pivotal Application Service v2.8 Release Notes in the PAS documentation

• Pivotal Isolation Segment v2.8 Release Notes in the PAS documentation

• Pivotal Application Service for Windows v2.8 Release Notes in the PASW documentation

• Release Notes in the Enterprise PKS documentation

Requirements

This section describes the resource requirements for installing Pivotal Platform.

Note: If you are using the Cisco Nexus 1000v Switch, see Using the Cisco Nexus 1000v Switch with Ops Manager for more information.

Note: When installing Ops Manager on a vSphere environment with multiple ESXi hosts, you must use network-attached or shared storage devices. Local storage devices do not support sharing across multiple ESXi hosts.

Resource Requirements

You can install Pivotal Platform with one of two runtimes. For more information about the requirements for each runtime, see the following:

• Pivotal Application Service (PAS): PAS on vSphere Requirements. For information requirements when deploying with NSX-T, see Requirements in Deploying PAS with NSX-T Networking.
• Enterprise Pivotal Container Service (Enterprise PKS):
  • Without NSX-T: vSphere Prerequisites and Resource Requirements
  • With NSX-T: See the Preparing to Install Enterprise PKS on vSphere with NSX-T section of Installing Enterprise PKS on vSphere with NSX-T Data Center.

vSphere Service Account Requirements

Ops Manager requires read/write permissions to the data center level of the vSphere Inventory Hierarchy to successfully install. Pivotal recommends defining a custom role for the service account that has all privileges for all objects in the data center, including propagating privileges to children.

Since Ops Manager passes all required credentials through to BOSH, you only need one service account with the required vSphere privileges to complete the installation. Setting up separate service accounts for Ops Manager and BOSH is not necessary or recommended.

For more information about service account requirements, see the following topics:

• PAS: vSphere Service Account Requirements
• Enterprise PKS: Create the BOSH/Ops Manager Service Account section of Preparing vSphere Before Deploying Enterprise PKS

Note: You can also apply the default VMware Administrator System Role to the service account to achieve the appropriate permission level.

vSphere Security Documents

• vSphere Security guide (PDF)
  This guide contains best practices for securing and managing a vSphere installation.

Procedure

This section describes the steps for installing Pivotal Platform.

Step 1: Install Ops Manager

Complete the following procedures to install Ops Manager on vSphere:

1. Deploying Ops Manager to vSphere

2. Configuring BOSH Director on vSphere

Additional Configuration

See the following topics for additional configuration options:

• Provisioning a Virtual Disk in vSphere
• Using the BOSH Resurrector
• Availability Zones in vSphere

Next Steps

After completing the procedures above, configure a runtime for Pivotal Platform. You can install the PAS runtime or the Enterprise PKS runtime.

For information about installing and configuring a runtime, see the following:

• PAS:
  • Without NSX-T: Configuring PAS
  • With NSX-T: Deploying PAS with NSX-T Networking

    Note: You must install the NSX-T tile before you install or Upgrade the PAS tile.

• Enterprise PKS:
  • Without NSX-T: Installing Enterprise PKS
  • With NSX-T: Deploying NSX-T for Enterprise PKS
• Installing and Configuring TAS for VMs on Windows
• Installing Small Footprint TAS for VMs