Home

In a previous post I outlined how to migrate your existing vCloud SQL Database over to a PostgreSQL Database. It’s not too difficult but you do need to deploy and configure the PostgreSQL server itself first, so there are a few steps involved. Then I thought what about the people that haven’t moved over to PostgreSQL and have stayed with the traditional SQL server database? Seeing as vCloud Director 9.7 will be the last version to support SQL what are their options and can they just skip this step all together and move directly to the appliance?

Luckily the answer is yes!

Currently in my lab I have vCloud Director 9.5 installed on a CentOS 7 VM with an external SQL Database running on a SQL 2016. In this post I will go through the four main steps you need to complete to migrate over to the new vCloud Director 9.7 Appliance.

1 – Upgrade the existing instance of vCloud Director

2 – Deploy the new vCloud Director 9.7 Appliance

3 – Migrate the external SQL Database to the embedded PostgreSQL Database

4 – Copy the shared transfer service data and certificate files to the Appliance

As with any upgrade or migration make sure you have a valid backup of the VM (Use Veeam Community Edition, its free!) and you also take a separate backup of the database on the SQL Server. Then take a snapshot before you get started just to be sure.

The first step is to upgrade vCloud Director 9.5 to 9.7 on the CentOS VM.

In order to upgrade vCloud we first need to stop the services. SSH into your vCloud cell and run the following command,

service vmware-vcd stop

Then use winscp to copy the install file over to your existing cell. Then we need to switch to the location that we have the install file saved and run the following command to make the file executable,

chmod u+x vmware-vcloud-director-distribution-9.7.0-12990033.bin

You will then notice that the installation file now displays in green text and is ready to be installed.

Run the following command to start the installation,

./vmware-vcloud-director-distribution-9.7.0-12990033.bin

Type Y and hit Enter to start the upgrade

The upgrade from vCloud 9.5 to 9.7 is now complete

Once the vCloud Upgrade has completed its time to upgrade the database. For this example the DB is hosted on my SQL 2016 server so once again before you do this ensure you have taken a backup of the DB just in case.

Type the following to start the DB upgrade,

/opt/vmware/vcloud-director/bin/upgrade

Enter Y to continue

Before the upgrade starts it will prompt you again to make sure you have backed up your database. Enter Y to continue

Enter Y to start the services

Both the vmware-vcd-watchdog and the vmware-vcd-cell services should now start

Wait a few minutes for the services to start up before attempting to login

If you check the About section you will see that vCloud Director has been upgraded to 9.7

The second step is to deploy the new vCloud Director 9.7 Appliance

The vCloud Appliance contains the VMware Photon OS, vCloud Director Services and PostgreSQL 10

Before we get started make sure you have created the required DNS entries for eth0 and eth1, both forward and reverse lookup. We will also require an NFS share to mount as the transfer store. You can do this by deploying an openfiler server and presenting the NFS share or presenting the share from a filer in your environment. If you are also just testing this out in the lab then the easiest way is to present it from a windows server.

You can do that by opening up Server Manager and selecting Add roles and features. Click next through the wizard until you reach the Server Roles section, then expand File and Storage Services, expand File and iSCSI Services and tick the box for Server for NFS. Then click Add Features on the window that appears, then click Next, then Next again and Install

Once that is complete create a folder on the windows server that you want to use as the transfer store. Then right click the folder and select properties and click on the NFS Sharing tab. Then click Manage NFS Sharing

Then tick Share this folder and enter the share name, I have just entered vcloud for this example. Then click Permissions

Then change the Type of Access to Read-Write and tick Allow root access and click OK

Then click OK again to close the NFS Advanced Sharing box and click Close on the folder properties. The NFS share is now created and ready to be used during the ova deployment.

I have created another DNS entry to reference this server so the new mount path will look like this,

labnfs.stevenonofaro.local:/vcloud

Now it’s time to deploy the ova file. Login to your vCenter server and choose the appliance ova file and click Next

Enter the VM Name and click Next

