Upgrading vROPs Tenant App for VCD via CLI

In this post I will walk through how to upgrade vROPs Tenant App for Cloud Director via CLI.

Although upgrade can be performed directly from TA vami interface by logging in to https://<vrops-ta-fqdn>:5480/, but having knowledge of CLI is important specially when you are looking for automating the upgrade.

Note: Vami credentials of vROPs TA defaults to root/vmware.

Below are high level steps of upgrading the TA appliance via CLI.

Note: I have tested below steps to upgrade Tenant App from v2.3 to 2.4

Step 1: Enable SSH on TA: Login to TA appliance via vCenter console (credentials: root/vmware) and enable ssh by typing below commands:

# systemctl start sshd

# systemctl enable sshd

Step 2: Download TA Upgrade Package: Upgrade package for appliance can be downloaded from VMware Market Place under Resources tab.

vROPs-TA-MP

Extract the downloaded iso. We need to upload the content of iso on TA in next step

Step 3: Create Upgrade Repo on TA appliance: Connect to TA appliance over ssh and run following command:

# mkdir -p /data/repo

# chmod 755 -R repo/

Now upload the extracted content in /data/repo directory via winscp or similar utility.Read More

Automating vROPs Tenant Appliance Deployment & Configuration via API

In my previous post on vROPs Tenant Appliance for vCD, I covered steps of manual deployment & configuration. In this post I will cover how we can achieve this via CLI/API.

These API’s can be leveraged via any scripting language to automate the deployment of vROPs TA.

Step 1: Deploy vROPs Tenant Appliance via ovftool

As of now there is no API for automating deployment of appliance via API, so we will use ovftool for this purpose.

Read More

Install & Configure vCD Management Pack in vROPs via API

In this post, I will walk through the steps of installing vCD Management Pack in vROPS via API. Installation of the management pack is leveraged via vROPS CaSA API. The adapter configuration is done via regular suite-api. 

What is vROps CaSA API?

CaSA stands for Cluster and Slice Administration. The CaSA API manages the internal working of vRealize Operations Manager and runs on a standalone vFabric tcServer. CaSA API can be explored directly from vROPs by typing https://<vrops-fqdn>/casa/api-guide.html

Install and Configure vCD Management Pack & Adapter

1: Upload vCD Management Pack: First we need to upload vCD MP to vROPs via POST call. 

Note: I am executing all API calls via Postman. If you have never used postman to upload files to the server, then please read this post for instructions.

Read More

Configuring vCenter Adapter in vROPs via API

In this post we will learn how to install Management Packs in vROPs via API. 

For vCenter we don’t have to install any management pack as its shipped with vROPs by default and we just have to create vCenter credentials and configure adapter. Below steps can be followed to configure VC adapter.

1: Obtain Session Token: vROPs session token is obtained via POST call. 

Sample Output:

The token id obtained in output is passed as “Authorization: vRealizeOpsToken token_value” header in all subsequent GET and POST calls.Read More

Getting Started With vROPs Tenant App For vCloud Director 10.x

In this post, I will walk through step by step installation for the vRealize Operations Manager Tenant App for vCloud Director. But before I jump into the lab, I want to take a moment to explain what this solution is all about and what it looks like from an architectural point of view.

What is vROPs Tenant App for vCloud Director?

vROPs Tenant App is a solution that helps in exposing vRops performance metrics to tenants in a vCD environment. Each tenant can only see metrics data relevant to their organization.

From a service provider point of view, this is an awesome solution as Tenant App enables tenants to have complete visibility of performance metrics of their environment. If an environment is not performing as per expectations, tenants can leverage this solution to root cause analysis of performance issues and they can perform L1-L2 level of maintenance/troubleshooting tasks themselves without raising service tickets with service providers. Read More