7.2

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.2, you must recreate its needed approval policies and entitlements.
Some multi-machine blueprint seings are not supported in the target vRealize Automation deployment,
including private network proles and routed network proles with associated PLR edge seings. Note that
if you have used a custom property to specify PLR edge seings (VCNS.LoadBalancerEdgePool.Names ),
the custom property is upgraded.
If the multi-machine blueprint uses vSphere endpoints and NSX network and security seings, the
upgraded composite blueprint also contains NSX network and security components in the design canvas.
N Routed gateway specications for multi-machine blueprints, as dened in reservations, are
upgraded. However, the target vRealize Automation deployment does not support reservations for routed
proles that contain associated PLR edge seings. If the source reservation contains a routed gateway value
for a PLR edge, the reservation is upgraded but the routed gateway seing is ignored. As a result, the
upgrade generates an error message in the log le and the reservation is disabled.
During upgrade, spaces and special characters are removed from referenced network and security
component names.
Depending on the seing type, the network and security information is captured as several seings in the
new blueprint.
n
Seings for the overall blueprint on its properties page. This information includes app isolation,
transport zone, and routed gateway or NSX edge reservation policy information.
n
Available seings for vSphere machine components in NSX network and security components in the
design canvas.
n
Seings in the network and security tabs of individual vSphere machine components in the design
canvas.
Chapter 1 vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
VMware, Inc. 11