vRealize Automation 8.1 – General Enhancements (Part 1)

Setting up vRealize Automation 8.1 with VMware Cloud Foundation (VCF) for workload domains

Utilizing the Simple Wizard Setup => Very Easy and Simple right!!!

Custom Resources

Finally having it!!!

We have introduced the ability to create custom resources in Cloud Assembly. Custom Resources allow you to define anything as a resource that can be used as part of a blueprint. As a part of creating the custom resource you define the Create, Update, and Destroy actions for the resource and can also add any additional Day-2 operation actions to be available for the resource once deployed

Custom Day 2 Actions

Just like when you create a custom resource, you can create custom actions that can be performed as Day-2 operations for any resource deployed whether that is a custom resource or one
of the many private and public cloud resources that are available in the Cloud Assembly blueprint design canvas. Once the resource is deployed you will be presented all operation actions you allow including OOTB actions as well as custom actions you have specified. All actions can be controlled by policy to projects, blueprints, or even down to a specific suser.

Resource Limit Settings in Project

Storage / CPU / Memory

Resource limits for storage, memory, and cpu can now be set when adding a cloud zone to a project within the Cloud Assembly service. This will allow you to set these limits per deployment target for a specific group of users to prevent overuse of a specific set of infrastructure or public cloud account.

Approval Policies in vRealize Automation 🙂

You know what I mean with ” 🙂

Approval policies are a level of governance that helps control which Deployment Requests and Actions require approvals before being initiated. If the approver rejects the request, the request is not initiated and fails to execute.
For example, you have a catalog item that is important, but it consumes a significant amount of resources. You want one of your IT administrators to review any deployment requests to ensure that the request is needed.
Another example applies to day 2 actions. Making changes to a deployment that is used by many might be devastating. You want the project administrator who manages the deployment for that team to review all changes to the deployed catalog item.

What is next: vRealize Automation 8.1 – General Enhancements (Part 2)

6 thoughts on “vRealize Automation 8.1 – General Enhancements (Part 1)

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 )

Facebook photo

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

Connecting to %s