vRealize Automation | 28 MAY 2022

Check for additions and updates to these release notes.

Release Versions

vRealize Automation Cloud | May 2022
VRealize Automation 8.8.1 | June 9 2022
  • vRA Easy Installer (ISO) build 19919827
  • vRA Product (appliance) build 19906703
  • SaltStack Config build 19886499

Updates made to this document

Date Description of update Type
5/28/2022 Initial publishing for vRealize Automation Cloud
6/09/2022 Initial publishing for vRealize Automation 8.8.1
6/21/2022  Machines connected to an NSX-T global network are not being tagged on NSX-T Known Issue

NEW DOCUMENT FORMAT

Starting with this release, the Release Notes for both vRA 8.8.1 and later, and vRA Cloud are now combined into one document. Some things to expect:

  • Currently, vRA Cloud and vRA 8.x.x release on separate dates. It is important to note the release dates as listed above and verify that the content is applicable. For example, if the dates above say vRA Cloud May 2022 and vRA 8.8.1 TBD, that means the content at that point in time is only applicable to vRA Cloud. Once vRA 8.8.1 is released the date would be updated to reflect the release date.
  • Resolved and Known issues are now listed in the What's New section, organized by Month/8.x.x version.

About vRealize Automation

You can find information about these new features and more at VMware vRealize Automation Cloud and in the signpost and tooltip help in the user interface. Even more information is available when you open the in-product support panel where you can read and search for related topics, and view community posts and KBs, that appear for the active user interface page.

Before you begin

Familiarize yourself with the supporting documents.

VRealize Automation Cloud VRealize Automation 8.8
After setting up your users, you can use the Getting Started and Using and Managing guides for each of the included services. The Getting Started guides include an end-to-end proof of concept. The Using and Managing guides provide more in-depth information that supports your exploration of the available features. Additional information is also available in vRealize Automation product documentation.

After installing vRealize Automation and setting up your users, you can use the Getting Started and Using and Managing guides for each of the included services. The Getting Started guides include an end-to-end proof of concept. The Using and Managing guides provide more in-depth information that supports your exploration of the available features. Additional information is also available in vRealize Automation 8.8 product documentation.

For information on vRealize Orchestrator 8.8 features and limitations, refer to the vRealize Orchestrator 8.8.1 Release Notes.

SaltStack Config Upgrade Requirements

Before you can upgrade your SaltStack Config appliance you must upgrade the Master plugin. For information on upgrading the Master plugin, see Upgrade the Master Plugin.

May 2022/vRA 8.8.1 What's New

New Features

  • Ability to enable/disable Log Analytics for Azure VMs - Day2

    You can now enable/disable Azure VM log Analytics. This allows you to capture VM log data for further analysis by Azure Monitor and Query solutions. 

  • Manage resource RBAC permissions with quick create VM

    The deployment manage permission under Role Based Access Control now includes a new feature that allows you to create a VM directly using a single button and wizard independent of a VMware Cloud Template. With this feature you can:

    • Quick create VM
    • Quick create VM with existing network
    • Quick create VM with new/existing storage
  • Support for remote vCenter Server Cloud accounts

    Similarly to 7.x releases of vRealize Automation, vRA 8.8.1 and later now supports the management of remote vCenter Server Cloud accounts. Instead of deploying a whole vRealize Automation instance in a remote site, you can now deploy a small vRealize Automation Extensibility (vREx) Proxy. This proxy VA helps a single central vRealize Automation instance to connect to the remote site and manage its resources. You will need to configure proper firewall rules and networking for a single communication channel only. This way, it is possible to manage resources of multiple sites while still having a simpler setup and and configuration.

    There is no impact for existing deployments, this is a new feature that is toggled off by default. For additional information on enabling and using the feature, please consult with the vRealize Automation documentation.Learn more.

  • Storage limits are applied for Independent Disks and First Class Disks (FCD)

    Previously, vRealize Automation only supported storage limits for day 0 attached disks and disks added via day2 operation. Independent disk & FCDs were not counted towards the storage limit set by the user.  Now, if the disk size exceeds the storage limit set then the deployment will fail. This is also supported in IaaS API.

     

  • Cloud Guardrails Initial Functionality Release (vRA Cloud Only)

    vRealize Automation has made it a priority to expand our capabilities deeper in the public cloud space. One of the areas we've identified to add value is in the provisioning, policy application, and continuous management of public cloud environments with an everything-as-code approach. This release represents our first step toward that vision with vRealize Automation Cloud Guardrails, a feature suite focused on the challenges faced with managing cost, performance, security, networking, and configuration at scale for multi-cloud environments.

    Our goal is for Cloud Guardrails to tackle the multi-cloud management space ,with tasks like creating on-demand AWS Member Account with appropriate security and IAM configurations, while Cloud Assembly continues to handle the provisioning of services into multi-cloud environments. You'll see a continuous flow of updates to build-out Cloud Guardrails in service of that goal. 

    • Guardrails tab visible in Cloud Assembly
      • The Guardrails tab is now visible in Cloud Assembly for users. The Cloud Guardrails User CSP role is required to operate this new feature suite.
    • Enforce Desired State using Cloud Guardrails
      • Cloud Guardrails at this stage is fundamentally a Salt Idem SLS launcher. Cloud Guardrails take a group of Idem SLS templates, bundled together as composite templates, and define them as a Desired State. A Desired State is a group of templates, or composite templates, with the input parameters provided.
      • Once defined, the Desired State is Enforced which triggers the engine to perform actions such as creating a cloud environment and instantiating cloud-native policies as defined in the Desired State. The system is Idempotent, meaning the end-result is always what is defined templates regardless of whether the actual steps include creating a new environment, updating an existing environment, or just updating a specific policy.
    • In-product library to host VMware-provided templates
      • To assist customers in their journey with Cloud Guardrails, VMware is providing a set of out-of-the-box templates to accomplish common use-cases needed in the public cloud.
      • The initial release of cloud guardrails includes some templates in the library like creating AWS Organizational Units (OU) and Member Accounts and creating IAM roles directly into the public cloud.
      • VMware will continue to build out this library as the feature suite matures and additional functionality is released.

    We look forward to your feedback around this announcement, and you'll hear more about vRealize Automation Cloud Guardrails and its vision soon.

