11
XaaS Blueprints
When inves ga ng items under XaaS Blueprints (see image below), we see a large number of XaaS
Blueprints that are not ready to migrate, and a handful that are ready to migrate. A er looking
through the list it seems that the determining factor between an XaaS Blueprint being ready or not
is whether the blueprint uses vRO custom resources. That criteria is not a great way of determining
and repor ng if something is ready to migrate to vRA8. Furthermore, we reviewed the list of XaaS
Blueprints that it says are ready and one by one we realized they would not work with vRA8.
The assessment tool looks for a few very finite requirements that VMware knows are currently not
available in vRA8. But that's just the p of the iceberg. You will need to understand what your vRO
workflow is doing that the XaaS Blueprint is calling. The assessment tool does not inspect your
workflow and understand what its func ons are.
Here's an example: one of the XaaS items that is ready for migra on is used to inspect and report
on vRA7 custom proper es. It looks across all the constructs in vRA 7 to report on where
proper es are defined and what their values are. It even gives you the op on to bulk update those
proper es. Although the assessment tool says this func onality is ready for migra on, it certainly
will not work on vRA8.
Composite Blueprints
When inves ga ng the assessment tool for Composite Blueprints, the tool presented me with
some blueprints that were Not Ready, some that are Ready With Warnings, and some that are Ready.
Here is what I discovered that each of those terms actually means.
M I G R AT I O N G U I D E
