Installing the Pivotal ops Manager.

Installing the Pivotal ops Manager.

In order for me to install the Pivotal Cloud Foundry environment i will first have to have the Pivotal OPS manager.

At the time of writing this blog post Pivotal ops manager 2.0.3 is the latest version.

As with all things:”everything starts with a download”, so i direct my web browser of choice to: and proceed to download the: “Pivotal Cloud Foundry Ops Manager for vSphere – 2.0-build.236”.

Once this is downloaded i will install the appliance using the “vSphere Web Client (Flash)”.

Unfortunately the HTML5 client still does not allow me to enter custom specification properties during installation.

Seeing how this is mandatory i have no choice but to use the flash client.

To deploy the ops manager appliance, i right click the ESXI host in the vCenter flash client and i select:”Deploy OVF Template”.

I select the file i just downloaded in the installation interface:

Then i select the name and location (i keep the name default and i select the datacenter i configured in vCenter):

As a resource i select my ESXI server:

I review the details:

(dont worry about the thick provisioning, we get to change that furter on).

For storage i select my fast SSD storage and i choose to use “thin” provisioning:

In networking i select my default (and only) network:

This being a lab setup i try to keep things as simple as possible.

This includes the use of only one network, i also use the ip range from my standard class-C home network.

Custom settings:

I enter my standard lab environment password twice.

The standard hostname sounds pretty good to me: pivotal-ops-manager.

For DNS i provide the ip address of the microsoft active directory server:

The default gateway is what you would expect for a standard class-C home network:

The IP address i have chosen is, i have pre-allocated the entire 192.168.1.[100-199] range for my Cloud Foundry lab.

For ntp i went with the standard European ntp server (this is the same one i configured for my vCenter environment and my AD server).

And finally for those who have been paying attention, my subnetmask is /24 class-C.

I review the final configuration summary:

And click finish with wild abandon!

On the bottom of your vCenter page in “recent tasks” you should be seeing a deployment occurring:

This is one of those great moments to go and get a cup of coffee.

Done, wonderful, lets start her up shall we?

In the vCenter configuration page i right click my new ops manager appliance and i start her up.

Then i open my webbrowser of choice to the IP address we configured earlier:

This will probably generate a warning about insecure SSL certificates, circumvent this and move on.

Now we are greeted with a setup page asking us to pick an authentication provider:

But wait!

Whats that bit at the bottom?

Warning: The internal security module used by Ops Manager will remember the IP or hostname of this visit and always redirect to it. You should plan on maintaining the current IP or hostname after this initial setup in order to avoid authentication problems later on. We recommend using a FQDN for Ops Manager. 

Well thats just really good advice isn’t it? i would be an idiot to ignore that.

To the DNS machine!

I log in to my windows Active Directory server and create a new A record for my opsmanager:

The record will be: with a ptr record.

Lets try out our new URL:


Now, for an identity provider i will choose to use internal authentication, You might be wondering:”but martin, you have this amazing ldap database called active directory, why not simply use that?” to which i would reply:”AD is a wonderful thing surely, but perhaps some of my readers do not wish to install a windows server, so i will try to provide them with a installation guide that has the absolute minimum when it comes to prerequisites”.

I fill out the required authentication information:

Username: martin

Password: Passw@rd!

Decryption phrase: “The answer to life the universe and everything!”

No proxy, and naturally i read the EULA thoroughly and agree to everything pivotal wants.

Then i setup the authentication by clicking the big blue button.

I am greeted with the following:

I love it when stuff is being done for me 🙂

After a short while i am greeted with this beautiful login page:

Very inviting don’t you think?

I log in and am greeted with my very own Pivotal OPS manager interface.

Now you might be tempted to think that you are done, but you would be wrong.

Much like bosh (the underlying platform of the Pivotal OPS manager) we will use the Pivotal OPS manager to “deploy” the actual Pivotal OPS manager “director”. I know i know, its all very meta.

Stay tuned for my next post:

Installing OPS manager through OPS manager, OPSCeption.

3 thoughts on “Installing the Pivotal ops Manager.

Leave a Reply

Your email address will not be published. Required fields are marked *