World's Smallest IaaS, Part 3: the PaaS

a.k.a. The World’s Smallest PaaS

In this blog post, we describe deploying Cloud Foundry/Elastic Runtime to our VMware/vCenter setup (i.e. the world’s smallest IaaS) in order to create the World’s Smallest PaaS (Platform as a Service).

[2014-10-18 this blog post has been updated to reflect ESXi 5.5U2, VCSA 5.5U2, the pivotal.io domain, and Pivotal CF 1.3.1]

[2014-06-29 this blog post has been updated to reflect installation on a 64GiB Mac Pro (not a 16GiB Mac Mini [1] ) with 48GiB allocated to the ESXi VM]

Previous blog posts have covered setting up the necessary environment:

As a final test of Cloud Foundry, we log into the Console, which is Cloud Foundry application that is included by default in the base Cloud Foundry installation.

click on the Pivotal Elastic Runtime tile

click on the Credentials tab

browse to the UAA section; look for the Admin Credentials

The credentials to log into the Console from the web interface are stored in the UAA section of the credentials tab of the Elastic Runtime installation. Note, “admin” is the login even though it’s technically not an email address

2 For those curious about installing with a genuine SSL cert, install this Certificate PEM, this Private Key PEM. Only use this certificate and key if your System and App domains are cf.nono.com and your HA Proxy IP is 10.9.8.40. Note: be sure to check Trust Self-Signed Certificates. Really. Otherwise the install will fail.

3 CPU core over-subscription is not something we worry about. vSphere 5.5’s Virtual CPU limit is 32 Virtual CPUs per core, which means that our 4-core Mac Pro could support as many as 128 Virtual CPUs. Cloud Foundry’s Engineering Team’s servers are often over-subscribed by a factor of more than 20:1 (i.e. as many as 240 cores allocated, but only 12 physical cores available).