LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.7

Prerequisites to Deploying Operations Manager and Elastic Runtime

Page last updated:

Note: Pivotal Cloud Foundry (PCF) for vCloud Air and vCloud Director is deprecated and availability is restricted to existing customers. Contact Support for more information.

This topic explains system requirements for deploying the Pivotal Operations Manager and Elastic Runtime applications.

General Requirements

The following are general requirements for deploying and managing the Pivotal Operations Manager and Elastic Runtime applications:

  • User privileges that meet the minimum vCenter requirements according to the BOSH vSphere CPI.

  • (Recommended) Ability to create a wildcard DNS record to point to your router or load balancer. Alternatively, you can use a service such as xip.io. (Example: 203.0.113.0.xip.io).

    Elastic Runtime gives each application its own hostname in your app domain. With a wildcard DNS record, every hostname in your domain resolves to the IP address of your router 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 router, every application deployed to the example.com domain resolves to the IP address of your router.

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

    Note: If you have DHCP, refer to the Troubleshooting Guide to avoid issues with your installation.

  • Sufficient IP Allocation:

    • One IP address for each VM instance.
    • An additional IP address for each instance that requires static IPs.
    • An additional IP address for each errand.
    • An additional IP address for each compilation worker. IPs needed = VM instances + static IPs + errands + compilation workers

Note: BOSH requires that you allocate a sufficient number of additional dynamic IP addresses when configuring a reserved IP range during installation. BOSH uses these IPs during installation to compile and deploy VMs, install Elastic Runtime, and connect to services. We recommend that you allocate at least 36 dynamic IP addresses when deploying Ops Manager and Elastic Runtime.

vSphere/vCenter Requirements

Note: If you are using the Cisco Nexus 1000v Switch, refer to the Using the Cisco Nexus 1000v Switch with Ops Manager topic 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.

The following are the minimum resource requirements for maintaining a Pivotal Cloud Foundry (PCF) deployment with Ops Manager and Elastic Runtime on vSphere:

  • vSphere 6.0, 5.5, or 5.1.
  • Disk space: 2TB recommended.
  • Memory: 120GB
  • Two public IP addresses: One for Elastic Runtime and one for Ops Manager
  • vCPU cores: 80
  • Overall CPU: 28 GHz
  • vSphere editions: standard and above.
  • Ops Manager Director must have HTTPS access to vCenter and ESX hosts on TCP port 443.
  • A configured vSphere cluster:
    • If you enable vSphere DRS (Distributed Resource Scheduler) for the cluster, you must set the Automation level to Partially automated or Fully automated. If you set the Automation level to Manual, the BOSH automated installation will fail with a power_on_vm error when BOSH attempts to create virtual machines (VMs).
    • Turn hardware virtualization off if your vSphere hosts do not support VT-X/EPT. If you are unsure whether the VM hosts support VT-x/EPT, then you can turn this setting off. If you leave this setting on and the VM hosts do not support VT-x/EPT, then each VM requires manual intervention in vCenter to continue powering on without the Intel virtualized VT-x/EPT. Refer to the vCenter help topic at Configuring Virtual Machines > Setting Virtual Processors and Memory > Set Advanced Processor Options for more information.
  • Ops Manager requires read/write permissions to the datacenter level of the vSphere Inventory Hierarchy to successfully install. Pivotal recommends using the default VMware Administrator System Role to achieve the appropriate permission level, or a custom role that has all privileges for all objects in the datacenter, including propagating privileges to children. For a complete list of required vSphere privileges, see the BOSH documentation.

Note: Be advised that Ops Manager might indicate that you do not have the appropriate rights to create/delete folders when this is untrue. If so, click Ignore errors and start the install to continue.

Note: For information on how IaaS user roles are configured, refer to the Pivotal Cloud Foundry IaaS User Role Guidelines topic.

vCD/vCloud Air Requirements

The following are the minimum resource requirements for maintaining a Pivotal Cloud Foundry (PCF) deployment with Ops Manager and Elastic Runtime on vCloud Air:

  • vCD 5.1, 5.2, or 5.6 (vCloud Air)
  • Disk space: 1TB
  • Memory: 120GB
  • Two public IP addresses: One for Elastic Runtime and one for Ops Manager
  • vCPU cores: 80
  • Overall CPU: 28 GHz
  • Virtual infrastructure administrator privileges to enable Elastic Runtime to automatically power VMs on and off

Note: For information on how IaaS user roles are configured, refer to the Pivotal Cloud Foundry IaaS User Role Guidelines topic.

Note: For more information about user privileges, refer to the “User Privileges by Role” section in the VMware vCloud Air User’s Guide.

Amazon Web Services

The following are the minimum resource requirements for maintaining a Pivotal Cloud Foundry (PCF) deployment with Ops Manager and Elastic Runtime on Amazon Web Services infrastructure:

  • 1 Elastic Load Balancer
  • 1 Relational Database Service. We recommend at least a db.m3.xlarge instance with 100 GB of allocated storage.
  • 5 S3 Buckets
  • EC2 Instances:
    • 13 t2.micro
    • 15 t2.small
    • 2 m3.medium
    • 6 m3.xlarge
    • 3 m3.2xlarge

See Installing Pivotal Cloud Foundry on AWS using CloudFormation for more detailed installation requirements.

OpenStack

Pivotal has tested and certified Pivotal Cloud Foundry on Mirantis OpenStack versions 5.1 (IceHouse) and 6.1 (Juno). Other OpenStack releases and distributions based on Havana, Icehouse, and Juno may also function properly.

See Installing Pivotal Cloud Foundry on OpenStack for detailed requirements.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub