7.1

n
Seings you dene in the outer blueprint override seings congured in your nested blueprints with
the following exceptions:
n
You can change the name of a nested blueprint, but you cannot change the name of a machine
component, or any other component, inside a nested blueprint.
n
You cannot add or delete custom properties for a machine component in a nested blueprint.
However, you can edit those custom properties. You cannot add, edit or delete property groups for
a machine component in a nested blueprint.
n
Changes you or another architect make to nested blueprint seings appear in your outer blueprints,
unless you have overridden those seings in the outer blueprint.
n
While the lease time specied on a nested blueprint and on the outer blueprint can be set to any value,
the maximum lease time on the outer blueprint should be limited to the lowest maximum lease value of
a nested blueprint. This allows the application architect to design a composite blueprint that has
uniform and variable lease values, but is within the constraints identied by the infrastructure architect.
If the maximum lease value dened on a nested blueprint is less than that dened on the outer
blueprint, the provisioning request fails.
n
When working in an outer blueprint, you can override the Machine Resources seings that are
congured for a machine component in a nested blueprint.
n
When working in an outer blueprint, you can drag a software component onto a machine component
within a nested blueprint.
Networking and Security Rules and Considerations for Nesting Blueprints
n
All networking and security components in outer blueprints can be associated with machines that are
dened in nested blueprints.
n
When app isolation is applied in the outer blueprint, it overrides app isolation seings specied in
nested blueprints.
n
Transport zone seings that are dened in the outer blueprint override transport zone seings that are
specied in nested blueprints.
n
When working in an outer blueprint, you can congure load balancer seings relative to network
component seings and machine component seings that are congured in an inner or nested
blueprint.
n
For a nested blueprint that contains an on-demand NAT network component, the IP ranges specied in
that on-demand NAT network component are not editable in the outer blueprint.
n
The outer blueprint cannot contain an inner blueprint that contains on-demand network seings or on-
demand load balancer seings. Using an inner blueprint that contains an NSX on-demand network
component or NSX load balancer component is not supported.
n
For a nested blueprint that contains NSX network or security components, you cannot change the
network prole or security policy information specied in the nested blueprint. You can, however, reuse
those seings for other vSphere machine components that you add to the outer blueprint.
n
To ensure that NSX network and security components in nested blueprints are uniquely named in a
composite blueprint, vRealize Automation prexes the nested blueprint ID to network and security
component names that are not already unique. For example, if you add a blueprint with the ID name
xbp_1 to an outer blueprint and both blueprints contain an on-demand security group component
named OD_Security_Group_1, the component in the nested blueprint is renamed
xbp_1_OD_Security_Group_1 in the blueprint design canvas. Network and security component names in
the outer blueprint are not prexed.
Chapter 4 Providing On-Demand Services to Users
VMware, Inc. 351