config-er-vmware.html.md.erb

---
title: Configuring Elastic Runtime for vSphere and vCloud
owner: RelEng
---

<strong><%= modified_date %></strong>

This topic describes how to configure the Pivotal Elastic Runtime components
that you need to run [Pivotal Cloud Foundry&reg;](https://network.pivotal.io/products/pivotal-cf) (PCF) for VMware vSphere, vCloud, or vCloud Air.

<p class="note"><strong>Note</strong>: If you plan to <a href = "http://docs.pivotal.io/addon-ipsec/installing.html">install the IPsec add-on</a>, you must do so before installing any other tiles. Pivotal recommends installing IPsec immediately after Ops Manager, and before installing the Elastic Runtime tile.</p>

## <a id='er-om-add'></a>Step 1: Add Elastic Runtime to Ops Manager ##

1. Navigate to the Pivotal Cloud Foundry&reg; Operations Manager Installation
Dashboard.

1. Click the Pivotal Network link on the left to add Elastic Runtime to Ops
Manager.

    For more information, refer to the [Adding and Deleting Products](./add-delete.html) topic.

1. Click the Elastic Runtime tile in the Installation Dashboard.

    <%= image_tag("images/er-tile.png") %>

## <a id='er-az-networks'></a>Step 2: Assign Availability Zones and Networks ##

1. Select **Assign AZs and Networks**. These are the Availability Zones that you [create](../customizing/vsphere-config.html#create-az) when configuring Ops Manager Director.

1. **(vSphere Only)** Select an Availability Zone under **Place singleton jobs**. Ops Manager runs any job with a single instance in this Availability Zone. 

1. **(vSphere Only)**  Select one or more Availability Zones under **Balance other jobs**. Ops Manager balances instances of jobs with more than one instance across the Availability Zones that you specify.

1. From the **Network** drop-down box, choose the network on which you want to run Elastic Runtime.
<%= image_tag("cloudform/er-az.png") %>

1. Click **Save**.
  <p class="note"><strong>Note</strong>: When you save this form, a verification error displays because the PCF security group blocks ICMP. You can ignore this error.</p>
    <%= image_tag("pcfaws/er-network-error.png") %>

## <a id='er-domain-config'></a>Step 3: Configure Domains ##

1. Select **Domains**.

    <%= image_tag("er17-config-domains.png") %>

1. Enter the system and application domains.
    * The **System Domain** defines your target when you push apps to Elastic
      Runtime.
    * The **Apps Domain** defines where Elastic Runtime should serve your apps.

    <p class="note"><b>Note</b>: Pivotal recommends that you use the same domain name but different subdomain names for your system and app domains. Doing so allows you to use a single wildcard certificate for the domain while preventing apps from creating routes that overlap with system routes. For example, name your system domain <code>system.EXAMPLE.com</code> and your apps domain <code>apps.EXAMPLE.com</code>.</p>

    <p class="note"><strong>Note</strong>: You configured wildcard DNS records
    for these domains in an earlier step.</p>

1. Click **Save**.

## <a id="networking"></a>Step 4: Configure Networking ##

<%= partial 'networking-vmware' %>

## <a id='application-containers-config'></a>Step 5: Configure Application Containers ##

<%= partial 'application_container_config' %>

## <a id='er-appdevctrl-config'></a>Step 6: Configure Application Developer Controls ##

1. Select **Application Developer Controls**.

    <%= image_tag("er17-config-appdevctrl.png") %>

1. Enter your intended maximum file upload size.

1. Enter your default RAM memory allocation per app.

1. Enter your default total RAM memory (RAM) quota per Org. You can change this in the CLI.

1. Enter your maximum and default disk quotas per app.

1. Enter your default service instances quota per Org. You can change this in the CLI.

1. Click **Save**.

## <a id='app-security'></a>Step 7: Review Application Security Group ##

<%= partial 'application_security_group' %>

## <a id='er-auth-config'></a>Step 8: Configure Authentication and Enterprise SSO ##

<%= partial 'authsso_config' %>

## <a id='er-db-config'></a>Step 9: Configure System Databases ##
<p class="note"><b>Note</b>: If you are performing an upgrade, do not modify your existing internal database configuration or you may lose data. You must migrate your existing data first before changing the configuration. See <a href="upgrading-pcf.html">Upgrading Ops Manager</a> for additional upgrade information.</p>
1. Select **Databases**. 
    <%= image_tag("./cloudform/sys-db.png") %>
1. If you want to use internal databases for your deployment, select **Internal Databases - MySQL and Postgres** or **Internal Databases - MySQL**. If you want to use external databases such as Amazon Web Services (AWS) RDS, select **External Databases** and complete the following steps:
    * For **Hostname DNS Name**, enter the hostname of your database.
    * For **TCP Port**, enter the port of your database.
    * For **Username** and **Password**, enter your username and password.
    <p class="note"><strong>Note</strong>: Pivotal recommends that you use internal databases unless you require the functionality of AWS RDS.</p>
1. Click **Save**.  

## <a id='internal-mysql'></a> Step 10 (Optional) Configure Internal MySQL ##

<%= partial 'mysql_proxy_config' %>

## <a id='filestore-config'></a>Step 11: Configure File Storage ##

<%= partial 'filestore_config' %>

## <a id='external-endpoints'></a>Step 12: (Optional) Configure System Logging ##

If you are forwarding logging messages to an external Reliable Event Logging Protocol (RELP) server, complete the following steps:

1. Select **System Logging**.
  <%= image_tag("cloudform/sys-logging.png") %>
1. Enter the IP address of your syslog server in **External Syslog Aggregator Hostname** and its port in **External Syslog Aggregator Port**. The default port for a syslog server is 514.
<p class="note"><strong>Note</strong>: The host must be reachable from the Elastic Runtime network, accept TCP connections, and use the RELP protocol. Ensure your syslog server listens on external interfaces.</p>
1. Select an **External Syslog Network Protocol** to use when forwarding logs.
1. For the **Syslog Drain Buffer Size**, enter the number of messages the Doppler server can hold from Metron agents before the server starts to drop them. See the [Loggregator Guide for Cloud Foundry Operators](../loggregator/log-ops-guide.html) topic for more details.
1. The **Loggregator Port** defaults to 443 if left blank. Enter a new value to override the default.
1. Click **Save**.

## <a id='customize-apps-man'></a>Step 13: (Optional) Customize Apps Manager##

<%= partial 'custombranding' %>

## <a id='smtp'></a>Step 14: (Optional) Configure Email Notifications ##

Elastic Runtime uses SMTP to send invitations and confirmations to Apps Manager
users.
You must complete the **Email Notifications** page if you want to enable end-user
self-registration.

1. Select **Email Notifications**.

    <%= image_tag("cloudform/smtp.png") %>

1. Enter your reply-to and SMTP email information

1. Verify your authentication requirements with your email administrator and use
the **SMTP Authentication Mechanism** drop-down menu to select `None`, `Plain`,
or `CRAMMD5`.
If you have no SMTP authentication requirements, select `None`.

1. Click **Save**.

<p class="note"><strong>Note</strong>: If you do not configure the SMTP settings using this form, the administrator must create orgs and users using the cf CLI tool. See <a href="../adminguide/cli-user-management.html">Creating and Managing Users with the cf CLI</a> for more information.</p>

## <a id='ccdb-key'></a>Step 15: (Optional) Add CCDB Restore Key##

<%= partial 'restore_ccdb_key' %>

## <a id='config-smoke-test'></a>Step 16: Configure Smoke Tests ##

<%= partial '_smoketests' %>

## <a id='er-experimental'></a>Step 17: (Optional) Enable Experimental Features ##

<%= partial 'experimental-features' %>

## <a id='er-errands'></a>Step 18: Configure Errands ##

<%= partial 'errands' %>

## <a id='resources'></a>Step 19: (Optional) Configure Resources ##

<p class="note"><strong>Note</strong>:  Ops Manager 1.7 defines specific instance types instead of custom sizes. Each instance adopts an instance type that is the closest match to its previous custom size for CPU, memory, and disk space. You can modify the automatically selected instance size by selecting a different <code>type</code> under <strong>Resource Config</strong>.</p>

Scale the number of instances in order to reduce resources and configure your deployment. 

<%= image_tag("images/vcloud-vchs/resource_config-v.png") %>

<%= partial 'disable_resources' %>

## <a id='stemcell'></a>Step 20: Configure Stemcell ##

1. Select **Stemcell**.
    This page displays the stemcell version that shipped with Ops Manager.
    <%= image_tag("stemcell.png") %>

	You can also use this page to import a new stemcell version. You only need to import a new Stemcell if your Ops Manager does not already have the Stemcell version required by Elastic Runtime.


## <a id='complete'></a>Step 21: Complete the Elastic Runtime Installation ##

1. Click the **Installation Dashboard** link to return to the Installation
Dashboard.

1. Click **Apply Changes**. If the following ICMP error message appears, click
**Ignore errors and start the install**.

    <%= image_tag("cloudform/install-error.png") %>

    The install process generally requires a minimum of 90 minutes to complete.
    The image shows the Changes Applied window that displays when the
    installation process successfully completes.

    <%= image_tag("cloudform/ops-manager-complete.png") %>

[Return to Installing Pivotal Cloud Foundry&reg; on vSphere and vCloud Air](./vsphere.html)