openstack-er-config.html.md.erb

---
title: Installing Elastic Runtime after Deploying Pivotal Cloud Foundry® on OpenStack
owner: Ops Manager
---

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

<% $this_IaaS = 'OpenStack' %>

This topic describes how to install and configure Elastic Runtime after deploying [Pivotal Cloud Foundry&reg;](https://network.pivotal.io/products/pivotal-cf) (PCF) on OpenStack.

Use this topic when [Installing Pivotal Cloud Foundry&reg; on OpenStack](./openstack.html).

Before beginning this procedure, ensure that you have successfully completed all
steps in the [Provisioning the OpenStack Infrastructure](./openstack-setup.html)
topic and the [Configuring Ops Manager Director after Deploying Pivotal Cloud Foundry&reg; on OpenStack](./openstack-om-config.html) topics.

<p class="note"><b>Note</b>: If you are performing an upgrade from PCF 1.5 to 1.6, please review <a href="upgrading-pcf.html#pcf16upgrade">Upgrading Ops Manager</a> for critical upgrade information.</p>

## <a id='log-in'></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.

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

## <a id='security-config'></a>Step 2: Complete Security Configuration ##

<%= partial 'security_config' %>

## <a id='cloud-controller'></a>Step 3: Complete the Cloud Controller Page ##

1. Select **Cloud Controller** and enter your system and application domains.

    <%= image_tag("openstack/cloud-controller.png") %>
    * 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>

1. Click **Save**.

## <a id='smtp'></a>Step 4: (Optional) Configure SMTP##

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

1. Select **SMTP Config**.

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

1. Enter your reply-to and SMTP email information.

1. For **SMTP Authentication Mechanism**, 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='diego'></a>Step 5: Configure Diego

<%= partial 'diego_config' %>

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

<%= partial 'experimental-features' %>

## <a id='floating-ips'></a>Step 7: Enable Traffic to Private Subnet ##

Unless you are using your own load balancer, you must enable traffic flow to the OpenStack private subnet as follows. Give each HAProxy a way of routing traffic into the private subnet by providing public IPs as floating IPs.

1. Click **Resource Config**.

    <%= image_tag("openstack/resource-config.png") %>

1. Enter one or more IP addresses in **Floating IPs** for each HAProxy.

1. Click **Save**.

Refer to the [Configuring Pivotal Cloud Foundry&reg; SSL Termination](../opsguide/ssl-term.html) topic for more information about configuring traffic depending on your load balancer.

## <a id='disable-resources'></a>Step 8: (Optional) Disable Unused Resources ##

<%= partial 'disable_resources' %>

## <a id='complete'></a>Step 9: Complete 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("openstack/icmp-error.png") %>

1. Elastic Runtime installs. The image shows the **Changes Applied** message that Ops Manager displays when the installation process successfully completes.

    <%= image_tag("openstack/om-installed.png") %>

---

Return to [Installing Pivotal Cloud Foundry&reg; on OpenStack](./openstack.html).