forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
openstack.html.md.erb
119 lines (94 loc) · 4.91 KB
/
openstack.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
---
title: Installing Pivotal Cloud Foundry® on OpenStack
owner: Ops Manager
---
<strong><%= modified_date %></strong>
This guide describes how to install [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF) on OpenStack Juno and Kilo distributions.
## Install PCF on OpenStack ##
Complete the following procedures to install PCF on OpenStack:
1. <a href="./openstack-setup.html" class="subnav">Provisioning the OpenStack Infrastructure</a>
1. <a href="./openstack-om-config.html" class="subnav">Configuring Ops Manager Director for OpenStack</a>
1. <a href="./openstack-er-config.html" class="subnav">Installing Elastic Runtime on OpenStack</a>
## Supported Versions ##
Pivotal's automated testing environments have been built using OpenStack releases and distributions based on Havana, Icehouse, Juno, Kilo (Keystone v2, and v3), and Liberty from different vendors including Canonical, EMC, Mirantis, Red Hat, and SUSE. The nature of OpenStack as a collection of interoperable components requires OpenStack expertise to troubleshoot issues that may occur when installing Pivotal Cloud Foundry® on particular releases and distributions.
## Prerequisites ##
In order to deploy Pivotal Cloud Foundry® on OpenStack, you must have a dedicated OpenStack tenant (formerly known as an OpenStack project) that meets the following requirements.
* You must have keystone credentials for the OpenStack tenant, including:
* Auth URL
* API key
* Username
* Project name
* Region
* SSL certificate for your wildcard domain (see below).
* Create any necessary OpenStack network objects.
* The following must be enabled for the tenant:
* The ability to upload custom images to [Glance](http://docs.openstack.org/developer/glance/)
* The ability to create and modify VM flavors. See the [VM flavor configuration table](#vm-flavors).
* DHCP
* The ability to allocate floating IPs.
* The ability for VMs inside a tenant to send messages via the floating IP.
* Permissions for VMs to boot directly from image.
* One wildcard DNS domain. Pivotal recommends using two wildcard domains if system and apps need to be separated.
<p class="note"><strong>Note</strong>: For information on how IaaS user roles are configured, refer to the <a href="iaas-user-roles.html">Pivotal Cloud Foundry® IaaS User Role Guidelines</a> topic.</p>
<p class='note'><strong>Note</strong>: It is possible to avoid using wildcard DNS domains by using a service such as xip.io. However, this option requires granting external internet access from inside VMs.</p>
* Your OpenStack tenant must have the following resources before you install Pivotal Cloud Foundry®:
* 118 GB of RAM
* 22 available instances
* 16 small VMs (1 vCPU, 1024 MB of RAM, 10 GB of root disk)
* 3 large VMs (4 vCPU, 16384 MB of RAM, 10 GB of root disk)
* 3 extra-large VMs (8 vCPU, 16 GB of RAM, 160 GB of ephemeral disk)
* 56 vCPUs
* 1 TB of storage
* Neutron networking with floating IP support
* Requirements for your Cinder back end:
* PCF requires RAW root disk images. The Cinder back end for your OpenStack tenant must support RAW.
* Pivotal recommends that you use a Cinder back end that supports snapshots. This is required for some BOSH functionalities.
* Pivotal recommends enabling your Cinder back end to delete block storage asynchronously. If this is not possible, it must be able to delete multiple 20GB volumes within 300 seconds.
* Miscellaneous:
* If any overlay network is being used with VXLAN or GRE protocols, the MTU of the created VMs must be adjusted to the best practices recommended by the plugin vendor (if any). If Neutron is configured with VXLAN via the Open vSwitch mechanism, the MTU should be 1400. For GRE, the recommended number is 1460. DHCP must be enabled in the internal network for the MTU to be assigned to the VMs automatically.
* Pivotal recommends granting complete access to the OpenStack logs to the operator managing the installation process.
* Your OpenStack environment should be thoroughly tested and considered stable before deploying PCF.
<a id='vm-flavors'></a>Configure your OpenStack VM flavors as follows:
<p class="note">Do not change the names of the VM flavors in the table below.</p>
<table class='nice' border='1'>
<tr>
<th><strong>ID</strong></th>
<th><strong>Name</strong></th>
<th><strong>Memory_MB</strong></th>
<th><strong>Disk</strong></th>
<th><strong>Ephemeral</strong></th>
<th><strong>VCPUs</strong></th>
</tr>
<tr>
<td>1</td>
<td>m1.small</td>
<td>2048</td>
<td>20</td>
<td>0</td>
<td>1</td>
</tr>
<tr>
<td>2</td>
<td>m1.medium</td>
<td>4096</td>
<td>40</td>
<td>0</td>
<td>2</td>
</tr>
<tr>
<td>3</td>
<td>m1.large</td>
<td>8192</td>
<td>80</td>
<td>0</td>
<td>4</td>
</tr>
<tr>
<td>4</td>
<td>m1.xlarge</td>
<td>16384</td>
<td>160</td>
<td>0</td>
<td>8</td>
</tr>
</table>