forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathrequirements.html.md.erb
415 lines (385 loc) · 12.9 KB
/
requirements.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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
---
title: Prerequisites to Deploying Operations Manager and Elastic Runtime
owner:
- Ops Manager
- RelEng
---
<strong><%= modified_date %></strong>
This topic explains system requirements for deploying the Pivotal Operations
Manager and Elastic Runtime applications.
## <a id="vsphere"></a>vSphere/vCenter Requirements ##
The following are the minimum resource requirements for maintaining a [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF) deployment with Ops Manager and Elastic Runtime on vSphere:
* vSphere 6.0, 5.5, or 5.1.
* vSphere editions: standard and above.
* Ops Manager Director must have HTTPS access to vCenter and ESX hosts on TCP ports 443, 902, and 903.
* 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 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](http://pubs.vmware.com/fusion-5/index.jsp?topic=%2Fcom.vmware.fusion.help.doc%2FGUID-38178690-1234-4843-B135-4063F9AA73E4.html) for more information.
* Ops Manager requires read/write permissions to the datacenter level of the [vSphere Inventory Hierarchy](http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic=/com.vmware.vsphere.dcadmin.doc_41/vsp_dc_admin_guide/managing_users_groups_roles_and_permissions/c_hierarchical_inheritance_of_permissions.html) to successfully install. Pivotal recommends using the default [VMware Administrator System Role](http://pubs.vmware.com/vsphere-51/index.jsp#com.vmware.wssdk.pg.doc/PG_Authenticate_Authorize.8.6.html#1110514) 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. 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.
<p class='note'><strong>Note</strong>: If you are using the Cisco Nexus 1000v Switch, refer to the <a href="nexus-switch.html">Using the Cisco Nexus 1000v Switch with Ops Manager</a> topic for more information.</p>
<p class='note'><strong>Note</strong>: 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.</p>
## <a id="vcloud-air"></a>vCD/vCloud Air Requirements ##
The following are the minimum resource requirements for maintaining a [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF) deployment with Ops Manager and Elastic Runtime on vCloud Air:
* vCD 5.1, 5.2, or 5.6 (vCloud Air)
* Disk space: 120GB
* Memory: 60GB
* Two public IP addresses: One for Elastic Runtime and one for Ops Manager
* vCPU cores: 28
* Overall CPU: 17 GHz
* Virtual infrastructure administrator privileges to enable Elastic Runtime to automatically power VMs on and off
<p class="note"><strong>Note</strong>: For more information about user privileges, refer to the "User Privileges by Role" section in the <a href="http://www.vmware.com/pdf/vchs_users_guide.pdf">VMware vCloud Air User's Guide</a>.</p>
## <a id="aws"></a>Amazon Web Services ##
The following are the minimum resource requirements for maintaining a [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (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.large instance with 100 GB of allocated storage.
* 2 S3 Buckets
* EC2 Instances:
* 10 t2.micros
* 1 r3.xlarge (1 per DEA)
* 1 c4.xlarge
* 2 m3.large
See [Installing Pivotal Cloud Foundry® on AWS using CloudFormation](./cloudform.html) for more detailed installation requirements.
## <a id="openstack"></a>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](./openstack.html) for detailed requirements.
## <a id="general"></a>General Requirements ##
The following are general requirements for deploying and managing the Pivotal Operations Manager and Elastic Runtime applications:
* The following user privileges:
* Datastore (Allocate space, Browse datastore, Low-level file operations, Remove file, Update virtual machine files)
* Folder (All)
* Network (Assign network)
* Resource (All)
* vApp (All)
* Virtual machine (All)
* (**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:
172.16.64.xip.io).
<br /><br />
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.
<p class="note"><strong>Note</strong>: If you have DHCP, refer to the Troubleshooting Guide to avoid issues with your installation.</p>
* 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`
<p class="note"><strong>Note</strong>: 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.
</p>
* The cf command line interface (cf CLI) tool version 6.1.1 or higher.
* One or more NTP servers.
* <a id='capacity-requirements'></a>Capacity for the following virtual machines:
<table id='req-table' border="1" class="nice" >
<thead>
<tr>
<th><strong>Virtual Machine</strong></th>
<th><strong>Instances</strong></th>
<th><strong>CPU</strong></th>
<th><strong>RAM (MB)</strong></th>
<th><strong>Ephemeral Disk (MB)</strong></th>
<th><strong>Persistent Disk (MB)</strong></th>
<th><strong>Static IP</strong></th>
</tr>
</thead>
<tbody>
<tr>
<td>Message Bus (NATS)</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>0</td>
<td>✓</td>
</tr>
<tr>
<td>consul</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>1024</td>
<td>✓</td>
</tr>
<tr>
<td>etcd</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>1024</td>
<td>✓</td>
</tr>
<tr>
<td>Blob Store (NFS Server)</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>10240</td>
<td>✓</td>
</tr>
<tr>
<td>Cloud Controller Database</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>2048</td>
<td>✓</td>
</tr>
<tr>
<td>OAuth2 Server Database (UAA Database)</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>8192</td>
<td>✓</td>
</tr>
<tr>
<td>Apps Manager Database</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>1024</td>
<td>✓</td>
</tr>
<tr>
<td>Cloud Controller</td>
<td>1</td>
<td>1</td>
<td>4096</td>
<td>20480</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>HAProxy</td>
<td>0</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td>✓</td>
</tr>
<tr>
<td>Router</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td>✓</td>
</tr>
<tr>
<td>Health Manager</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Clock Global</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Cloud Controller Worker</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Collector</td>
<td>0</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>OAuth2 Server (UAA)</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>MySQL Proxy</td>
<td>0</td>
<td>1</td>
<td>1024</td>
<td>4096</td>
<td>0</td>
<td>✓</td>
</tr>
<tr>
<td>MySQL Server </td>
<td>1</td>
<td>1</td>
<td>4096</td>
<td>10000</td>
<td>10000</td>
<td>✓</td>
</tr>
<tr>
<td>MySQL Backup Service</td>
<td>0</td>
<td>1</td>
<td>4096</td>
<td>20000</td>
<td>0</td>
<td></td>
</tr>
<tr>
<td>Application Execution (DEA)</td>
<td>1</td>
<td>1</td>
<td>4096</td>
<td>10240</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Doppler Server</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td>✓</td>
</tr>
<tr>
<td>Loggregator Trafficcontroller</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td>✓</td>
</tr>
<tr>
<td>Push Apps Manager</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Push App Usage Service</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Run Smoke Tests</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Notifications with UI</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>2048</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Deploy CF Autoscaling App</td>
<td>1</td>
<td>1</td>
<td>512</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Register Autoscaling Service Broker</td>
<td>1</td>
<td>1</td>
<td>512</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Destroy Autoscaling Service Broker</td>
<td>1</td>
<td>1</td>
<td>512</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Run CF Acceptance Tests</td>
<td>1</td>
<td>1</td>
<td>512</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Run CF Acceptance Tests without internet</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>1024</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<td>Compilation</td>
<td>1</td>
<td>1</td>
<td>1024</td>
<td>20480</td>
<td>0</td>
<td> </td>
</tr>
<tr>
<th><strong>TOTALS</strong></th>
<th><strong>27</strong></th>
<th><strong>30</strong></th>
<th><strong>37 GB</strong></th>
<th><strong>102 GB</strong></th>
<th><strong>33 GB</strong></th>
<th><strong>13</strong></th>
</tr>
</tbody>
</table>
[Return to the Installing PCF Guide](../installing/index.html)