7.0

Managed vApps for vCloud Air or vCloud Director resources are not supported in the target
vRealize Automation deployment.
Note A known issue exists where the following deprecated approval policy types appear in the list of
available approval policy types after upgrade is finished. These policy types are unusable.
n
Service Catalog - Catalog Item Request - vApp
n
Service Catalog - Catalog Item Request - vApp Component
You can create vCloud Air and vCloud Director endpoints and reservations in the target deployment. You
can also create blueprints that contain vCloud Air or vCloud Director machine components.
Understanding How Multi-Machine Blueprints Are Upgraded
You can upgrade managed service, multi-machine blueprints from a supported vRealize Automation 6.2.x
version deployment.
When you upgrade a multi-machine blueprint, component blueprints are upgraded as separate single-
machine blueprints. The multi-machine blueprint is upgraded as a composite blueprint in which its
previous children blueprints are nested as separate blueprint components.
The upgrade creates a single composite blueprint in the target deployment that contains one machine
component for each component blueprint in the source multi-machine blueprint. If the multi-machine
blueprint contains a setting that is not supported in the target vRealize Automation deployment, the
blueprint is upgraded but its status is changed to draft in the target deployment. For example, if the multi-
machine blueprint contains a private network profile, the private network profile setting is ignored during
upgrade and the blueprint is upgraded in a draft state. You can edit the draft blueprint to specify different
network profile information and publish it.
Note If a published blueprint in the source deployment is upgraded to a draft status blueprint, the
blueprint is no longer part of a service or entitlement. After you update and publish the blueprint in
vRealize Automation 7.0.1, you must recreate its needed approval policies and entitlements.
Some multi-machine blueprint settings are not supported in the target vRealize Automation deployment,
including private network profiles and routed network profiles with associated PLR edge settings. Note
that if you have used a custom property to specify PLR edge settings
(VCNS.LoadBalancerEdgePool.Names ), the custom property is upgraded.
If the multi-machine blueprint uses vSphere endpoints and NSX network and security settings, the
upgraded composite blueprint also contains NSX network and security components in the design canvas.
Note Routed gateway specifications for multi-machine blueprints, as defined in reservations, are
upgraded. However, the target vRealize Automation deployment does not support reservations for routed
profiles that contain associated PLR edge settings. If the source reservation contains a routed gateway
value for a PLR edge, the reservation is upgraded but the routed gateway setting is ignored. As a result,
the upgrade generates an error message in the log file and the reservation is disabled.
Upgrading from vRealize Automation 6.2 to 7.0.1
VMware, Inc. 14