Using the vRA 8 Migration Assistant

-

 It looks great, but it definitely could do better on the error presentations.

Migration failed:







Diving into the "See details", feeling it could be a bit more helpful





Not to worry

Login to your vRA8 shell, find the migration assistant pod

kubectl -n prelude get pods | grep migration-service

Then tail the logs while performing a migration and hopefully you can get closer to the real details

kubectl logs -f -n prelude migration-service-app-5dcd4f7
Note: replace the pod name with the one you found for your migration-service pod.


Kommentarer

Legg inn en kommentar

Populære innlegg fra denne bloggen

vRA7 to vRA8 migration - Orchestrator

-
Steps to get up and running with vRO 8. Depending on your previous usage of vRO 7 this might the step that requires the most work when you are migrating to vRA8. Attribute Parameter Contains vCAC/vCACCAFE type! cafeHost|vCACCAFE:VCACHost| Switch to vRealize Automation 8 Types Input Parameter Contains vCAC/vCACCAFE type! subtenant|vCACCAFE:Subtenant Switch to vRealize Automation 8 Types Input Parameter Contains Payload Properties! payload|Properties Ensure the selected properties are supported by vRealize Automation 8 The first two will be quite common for everyone who has automated vRA7 using the vRA Plugins for vCAC and vCACCAFE the only working rewrite here is to move to the REST API and redo the work directly. The last one is also heavily used by everyone who relies on the Subscriptions both by pick up information in vRO and sending information back to vRA with " virtualmachineAddorUpdateProperties ". With just about 190 workflows to redo/rewrite or so i gues...
Les mer

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