Aria Automation supports integration with Ansible Open Source configuration management as well as with Ansible Automation Platform, fomerly Ansible Tower. After configuring an integration, we can add Ansible components to new or existing deployments from the cloud template editor.
This post demonstrates how to setup Ansible Open Source integration and how to use it in a cloud template.
The upgrade process of VCD allows two different paths:
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.
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.
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_unknownTo 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 --statusThe 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 --forceAfterwards, we restarted all cells:
service vmware-vcd restartThis fixed the issue in this environment.
We can configure and replace license changes to Aria Automation either using the CLI or through the Aria Suite Lifecycle UI. This short post demonstrates the convenient way using Aira Suite Lifecycle (formerly known as vRealize Suite Lifecycle Manager).
All your base are belong to us.