What’s New in vRealize Automation 8.6

Today I will discuss about the new capability and enhancement of vRealize Automation 8.6. The new vRealize Automation 8.6 platform is design to self-service clouds, multi-cloud automation with governance and DevOps based management and enhance security, IT agility, productivity and efficiency so that you plan and prepare your business for the future.


The many benefits of vRealize Automation 8.6 include:

  • VCD Organizations can be added as a Cloud Account in vRA
Customers and partners with existing investment in VCD are now able to leverage vRA for modern template, catalog, pipeline, extensibility, multi-cloud management and governance capabilities while continuing to utilize VCD’s multi-tenanted infrastructure capabilities. VCD Organization owners will add their Org as a cloud account in vRA, map VCD OrgVDCs to vRA Cloud zones and continue to provision and manage IaaS resources into the OrgVDCs.
 
  • Support Puppet Enterprise for machines without a public IP address
You can register machines without a public IP address.
 
  • Ability to configure name of Azure NIC interfaces
You can use the new API to configure a name of NIC for a VM running on Azure.
Note: This is only supported using API and not using VCT
 
  • Resource Quota policy additional day 2 governance

In this release, vRealize Automation Cloud includes Resource Quota Policy enhancements that add additional support for Day2 actions. Quotas now properly account for Day2 actions that affect allocations including disk and machine resizes.

  • Ability to add External validation to a custom day2 action

You can apply a complex validation to the user inputs on the custom day2 request form. The validation is run externally as a   vRealize Orchestrator action and prevents you from submitting the request form until the validation is complete.

  • New VMware Salt Modules Available
We are pleased to announce the release of Salt modules for vSphere/ESXi, NSX, and VMC. These modules were developed as a collaborative effort between VMware and the Salt Open Community and are available under the Salt GitHub project in ‘Salt Extension Modules for VMware’.
 
  • Post DR, you can change the network settings of the vRA appliances, including new IP addresses, and continue to manage all workloads not impacted by the same DR event.
In case of a disaster recovery scenario, vRealize Automation is backed up by SRM and is brought up in a backup vCenter. With vRA this release, you can update the network settings, post DR without your vCenters being on a stretched L2. The same applies for the VMware Identity Manager. Note that any failed vCenter workloads are not managed by the newly-active vRA.

 

I hope you enjoyed reading this post, please like and share if you think it’s worth reading.

Reference: vmware sources

 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.