Select the compute resource and click Next

Review Details and click Next

Accept the License Agreement and click Next

Select your configuration size, there are 5 options available. For this example I will be using Primary – small. Once you have made your selection click Next

Select your disk format and storage, then click Next

Select which networks you will be using for each adapter.

In production these should be placed on separate networks. The Eth0 Network is used for the HTTP traffic and the console proxy service on custom port 8443. Eth1 Network is used for vPostgreSQL, so having them on separate networks splits the traffic and helps to avoid duplicate entries in the route table.

For this example in my lab I have used two separate port groups to illustrate this.

Next up is the Customize template section and you will have to scroll down and complete each of the options. I have put together an expanded view with all of the options I used during the deployment.

The entries below a pretty standard for an ova deployment but I just want to outline a few which can cause you a few issues if set incorrectly.

Expire Root Password Upon First Login – Untick this box then you can use the password you set instead of having to reset it when you first login.

Enable SSH Root Login – Enable this option to assist with testing once the appliance is deployed.

NFS Mount for Transfer File Location – The format for this needs to be set as the IP/DNS name of the server hosting the service and then the mount path. Earlier we presented an NFS share from a windows server so I have used labnfs.stevenonofaro.local:/vcloud

The “vcloud” part at the end is just the NFS share name. Another good option for this it so deploy Openfiler and then present the NFS share. I have tested with both and can confirm either one works fine.

Installation ID – If you are deploying the appliance at a new site and are looking to configure multisite later on update this entry from 1 to 2 for example.

 

Static Routes for Eth0 and Eth1 – Since this is in my lab and I have both on the same subnet, including the NFS share this can be left blank. In production this would need to be configured when trying to communicate with external services.

 

Domain Name – The entry says the domain name of this VM. For this just enter the domain name itself, so my labs domain is stevenonofaro.local. Make sure this one is correct otherwise services can fail to start and you will have issues connecting to the PostgreSQL DB.

 

Domain Search Path – Then again for this entry use the domain name in your lab/production environment. So I have used stevenonofaro.local here also.

 

Once complete click Next to continue

 

 

Review the settings and click Finish

Next SSH into the newly deployed appliance with the password used during the deployment. If you did leave the expire password on first login box selected you would be prompted here to change it. If not you would just login as normal.

Now it’s time to check the services are running correctly. The two main services you want to check are the vCloud Services and the PostgreSQL Services.

Enter the following to check the vCloud Director Services – service vmware-vcd status

Then if that comes back as active (running) just like the image below then check the PostgreSQL Service.

Enter the following to check the PostgreSQL Services – service vpostgres status

You can then log into the management interface of the appliance on port 5480,

https://labvcd97.stevenonofaro.local:5480

You should see the server Name LABVCD97 with the Role set to primary and a Status of running. If this is not the case then you can check the following log files to help you troubleshoot the issue.

/opt/vmware/var/log/firsboot

/opt/vmware/var/log/vcd/setupvcd.log

/opt/vmware/var/log/vami/vami-ovf.log

You can also run the command ovfenv to double check all of the entries used when you were configuring the appliance.

If all looks well you should be able to access the vCloud Director logon prompt using your dns name followed by /cloud

https://labvcd97.stevenonofaro.local/cloud

Or the HTML5 interface using https://labvcd97.stevenonofaro.local/provider

The third part is Migrating the existing SQL DB over to the embedded PostgreSQL database on the appliance

We need to stop the vCloud services on each of the cells (existing and new)

First on the new appliance,

service vmware-vcd stop

Then SSH to the original vCloud cell and stop the services also

Now we need to configure the external access to the embedded database running on the vCloud Appliance. This will allow the existing vCloud cell to connect to the appliance database.

SSH to the newly deployed appliance and browse to the following location,

cd /opt/vmware/appliance/etc/pg_hba.d/

Then create a new txt file here by entering vi external.txt

My original vCloud cell IP is 192.168.1.61 so enter the following txt to allow the cell access to the embedded database

