Tag: VMware Cloud Director Page 1 of 2

VMware Cloud Director Aria Operations integration for tenants

In VMware Cloud Director (VCD), there are several variants of infrastructure that are service providers can sell to their tenants such as, “Pay as you go”, “Allocation based”, “Reservation based”. The combination of these can be offered to same tenants and it becomes challenging to track usage (“metering”) over a period and charge appropriately. It becomes critical for the cloud service providers as the tenants demand transparency in billing, and the cloud service providers must offer it.

VMware Chargeback is a tool provided by VMware that allows service providers to manage and allocate costs associated with virtualized environments. It helps both providers and tenants understand resource consumption and allocate costs accordingly.

Chargeback has undergone some significant transformations during the last years. Originally, it was known as vRealize Operations Tenant App (TA). This functionality was later incorporated in the new Chargeback solution. Chargeback needed two virtual appliances, namely the VMware Chargeback VA and the vRealize Operations VA.

With Aria Operations version 8.16, Chargeback has been completely integrated into Aria Operations (AOPS). Service providers have the capability to to effortlessly integrate VCD with Chargeback using the AOPS Launchpad. VCD tenant users can access Chargeback capabilities through the VCD portal by utilizing the Operation Manager plugin.

In this post, I’ll show how to setup AOPS integration with VCD, and how to enable VCD tenants to access detailed billing and metering information within their VCD tenant portal.

Upgrade VMware Cloud Director to version 10.5

The upgrade process of VCD allows two different paths:

  1. Upgrade by using an update package
  2. Upgrade by using the VMware update repository

In this post, we’ll walk though the update using an update package. In particular, we’ll upgrade VCD from version 10.4.2 to 10.5.1.1 in a multi-cell setup. In this setup we have one primary appliance and two standby appliances.

During the upgrade of the VCD appliance deployment, the Cloud Director service stops working and some downtime can be expected. The downtime depends on the time we need to upgrade each VCD appliance and to run the VCD database upgrade script. The number of working cells in the VMware Cloud Director server group reduces until we stop the VCD service on the last VCD appliance. A properly configured load balancer in front of the Cloud Director HTTP endpoints should stop routing traffic to the cells that are stopped.

Configure VMware Cloud Director Failover Mode

If you have a production-ready VCD installation, you must create it with a database HA cluster that provides failover capabilities to the VCD database (deployments without database HA are not supported by VMware). The VMware Cloud Director appliance includes an embedded PostgreSQL database. The embedded PostgreSQL database includes the Replication Manager (repmgr) tool suite, which provides a high availability (HA) function to a cluster of PostgreSQL servers. To configure HA for the VCD database in a VCD server group, you configure a database HA cluster by deploying one primary and two standby instances of the VCD appliance.

If the primary database service fails, you can activate VCD to perform an automatic failover to a new primary. The automatic failover eliminates the need for an administrator to initiate the failover action if the primary database service fails to perform its functions for any reason. By default, the failover mode is set to manual.

In this post, I’ll demonstrate how to configure VCD failover mode.

Tasks are slow or stall out in Cloud Director multi cell installation

Recently, I was troubleshooting a VCD 10.4 installation with three cells which experienced very slow response times during operations such as Power on/off a VM.

Looking throw the log files soon revealed messages such as:

ERROR | ActiveMQ BrokerService[] Task-15 | TransportConnector | Could not accept connection from tcp://:47990 : javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown

To resolve this issue, we’ve checked if the certificate is expired by running the following command on one of the cells:

/opt/vmware/vcloud-director/bin/cell-management-tool jms-certificates --status

The following part of the command result shows, that all of the 3 cells didn’t had a valid certificate:

To generate new certificates, we’ve run the command:

/opt/vmware/vcloud-director/bin/cell-management-tool jms-certificates --certgen --force

Afterwards, we restarted all cells:

service vmware-vcd restart

This fixed the issue in this environment.

How to resolve unavailability of vSphere Cluster Service VMs

Recently, I wanted to create a new provider VDC with a vSphere cluster as resource pool in a customer VMware Cloud Director environment. It failed with the error message “[ … ] class com.vmware.vcloud.api.presentation.service BadRequestException”.

While checking the cluster in the resource vCenter Server (version 7.x), the following error was shown in the vSphere Client:

“vSphere DRS functionality was impacted due to unhealthy state vSphere Cluster Services caused by the unavailability of vSphere Cluster Service VMs. vSphere Cluster Service VMs are required to maintain the health of vSphere DRS”

Page 1 of 2

All your base are belong to us.