7.1

Understanding How Blueprints Are Upgraded
As a rule, published blueprints are upgraded as published blueprints.
However, there are exceptions to that rule. Multi-machine blueprints are upgraded as composite blueprints
that contain blueprint components. Multi-machine blueprints that contain unsupported seings are
upgraded as unpublished.
For related information see “Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations,”
on page 11 and “Understanding How Multi-Machine Blueprints Are Upgraded,” on page 11.
Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
You cannot upgrade a deployment that contains vApp (vCloud) endpoints. The presence of endpoints of
type vApp (vCloud) prevent upgrade to vRealize Automation 7.0.1.
When upgrade encounters a vApp (vCloud) endpoint in the source deployment, upgrade fails on the master
virtual appliance and reports a message in the user interface and log. You can determine if your source
deployment contains vApp (vCloud) endpoint by logging in to vRealize Automation with Iaas
Administrator privileges, selecting Infrastructure > Endponts and noting the platform type value in the
Endpoints list. If the list contains endpoints of platform type vApp (vCloud), upgrade to 7.0.1is not
supported.
Managed vApps for vCloud Air or vCloud Director resources are not supported in the target
vRealize Automation deployment.
N A known issue exists where the following deprecated approval policy types appear in the list of
available approval policy types after upgrade is nished. 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 seing 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 prole, the private network prole seing is ignored during
upgrade and the blueprint is upgraded in a draft state. You can edit the draft blueprint to specify dierent
network prole information and publish it.
N 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.1, you must recreate its needed approval policies and entitlements.
Upgrading from vRealize Automation 6.2.x to 7.1
VMware, Inc. 11