Automation

vRealize Automation 8.0 brought with it a completely new method for controlling access to resources within our cloud environments. In previous versions of vRealize Automation, the concept of a Reservation existed, which provided a clear contract as to what compute, storage, and network resources a particular Business Group had access to as well as limits on the amount of memory and storage resources that the Business Group could consume. Fast forward to vRealize Automation 8.

As a followup to my Deploying VMware vRealize Automation 8.0 walkthrough, we’ll now utilize our new vRealize Automation 8.0 deployment to configure a basic Blueprint and provision our first virtual machine using Cloud Assembly. vRealize Automation 8.0 includes a great “Getting Started” wizard that we’re provided when we access our deployment for the first time. While this option gets us up and running the fastest with Cloud Assembly, it obscures the task required to begin using Cloud Assembly.

vRealize Suite Lifecycle Manager 8.0 is the latest release of VMware’s application platform for deploying, upgrading, and managing the various products included in the vRealize Suite. Don’t worry; you didn’t miss several releases between version 2.1 to version 8.0. Instead, VMware has decided to baseline all of the latest vRealize Suite products onto a common version number. Unlike with the previous version of Lifecycle Manager, upgrading to version 8.0 requires the deployment of a new virtual appliance and migration of your existing configuration.

The latest release of vRealize Automation 8.0 is based on a completely rewritten codebase and is a dramatic departure from the previous versions of vRealize Automation. vRealize Automation 8.0 is an on-premise release of the VMware vRealize Automation Cloud SaaS offering that has been available for a while now. The platform consists of 3 components: Cloud Assembly, Cloud Broker, and Code Stream. The new vRealize Automation 8.0 virtual appliance includes these components as well as an integrated version of vRealize Orchestrator 8.

I have been using vRealize Operations to monitor the compliance of virtual machines against the DISA VMware vSphere Virtual Machine STIG for quite some time now. With the release of the new VMware vSphere 6.5 Virtual Machine STIG, I have discovered that vRealize Operations does not collect all the necessary information out of the box to verify compliance with the new STIG rules. Rather than waiting for VMware to provide an update to vRealize Operations, I decided to utilize vRealize Orchestrator to add custom properties to the virtual machines in vRealize Operations using the vRealize Operations REST API.