forked from cloudfoundry/docs-bosh
-
Notifications
You must be signed in to change notification settings - Fork 0
/
setup-vsphere.html.md.erb
39 lines (27 loc) · 1.4 KB
/
setup-vsphere.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
---
title: Setting Up vSphere for BOSH
---
This topic explains how to prepare vSphere for deploying BOSH or MicroBOSH.
##<a id="hardware"></a>Step 1: Allocate Hardware Resources ##
Your intended use of BOSH determines what hardware resources you should allocate
in your IaaS.
For example:
* BOSH needs room to store the releases it deploys.
Larger applications or larger numbers of applications require more disk space.
* Larger numbers of active users require more RAM.
vSphere describes hardware in terms of RAM, CPU, virtual disk, and other specs.
Refer to the [hardware requirements](../deploying/vsphere/hardware_spec.html)
for Cloud Foundry topic for help deciding what hardware to use.
##<a id="traffic"></a>Step 2: Restrict Network Traffic ##
To restrict incoming network traffic to the BOSH VMs on vSphere:
1. Deploy BOSH and your applications deployed with BOSH to separate private
networks.
1. Route requests to BOSH or your applications from a router or load balancer on
a public network.
One way to accomplish this is to configure Network Address Translation (NAT) on a VM.
Assign two network adapters to the VM.
This results in the VM having two IP addresses:
* A public-facing IP address: This IP address connects to the public network
VLAN through an external gateway IP address.
* An internal VLAN IP address: This IP address connects to BOSH and your
application VMs through an internal gateway IP address.