#TYPE  DATABASE  USER     ADDRESS               METHOD

host       vcloud            vcloud   192.168.1.61/24     md5

 

When you are ready to save the file hit escape then type :wq and press enter

If you type ls and hit enter you will now see the newly created txt file in the directory

The entries added to this file are dynamically updated to the pg_hba.conf file which controls access to the database. Now if you want to check that your entry was actually added to the pg_hba.conf file then browse to the following location,

cd /var/vmware/vpostgres/10/pgdata

Then if you use the ls command you should see the pg_hba.conf file located within this directory. This file controls access to the PostgreSQL instance.

Type the following,

cat pg_hba.conf to view the file

You will see the new entry has been automatically added to the bottom line of the pg_hba.conf file

Now let’s migrate the database from the original vCloud Cell over to the New Appliance. Currently my original vCloud cell is running on CentOS 7 and the database is still on a SQL 2016 Server. I could migrate the DB to a PostgreSQL server first to make my life easier but I am keen to see if this will work.

SSH to the original cell and run the following command

/opt/vmware/vcloud-director/bin/cell-management-tool dbmigrate -dbhost 192.168.1.85 \ -dbport 5432 -dbuser vcloud -dbname vcloud -dbpassword P@ssw0rd

The command is basically saying migrate the Source DB of this original cell to the PostgreSQL DB via the ETH1 interface (192.168.1.85) using the database information we entered when deploying the new appliance. If all goes well you should see the Database Migration Succeeded with a failed and skipped count of 0.

The fourth step is to copy the shared transfer service data and certificate files to the Appliance

Now SSH to the newly deployed appliance and browse to cd /opt/vmware/vcloud-director/etc

We need to take a backup copy of the following files,

Certificates

Global.properties

Proxycertificates

Responses.properties

Enter the following command to backup each of the files to the /tmp directory,

cp certificates global.properties proxycertificates responses.properties /tmp

Then run the following command to backup the keystore file to the same /tmp location

cp /opt/vmware/vcloud-director/certificates.ks /tmp

Next we need to copy these same files over from the original vCloud instance

The following command can be used to copy the files from the original vCloud Director Cell to the newly deployed appliance. Just update the IP to reference your vCloud Cell and when prompted enter the password.

scp root@192.168.1.61:’/opt/vmware/vcloud-director/etc/certificates /opt/vmware/vcloud-director/etc/global.properties /opt/vmware/vcloud-director/etc/proxycertificates /opt/vmware/vcloud-director/etc/proxycertificates /opt/vmware/vcloud-director/etc/responses.properties’ /opt/vmware/vcloud-director/etc/

Then run the following command to copy the certificates.ks file from the original vCloud Cell,

scp root@192.168.1.61:/opt/vmware/vcloud-director/data/transfer/certificates.ks /opt/vmware/vcloud-director/

Then run the following command to reconfigure the vCloud Director Service. Make sure the keystore password is set to the password on the certificates.ks file from the original cell otherwise the command will fail.

/opt/vmware/vcloud-director/bin/configure –unattended-installation –database-type postgres –database-user vcloud –database-password P@ssw0rd –database-host 192.168.1.85 –database-port 5432 –database-name vcloud –database-ssl true –uuid –keystore /opt/vmware/vcloud-director/certificates.ks –keystore-password P@ssw0rd –primary-ip 192.168.1.84 –console-proxy-ip 192.168.1.84 –console-proxy-port-https 8443

Now it’s time to start the vCloud Director Service on the appliance,

service vmware-vcd start

You can then check the service by running service vmware-vcd status

Then open your web browser and login to the new vCloud Appliance,

https://labvcd97.stevenonofaro.local/cloud

Check through each of the settings under the Manage & Monitor tab and you will see that everything is still available and has been moved across successfully.

The last thing we need to do is remove the old cell. Under the Manage and Monitor tab click on Cloud Cells. Right click on the old Cell and click Delete.

