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...
As it seems every week now VMware releases a hotfix for vRA7.6 https://kb.vmware.com/s/article/70911 Installing these usually go rather smoothly, but today we ran into a smaller issue. Installation got stuck at rpm -Uvh --replacepkgs /usr/lib/vcac/patches/repo/cafe/patchRpms/*.rpm We tried to manually update the packages and found there was a transaction lock warning: waiting for transaction lock on /var/lib/rpm/__db.000 This can be fixed by rebuilding the RPM database. rm -f /var/lib/rpm/__db.00* rpm --rebuilddb Now we were more or less ready to revert to snapshots and restart the whole process when I noticed there is actually a retry option, previously when patches failed we had to restart the whole process. Cheers VMware that was useful
To a lot of vRealize Automation 6-7 Managers moving to vRealize Automation 8 is a rather large adaptation of new skillsets. What we have currently been looking at is adapt the new Event Topic model. And there is a lot of Event Topics to follow, but I still feel something is missing. Full list of Event Topics documented @VMware Docs Compute allocation Yes Issued before the allocation of resourcenames and hostselections . Both of these properties can be modified at this stage. Compute post provision Yes Issued after a resource was provisioned successfully. Compute post removal Yes issued after a compute resource was removed. Compute provision Yes Issued before the resource is provisioned at the hypervisor layer. Note: You can change the allocated IP address. Compute removal Yes Issued before the resource is removed. Compute reservation Yes Issued at the time of reservation. Note: You can change the placement order. Deployment action completed Yes Issued after a deploymen...
Kommentarer
Legg inn en kommentar