VRealize Automation 8 lacks approval policies and some XaaS functionality, but it introduced ABX scripts, Cloud Accounts and Cloud Assembly as part of its cloud optimization.
The following Article was written by Rob Bastiaansen. I found the original article here. I wanted to share this, because I believe that Rob was spot on with his review of vRA 8 on-prem. I do believe that this information can benefit the community as a whole. As I continue to build out my homelab, I am sure that I will be discovering some of these changes within the product.
Rob Bastiaansen is an independent trainer and consultant specializing in VMware and Linux. A VMware Certified Instructor based in the Netherlands, he delivers training around the world. He writes articles for several print and online publications and is founder of VMwarebits.com, a site dedicated to technical content related to VMware. Rob has been working with VMware technology since 2000 and has authored several books, including one of the first books dedicated to VMware entitled Rob’s Guide To Using VMware. He has spoken at VMworld, which he has attended since 2004, and other conferences.
At the end of 2019, VMware released the new version 8 of vRealize Automation. Usually, a new version of a product offers more features than previous versions, but that’s not the case with vRealize Automation 8. Instead, VMware released vRealize Automation 8 mainly as an on-premises version of its new product, vRealize Automation Cloud, with a new code base but fewer features.
Earlier in 2019, VMware introduced Cloud Automation Services, a cloud-based offering that provided the same functionality as vRealize Automation (vRA) in the cloud. VMware built that software from the ground up, rather than modifying vRealize Automation Services, although it offers similar services. VMware then renamed this product vRealize Automation Cloud.
And that software now has also been released as the on-premises software stack for vRealize Automation 8. This change to the codebase renders the old vRA appliance obsolete and is a primary reason that some of version 7’s functionality isn’t yet present in version 8.
Feature backtrack with vRealize Automation 8
Although VMware likely intends to add features back in, it has yet to announce anything officially. Still, you can expect many features missing in 8.0 to return in version 8.1 or 8.2. VRA 8 lacks approval policies as well as endpoints for Hyper-V, kernel-based VM and vCloud Director. It also has limited functionality for anything as a service, with no custom resources and no XaaS blueprint components (software components).
VMware also has yet to release an upgrade path from version 7.x to 8.0. VMware will likely premiere upgrade functionality in a future version. Until then, VMware offers documentation about how to prepare for a future upgrade, and you can use the vRealize Automation 8 Migration Assessment Service to ease the process.
Installing vRealize Automation 8
To install the new version of vRA, you can use a single ISO file containing the Easy Installer. This software installs Lifecycle Manager first and, based on your input, deploys VMware Identity Manager and vRA. This means that for all deployments you automatically have an instance of Lifecycle Manager.
A single ISO file contains vRealize Easy Installer, which installs Lifecycle Manager, VMware Identity Manager and vRealize Automation.
If you choose to, you can also use an existing Identity Manager instance or deploy vRA later from Lifecycle Manager. Lifecycle Manager, Identity Manager and vRA each run in their own appliances. However, vRA software now runs entirely in Kubernetes pods.
You don’t have to set up the Kubernetes nodes yourself; Easy Installer creates them automatically. You can also access your entire deployment with the Kubernetes command set. You can deploy additional vRA nodes to form a cluster via Easy Installer, making it easy to create a highly available deployment.
New services and features
VRA 8 offers several new and updated services and features, despite the removal of certain familiar features. These include:
Catalog. From the perspective of an end user who already has access to a current version of vRealize Automation, the catalog appears much the same. It’s part of Service Broker, the catalog management service that enables you to set up access to blueprints and vRealize Orchestrator workflows. It still includes custom forms management from version 7.4.
The vRealize Automation catalog in version 8 closely resembles earlier versions of the same feature.
Cloud Assembly. Cloud Assembly helps you to create the setup for your environment and manage blueprints. Although you must use code to define what you want to achieve in Cloud Assembly, the language it uses — YAML — is simple.
Using Cloud Assembly, you can define a vSphere machine with a configured network adaptor and modify VM properties with code.
Cloud Assembly features a test-button that performs a check of your configurations to verify that you can deploy the blueprint with the given parameters. If you then want to deploy the blueprint, you can do so directly from the design interface — no need to publish it and place it in the catalog first.
You can also now save versions of your blueprint design. These saved blueprints behave like snapshots in the sense that you can return to a previous version or to newer saved copies. You can also compare versions both graphically — such as in the image — or by comparing the YAML and looking for alterations in the code.
Cloud Assembly enables you to compare blueprints with two side-by-side graphic images.
Cloud Accounts. Previous versions of vRA referred to Cloud Accounts as Endpoints. Blueprints can contain components from the various Cloud Accounts with which vRA can connect. Such Cloud Accounts include vCenter, VMware Cloud on AWS, AWS, Microsoft Azure and Google Cloud Platform. VRA can also connect with either NSX-V or NSX-T in combination with vCenter instances.
Blueprints can also integrate with Kubernetes. For that, however, you must use another new vRA 8 service called Code Stream. Code Stream enables you to deploy container workloads in Kubernetes clusters, and you maintain full control over versioning and updating.
Major Cloud Accounts include AWS, Microsoft Azure, Google Cloud Platform, both versions of NSX, VMware Cloud on AWS and vCenter.
Event Broker. VRA 7 introduced Event Broker, which remains in version 8. Although the number of event topics has been reduced, many of the necessary events remain for when you must trigger Orchestrator workflows.
Major event topics deal with blueprint configuration, compute management and deployment actions, among other events.
To further simplify your use of event subscriptions, you can now script your workflow conditions. Such workflow events can be as simple as checking the username for blueprint requests or as complex as triggering large constructions based on blueprint name or project name.
You can use a modified version of the default template with a Python script to rename a machine in the blueprint and process it as a custom property.