You will now just be left with New vCloud Director 9.7 Appliance

That’s it, you have successfully migrated from vCloud Director 9.5 with an external SQL Database over to the new vCloud Director 9.7 Appliance with embedded PostgreSQL!

As always use the subscribe box above for new post notifications and follow me on twitter @steveonofaro

 

 

 

 

In a previous post I went through the base installation of vRealize Operations Manager 7 and also a deployment of RabbitMQ on a separate CentOS 7 VM. Now it’s time to install the Management Pack and the vRealize Tenant App for vCloud Director.

To begin the first thing we need to do it download the vRealize Operations Management Pack for vCloud Director.

You can find the link to the marketplace here

Select the big green Login to Try button on the right to login and download it.

Login to your vRealize Operations Manager and click on the Administration on the top menu. Then under Solutions click the + button to add a new solution.

Click Browse and select the Management PAK file you just downloaded and then click the Upload button.

Once the file has uploaded you should see the following screen. Click Next

Accept the License Agreement and click Next

The installation will now start. Once complete click Finish

Now if you scroll down on the solutions list you should see Management Pack for vCloud Director

Before we connect to vCloud Director we need to make sure the certificate has been updated and the Public Addresses section has been filled out. To do this log back into the vCloud Director Portal (https://vclouddirectorurl/cloud) and go to Administration then Public Addresses. Update the certificate chain for the API, Tenant Portal and Web Console.

The easiest way is to convert your existing certificate to a pem file, open with wordpad and remove the private key. Then paste the remaining chain into the 3 locations listed above.

Now back over to vRealize,

Click on the Management Pack for vCloud Director and then click on the Configure icon

Next point the Instance Settings to your vCloud Director deployment. If you have a multi-cell environment setup you can enter the load balanced address here.

Click the + to add in your user credentials for vCloud Director and also enter the password for AMQP server we created in the previous post. Then click OK

Once that is complete click Test Connection and accept the certificate prompt

Then click on Save Settings and then OK once the Adapter Instance has saved.

Then click Close to complete.

You may have to refresh your screen before the Management Pack for vCloud Adapter status changes to a green tick and shows Data Receiving.

Now it’s time to download and deploy the vRealize Tenant App for vCloud Director. For this installation I have downloaded the following version from the Marketplace via the following link

From the Resources tab you can scroll down and select the version you would like to use.

vROps-Tenant-App-for-vCD-2.1.0.25981-11344116_OVF10

From vCenter select Deploy OVF Template and browse to the location of the downloaded file. Click Next

Enter a name for the VM and click Next

Select a Cluster to deploy the Tenant App on and click Next

Review the details and click Next

Accept the License Agreement and click Next

Select the Datastore and click Next

Select the Network you would like to use and the default protocol which should be IPv4 and click Next

Complete the Customize Template section updating each of the required fields. This will reference vCloud Director and also the RabbitMQ installation. Once complete click Next

Review the settings and click Finish

Once the VM is ready, power it up and log into the web interface using the Hostname or IP address http://LABTENANTAPP01

Click on vCloud Director and click Finish

Now login using your vRealize Operations Manager credentials

Once logged in you will see the vRealize Tenant App Dashboard

From the Tenant App expand Administration and then select Access Management. Your current vCloud Director Tenants will be listed here.

Click on Enable Plugin Access for the Tenant you would like to enable the plugin for.

Next select the Manage Users tab and the click on Add User

Select the Tenant and click Next

Then select Local User and enter the user details from vCloud Director and click Add User

Then select Administration and click on Support, then click on Configure with VCD Tenant UI

Enter the vCloud Director and RabbitMQ connection details, then click Start

If you have multiple cells enter your load balanced address in the vCloud Director host section.

You will now see the Tenant App listed below and the status should be Running

Before you register the plugin you need to make sure that you have replaced the certificates in use on vCloud Director. Also you need to have updated the public addresses section under then Administration in VCD.

I have mentioned this earlier in the article so if you have issues with the next part please check your Public Addresses in vCloud, specifically the API section.

Now it’s time to register the plugin with vCloud Director

Login to the vSphere Web Client and open up a console session to the Tenant App VM

Login as root and password vmware – defaults

Browse to cd /opt/vmware/plugin

Then run the following python publish.py -H labvcd.stevenonofaro.com -u administrator@system -p ‘password’

Change ‘password’ for your own secure password. You need to keep the brackets in place.

Now let’s login as the Tenant via their URL https://labvcd.stevenonofaro.com/tenant/tenant01 and check if the plugin is available from the vCloud Director Portal

The Operations Manager page for the Tenant will now be displayed. I only have one Linux VM running in the Org at the moment so there isn’t a lot to see yet. If this is your production environment then your dashboard will display more information.

Now let’s run through creating a basic Pricing Policy and assigning it to a Tenant so that they can receive reports from the Tenant App within vCloud Director.

Login into the vCloud Tenant App and expand Metering and select Configuration. Click on Pricing Policies and click Add.

This will be a basic policy setup, if you work for a service provider or cross bill between your internal departments this will look very familiar to you. I will highlight the entries I have modified.

Enter a Policy Name and select the Policy Type. Notice the Currency is already set as we did this earlier. Update the description and click Next

The next section is used to setup the CPU Rate, adjust settings based on how you would like to charge and then click Next.

The next section is used to setup the Memory Rate, adjust settings based on how you would like to charge and then click Next

The next section is used to setup the Storage Rate, adjust settings based on how you would like to charge and then click Next

The next section is used to setup the Network Rate, adjust settings based on how you would like to charge and then click Next

The next section is used to setup the Advanced Network Rate, adjust settings based on how you would like to charge and then click Next

The next section is used to setup the Guest OS Rate, add in a Base Rate for the Guest OS and then click Next

The next section is used to setup the VM Tag Rate, adjust settings based on how you would like to charge and then click Next

The next section is used to setup the VCD Metadata Rate, adjust settings based on how you would like to charge and then click Next

Review the Policy and click Finish

The new policy will now be listed below

Click on the Organization VDCs tab and the click Assign

Then select the policy to assign to the Tenant and click Assign

Then under Metering you can click on Bills and then select Generate New Bill to test

Select the Tenant OVDC and click Next

Select the Policy and click Next

Select the start and end date for the report and enter a Title and click Finish

The Test Bill is now displayed under the My Bills section. I have only had the one VM running for a short period of time so nothing to bill at this stage.

Now let’s see how this would look for the Tenant. Login to VCD as the Tenant (user account we added earlier) and click on Operations Manager from the drop down menu

Under Metering select Bills

Then the user can select the bill and click View to get a breakdown of the costs

The bill details will depend on the policy settings you have selected and the workloads within the Tenant environment. I hope this run through has helped you get started with exploring the features available in the vRealize Tenant App for vCloud Director.

As always use the subscribe box above for new post notifications and follow me on twitter @steveonofaro

RabbitMQ is a messaging broker service which gives applications a common platform to send and receive messages. The messages themselves land in a queue ready for another application to retrieve.

In this post I will be setting up RabbitMQ and connecting it to vCloud Director. This is required if you have a multi-cell environment configured as the cells will use this communicate system notifications and updates etc. Another use case is when you are deploying the vRealize Tenant App for vCloud Director.

In a previous post I walked through setting up the first stage which is the base install of vRealize Operations Manager 7. So this post will cover the RabbitMQ requirements of the vRealize Tenant App 2.1.

If you are using this guide to just connect RabbitMQ to vCloud Director then the process is the same.

First off I have deployed a basic Centos 7 VM and I have given it a Name and IP Address. Then once it was at the login prompt I connected to the IP using putty.

So to get started we need to switch over to the root user

Type su and hit enter to put the root password in

Then make sure the system is up to date, to do this run the following command and let it complete,

yum -y update

Next we need to install Erlang which is one of RabbitMQ’s dependencies,

yum install epel-release and type Y to continue

Then run the following command,

yum install erlang when prompted press Y to continue

Now let’s start downloading the package to install,

wget https://www.rabbitmq.com/releases/rabbitmq-server/v3.6.15/rabbitmq-server-3.6.15-1.el6.noarch.rpm

Then it’s time to import the RabbitMQ key

rpm –import https://www.rabbitmq.com/rabbitmq-signing-key-public.asc

Next we can run the following command to install RabbitMQ

yum install rabbitmq-server-3.6.15-1.el6.noarch.rpm

Then we need to allow SELinux to enable the RabbitMQ Service,

setsebool -P nis_enabled 1

Start and Enable the RabbitMQ Services,

systemctl start rabbitmq-server

systemctl enable. rabbitmq-server

Now it’s time to enable the RabbitMQ management console,

rabbitmq-plugins enable rabbitmq_management

Then modify the ownership of the RabbitMQ Directory,

chown -R rabbitmq:rabbitmq /var/lib/rabbitmq/

Create a new user account called rabbitadmin and change password123 to your secure password,

rabbitmqctl add_user rabbitadmin password123

Enable access for the user and set the corresponding permissions,

rabbitmqctl set_user_tags rabbitadmin administrator

Then enter the following,

rabbitmqctl set_permissions -p / rabbitadmin “.*”  “.*”  “.*”

Allow the following firewall ports,

firewall-cmd –permanent –add-port=4369/tcp

firewall-cmd –permanent –add-port=25672/tcp

firewall-cmd –permanent –add-port=5671-5672/tcp

firewall-cmd –permanent –add-port=61613-61614/tcp

firewall-cmd –permanent –add-port=8883/tcp

firewall-cmd –permanent –add-port=15672/tcp

Once entered it’s time to reload the firewall

firewall-cmd –reload

Then launch the web browser and browse to the IP or DNS name on port 15672

http://LABRABBITMQ01:15672

The username will be rabbitadmin and the password we set earlier

The following screen should now be displayed

Now let’s configure vCloud Director

Login to vCloud Director as a system administrator and then click on the Administration tab

Expand System Settings and then click on Extensibility from the left hand menu

Next we need to tick Enable Notifications

Enter the RabbitMQ host details in the first box

Leave the default settings for AMQP Port, Exchange, vHost, Prefix and SSL options.

Then enter the Username and Password

Once you have entered the information above click on Test AMQP Connection. You should see the following box

Click OK and then click Apply to save the settings.

If you look back in RabbitMQ and check the Exchanges Tab you will notice that the new vCloud Director entries have been created.

Then again in the Queues Tab, new entries will be listed for vCloud Director

RabbitMQ is now installed and connected to vCloud Director. Keep a look out for my next post covering the install and configuration of the vRealize Tenant App for vCloud Director.

As always use the subscribe box above for new post notifications and follow me on twitter @steveonofaro

vCloud Director is one of the products I really enjoy working with and it has come a long way from when it was first released. I remember trying to work through deploying the early releases of v1 and 1.5 which seems like a life time ago now.

In my opinion one thing it has always needed is more visibility for the Tenant. Up until the release of version 1.0 of the vRealize Tenant App for VCD it was difficult for customers to get a detailed view of how their VMs inside of a hosted VCD environment have been performing. When a customer needed to troubleshoot issues at a VM level they would always have to reach out to their provider first.

Now with the combination of vRealize Operations Manager 7, vRealize Management Pack for VCD, vRealize Management Pack for NSX and the vRealize Tenant App for vCloud Director 2.1 this is no longer the case. Tenants can now access all of this information on an easy to read dashboard, along with reporting and billing capabilities from the drop down menu within vCloud Director.

To get started we need to have vRealize Operations Manager deployed with our environment so the following is a walk through for the base deployment of the vRealize Operations Manager 7 virtual appliance. As there are a few components we need to deploy and connect together this one post looks like it might turn into three as we also need to run through deploying RabbitMQ. Stay tuned for those as they will be up soon.

So to get started let’s download the appliance from VMware

Log into vCenter and right click on the host or cluster where you would like to deploy the VM and select Deploy the OVF Template

Enter a Name for the VM and click Next

Select a location to install the OVF and click Next

Review the details and click Next

Accept the License agreement and click Next

For this deployment I will be selecting the Small deployment configuration. Pretty sure my lab won’t get anywhere near 3500 VMs.

Then click Next

From here modify the disk format if required and select the datastore to install the VM on. Then click Next

Select the Destination network and click Next

Fill out the following fields to complete the installation,

Timezone Setting

Default Gateway

Domain Name

Domain Search Path

Domain Name Servers

Network IP Address

Netmask

Review the settings and click Finish

Next we are going to log into the web portal to configure vRealize Operations Manager as a Master node. The Master node is required first and you can also add in a data node, a HA master replica node and a remote controller node. For this installation as we will only have a single master node so both administration and data functions will run from the same VM.

The default installation has the following configuration, 4 vCPU and 16GB of ram. It also has 3 hard disks attached, 20GB, 250Gb and 4GB.

Browse to the newly deployed VM to start the setup https://LABVROPS01

Now you should see the Get Started screen. For this deployment we are going to select New Installation

On the New Cluster screen click Next

Enter the admin password you would like to use and click Next

From here you can select a Certificate to use but for this example I am just going to use the default certificate as its being run up in my lab.

Click Next

Enter the Cluster Master Node Name you would like to use and then add in an NTP Server.

Once complete click Next

Since we have only setup the one node so far just click Next on the Add Nodes screen

Then on the Ready to Complete screen click Finish

You will then be redirected to the vRealize Operations Manager screen. If at this point it logs out just log back in with admin and credentials you entered during the install and click Start vRealize Operations Manager.

Then click Yes on the Confirm First Application Startup screen

Now it’s time to get yourself a coffee and wait for the Master server Cluster Status to change to Online. This can take over 10 minutes in some instances.

When everything is ready you should see the following screen. Both the Cluster Status and the Master Node should be Online.

We have now deployed the Master Node which is required before any other additional nodes can be added in. You can now follow a similar process to add in additional collector nodes and replicas if required for your scenario. After deploying the OVF file again you will just need to select Expand An Existing Installation and follow the prompts.

For this guide I won’t be adding in any additional nodes as the main purpose of this post is to get us to a point where we are ready to deploy and integrate the vRealize Tenant App 2.1 for vCloud Director.

Now it’s time to login to vRealize Operations Manager and finish the setup.

Connect to vRealize by entering the following url – https://labvrops01/ui

You will be presented with the Congratulations on setting up vRealize Operations Manager screen. Click Next to continue.

Accept the License Agreement and click Next

Enter the product key and click Next

Select whether or not you would like to Join the Vmware Customer Experience Improvement Program and click Next

Then click Finish to complete the setup

Once complete you should see the following dashboard.

One thing we should do first is set the Currency. From the Administration tab expand Management and click on Global Settings. Then on the right locate Currency and click Choose Currency.

Then you can search for your currency to narrow down the list. Click on the currency you would like to use and then tick the box below explaining that once you set this you cannot change it. Then click Set Currency.

This is something that is required before you can setup the billing within the app.

Click OK on the Info box that is displayed.

In the left hand menu expand Access and select Authentication Sources. From here you can go through and connect your vRealize Operations Manager deployment to AD. This part is optional.

You can select Active Directory from the Source Type drop down menu. Fill in the connection details for your environment, Test the connection and click OK.

Step 1 is now complete and we have the base installation of vRealize Operations Manager 7 in place. In my next post we will cover the RabbitMQ component and then go through deploying and configuring the Tenant App plugin so that it is available to Tenants within vCloud Director.

You can find a link to that post here

As always use the subscribe box above for new post notifications and follow me on twitter @steveonofaro