In the last 2 blog posts (here, and here) I showed how to deploy and configure Pivotal Cloud foundry operations manager and the operations manager director for VMware vSphere. This log will show you how to deploy the Pivotal Cloud foundry elastic runtime environment.
Elastic runtime is the framework that hosts your running applications (DEAs), manages the system health, provides consolidated application logging , and the api endpoint and broker(cloud controller) that are all running on virtual machines that Ops Manager provisioned. The Ops Manager deploys the virtual machines with a Linux OS that includes a BOSH agent. Below is a diagram of the network components deployed by the elastic runtime.
Before setting up the elastic runtime you must make a decision about SSL termination. The table below shows your options:
If you are using the HAProxy deployed by CF, as we are in this example, then you must do 2 thing. 1st assign it an IP address from the range of IP’s used when configuring the director (see this post), and second you must create a wild-card A-record in DNS pointing to this IP.
Example: my range is x.x.x.100 –x.x.x.200. When deploying the vSphere director the 1st ip will be assigned to the controller (101). I use x.x.x.110 for my HAProxy. In DNS I create an A record for my domain. A record = *.cto.emc.loca/x.x.x.110. This needs to be setup before deployment.
|
From the Ops manager gui, on the left side click “Import a Product” In the folder where you unzipped the CF files is the cf-1.2.0.0.pivotal file. Select it |
|
Once imported you will see it available in the products list |
|
Click on the Elastic runtime version and the Add button will appear. Click Add. |
|
Elastic runtime is now available to be configured in the installation dashboard. Click Pivotal Elastic Runtime |
|
There are 2 main configuration items. HAProxy and Cloud Controller. Click HAProxy |
|
Enter the IP address for the HAProxy. This needs to be the address that has a wildcard A record setup in DNS |
|
Click the Self-Signed cert |
|
A cert will be generated based off the A record created for the HAProxy |
|
Select “Trust-Self Signed Certificates” and click Save |
|
Verification is done on the setup |
|
Select Cloud Controller |
|
Enter the domain names for the syetme an Apps. In my lab Im deploying everything to the same domain. Click Save |
|
The wild card records are verified. |
|
Give the CF router an IP address from your pool. Click Save IP is verified The basic setup is now completed |
|
Click Apply changes |
|
Deployment is completed. Once deployment is complete we see the Elastic runtime is setup in the installation dashboard |
|
In the vSphere client we see all of the VM’s that have been deployed to run the environment We are now ready to begin adding buildpacks to CF. |
Comments