Planning Your Pivotal Platform Deployment

Page last updated:

This documentation provides an overview of how to plan a Pivotal Platform installation.

Overview

In planning a Pivotal Platform installation, you should:

  • Review the Requirements for your IaaS.

  • 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.

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

Contents

General Requirements

The general requirements for deploying and managing a Pivotal Platform deployment with Ops Manager and Pivotal Application Service (PAS) are:

  • A wildcard DNS record that points to your Gorouter or load balancer. Alternatively, you can use a service such as xip.io. For example, 203.0.113.0.xip.io.

    • PAS gives each app its own hostname in your app domain.
    • With a wildcard DNS record, every hostname in your domain resolves to the IP address of your Gorouter or load balancer, and you do not need to configure an A record for each app hostname. For example, if you create a DNS record *.example.com pointing to your load balancer or Gorouter, every app deployed to the example.com domain resolves to the IP address of your Gorouter.
  • At least one wildcard TLS certificate that matches the DNS record you set up above, *.example.com.

  • Sufficient IP allocation:

    • One static IP address for either HAProxy or one of your Gorouters.
    • One static IP address for each job in the Ops Manager tile. For a full list, see the Resource Config pane for each tile.
    • One static IP address for each job listed below:
      • Consul
      • NATS
      • File Storage
      • MySQL Proxy
      • MySQL Server
      • Backup Restore Node
      • HAProxy
      • Router
      • MySQL Monitor
      • Diego Brain
      • TCP Router
    • One IP for each VM instance created by the service.
    • An additional IP address for each compilation worker. The formula for total IPs needed is IPs needed = static IPs + VM instances + compilation workers.

      Note: Pivotal recommends that you allocate at least 36 dynamic IP addresses when deploying Ops Manager and PAS. BOSH requires additional dynamic IP addresses during installation to compile and deploy VMs, install PAS, and connect to services.

  • One or more NTP servers if not already provided by your IaaS.

  • (Recommended) A network without DHCP available for deploying the PAS VMs.

    Note: If you have DHCP, see Troubleshooting Guide for guidance on avoiding issues with your installation.

  • (Optional) External storage. When you deploy PAS, you can select internal file storage or external file storage, either network-accessible or IaaS-provided, as an option in the PAS tile. Pivotal recommends using external storage whenever possible. For more information about how file storage location affects platform performance and stability during upgrades, see Configure File Storage.

  • (Optional) External databases. When you deploy <PAS, you can select internal or external databases for the BOSH Director and for PAS. Pivotal recommends using external databases in production deployments. An external database must be configured to use the UTC timezone.

  • (Optional) External user stores. When you deploy PAS, you can select a SAML user store for Ops Manager or a SAML or LDAP user store for PAS, to integrate existing user accounts.

  • The most recent version of the Cloud Foundry Command Line Interface (cf CLI).

 

Front End Planning for All IaaSes

IaaS-Specific Planning