Deploying Pivotal Cloud Foundry in Your Own Home Lab
Assuming you have done steps 1-5 correctly:
Pointing your web browser at the address you chose in step 2.i above (for me that is 10.0.0.150) should produce the following screen:
Click import a product. I then imported cf-126.96.36.199.pivotal (which is the elastic runtime) and do the same again for p-mysql-188.8.131.52.pivotal.
It takes some time to import….
After importing I clicked the add button on the left for both Pivotal Elastic Runtime and Pivotal MySQL (v1.2).
Next step is to configure Ops Manager Director. Click on the large vmware vsphere icon. It asks for the IP address of your vcenter server or appliance and user/password. Click save.
Select the big button to configure Operations Manager Director for vSphere and go through each of the steps on the left of the screen. I skipped health monitor and resource sizes, leaving them at the default. Everything else I changed or added details. Don’t forget to press save.
- vCenter credentials: your IP address and a suitable user (maybe root) and password for your vCenter server. It needs a high level of privileges to do things like create VMs.
- vSphere configuration: Data centre name and cluster containing the servers that you will store Pivotal CF on. Datastore name: This is the single 438GB iscsi storage volume that is share between both hosts. Resource pool: I used one that I had created earlier.
- Network configuration: choose the name of the network you use for ESX. Subnet: this is one that tripped me up a few times. Use something like 10.0.0/24 and then exclude the ranges that are used by your network for DHCP (see screen shot). Based on this example, Pivotal CF will create VMs using the IP addresses between 10.0.0.180 and above. DNS: This is the Windows simple DNS server that I created. The gateway is just my home network router IP address.
- NTP server: I used time.nist.gov. Note: If you have issues during the install, check all your ESX servers are time synchronized.
- System settings: I received a suggestion to enable this. Pivotal CF will restart failed VMs.
Next configure Pivotal Elastic Runtime.
- For HAProxy, this is a step that tripped me up. I chose 10.0.0.183 (deliberately 3 addresses after the starting point of my range that I created above which began with 10.0.0.180). The CF install will create an IP address against this later. Here’s the tricky bit – you need to have created a DNS server or somehow serve up a DNS address that you create. More on that in a moment. The domain I created is *.cf.mattzwol.com.
- Choose the check box to “Trust Self-Signed Certificates”. Then click “Generate Self-Signed RSA Certificate”. In this box you need to add the wildcard domain that you are creating – e.g “*.cf.mattzwol.com”. If you do this successfully and click save you should have: Successfully verified ability to allocate IP
- Cloud Controller: Here you enter your domain such as cf.mattzwol.com into the system and apps domain. If you click save you should see success at the top.
Leave everything else the same. Now hit the big blue “Install” Button.
You will no doubt see a big red warning at the top stating that you need 43 CPUs, but you only have 16. At this point you can either go out and buy another 4 servers, or do what I did and click “Ignore and continue”.