NSX 3.2 Will make management easier

-

K8s with Antrea management or the ability to fetch vSphere tags is awaited functionality.

Read more on blogs.vmware.com

Kommentarer

Legg inn en kommentar

Populære innlegg fra denne bloggen

vRealize Automation 8.7 makes custom validations easier with API support

-
Bilde
My world/job has been simplified  a LOT with the release of VMware vRealize Automation 8.7 Release Notes Custom validation for catalog items by custom forms now supported via API VRealize Automation now supports custom validation with API. With this new feature, you can design a catalog item with a customs form and external validation via the API. When the user creates a deployment from the catalog item via API, the validation is executed. In the case that the validation fails, the API response would contain validation error messages. It has never been easier to develop a workflow with proper input validation, publish it to vRA and now finally get proper input validation through the API along with the UI. {      "message" :  "Catalog item request validation failed. Reason: .... Your reasons for this validation to fail ....." ,      "statusCode" :  400 ,      "errorCode" :  30058...
Les mer

vRealize Automation 8.2 Patch1 - Patch attempt #1

-
Bilde
vRealize Automation 8.2 Patch 1 - https://kb.vmware.com/s/article/81396 With 17 Hot-fixes for vRealize Automation 7.6 fresh in mind, looking forward to attempting a vRSLCM only upgrade for the first time, except for some lab environments but they never fail so those don't count. And Patch 1 is a whopping 20 GB Of course my vRSLCM have 19GB of free space, now makes sense why the Patch 1 installer notes start off by telling you to check and gives a free guide on how to increase space. Note : It is recommended to install vRealize Suite Lifecycle Manager 8.2 Patch 1 before vRealize Automation 8.2 Patch 1. This note seems to be a requirement else you will run into a download error: Figured this out after waiting a great deal of time while it was apparently downloading. The next step that also seems to be a requirement that's not directly mentioned in the KB article is to upgrade vIDM to 3.3.3.  https://docs.vmware.com/en/VMware-Workspace-ONE-Access/3.3/rn/VMware-Identity-Manager-33...
Les mer