Resolved Issues

Known Issues

  • Machines connected to an NSX-T global network are not being tagged on NSX-T

    Machine tags are defined in the cloud template and apply to the machine if deployed on vCenter, but also on the NSX-T if the machine is connected to an NSX-T network.   Thi NSX-T Federation support was introduced in vRA 8.4. However, deployed machines with tags that are connected to an NSX-T global network are not being tagged on the NSX-T. NSX-T global networks are networks that are defined by the NSX-T global manager and apply to one or more NSX-T local managers.

    Note: Machine tagging is different than machine NIC (network interface) tagging, which is working as expected.

    Workaround: Manually add the tag on the machine on the NSX-T. 

API Documentation and Versioning

API documentation is available with the product. To access all Swagger documents from a single landing page, go to:

  • https://www.mgmt.cloud.vmware.com/automation-ui/api-docs/ for vRealize Automation Cloud.
  • https://<appliance.domain.com>/automation-ui/api-docs for vRealize Automation 8.x, where appliance.domain.com is your vRealize Automation appliance.

Before using the API, consider the latest API updates and changes for this release, and note any changes to the API services that you use. If you have not locked your API using the apiVersion variable before, you might encounter a change in an API response. All API updates and changes for this release are provided in the table below.

For unlocked APIs, the default behavior varies depending upon the API.

  • For Cloud Assembly IaaS APIs, all requests which are executed without the apiVersion parameter will be redirected to the first version which is 2019-01-15. This redirect will allow every user who did not previously specify the apiVersion parameter to transition smoothly to the latest version without experiencing breaking changes.

    NOTE: For the Cloud Assembly IaaS APIs, the latest version is apiVersion=2021-07-15. If left unlocked, IaaS API requests will be redirected to the first version which is 2019-01-15. The first version is deprecated and will be supported for 12 months. To ensure a smooth transition to the new version, lock your IaaS API requests with the apiVersion parameter assigned to 2021-07-15.

  • For other APIs, your API requests will default to the latest version. If you select one of the earlier version dates listed for the Swagger spec, the API behavior will reflect APIs that were in effect as of that date and any date until the next most recent version date. APIs are not versioned for every vRealize Automation release and not all APIs support the apiVersion parameter.

For more information about using the apiVersion parameter when upgrading to newer vRealize Automation 8.x versions, see the vRealize Automation 8.8 API Programming Guide.

Service Name Service Description API Updates and Changes
ABX Holds all functionality specific to ABX, including creation and management of actions and their versions and executing actions and flows. No change
Approval Enforce policies which control who must agree to a deployment or day 2 action before the request is provisioned No change
Blueprint Create, validate, and provision VMware Cloud Templates (formerly called Blueprints) No change
CMX When using Kubernetes with vRealize Automation, deploy and manage Kubernetes clusters and namespaces. No change
Content Gateway (content service) Connect to your infrastructure as code content in external content sources such as SCM Providers. No change
Custom Forms (form-service) Define dynamic form rendering and customization behavior in Service Broker and Cloud Assembly VMware services. No change
Deployment Access deployment objects and platforms or blueprints that have been deployed into the system. No change
IaaS Perform infrastructure setup tasks, including validation and provisioning of resources in iterative manner. No change
Migration This service is used to quickly setup a vRA 8 instance based on information in a configuration file a.k.a Zero-Setup No change
Project Holds all functionality specific to creation, management and delete of projects No change
Relocation Define policy and plans for bringing existing VMs from any cloud under management. No change
Catalog Access Service Broker catalog items and catalog sources, including content sharing and the request of catalog items. No change
Catalog Service (Policies) Interact with policies created in Service Broker. No change
Code stream all pipeline-service These API provide access to Code Stream services. No change
Identity Service A list of identity, account and service management APIs. No change
Relocation Service New restrictions added to PATCH action on onboardingBlueprintState No change

Changed and Deprecated Functionality

None

check-circle-line exclamation-circle-line close-line
Scroll to top icon