eBooks

VMware vRealize Automation Migration Guide for 2022

Issue link: https://resources.cloudbolt.io/i/1443939

Contents of this Issue

Navigation

Page 12 of 17

12 Not Ready - Blueprints with nested blueprints inside, blueprints with items other than networks on the canvas, and Blueprints with XaaS items on the canvas. Ready With Warnings - Blueprints with reserved vRA7 custom proper es, including proper es such as _deploymentName, Extensibility.LifeCycleProepr es, and other vRA7 specific reserved proper es. Ready - If the blueprint doesn't meet any of the criteria listed in the above two statuses, then the blueprint is deemed "Ready". Be careful though: the assessment tool has no idea what other proper es values are actually used for. It only knows that they are not reserved vRA7 proper es that have been deprecated, so they must be good. There does not appear to be a check to see if these proper es are used to trigger event subscrip ons, which would poten ally make them unsupported if the state they are triggering is no longer available in vRA8. Further, the assessment tool has no idea what they are being used for in your custom or third-party workflows, so it's best to assume that, if they are used in vRO workflows, they are not ready for vRA8. M I G R AT I O N G U I D E

Articles in this issue

view archives of eBooks - VMware vRealize Automation Migration Guide for 2022