7.4

n
Component settings can change depending on which blueprint the component resides on. For
example, if you include security groups, security tags, or on-demand networks at both the inner and
outer blueprint levels, the settings in the outer blueprint override those in the inner blueprint. Network
and security components are supported only at the outer blueprint level except for existing networks
that work at the inner blueprint level. To avoid issues, add all your security groups, security tags, and
on-demand networks only to the outer blueprint.
Software Component Considerations for Nesting Blueprints
For scalable blueprints, it is a best practice to create single layer blueprints that do not reuse other
blueprints. Normally, update processes during scale operations are triggered by implicit dependencies
such as dependencies you create when you bind a software property to a machine property. However,
implicit dependencies in a nested blueprint do not always trigger update processes. If you need to use
nested blueprints in a scalable blueprint, you can manually draw dependencies between components in
your nested blueprint to create explicit dependencies that always trigger an update.
Using Machine Components and Software Components When
Assembling a Blueprint
You deliver Software components by placing them on top of supported machine components when you
assemble blueprints.
To support Software components, the machine blueprint you select must contain a machine component
based on a template, snapshot, or Amazon machine image that contains the guest agent and the
Software bootstrap agent, and it must use a supported provisioning method.
Because the Software agents do not support Internet Protocol version 6 (IPv6), use IPv4 settings.
Note Software components must have an ordered dependency in the blueprint. Unordered software
components can cause blueprint provisioning to fail. If there is no actual order dependency for the
software components, you can satisfy the blueprint ordering requirement by adding a faux dependency
between the software components.
If you are designing blueprints to be scalable, it is a best practice to create single layer blueprints that do
not reuse other blueprints. Normally, the update processes that are used during scale operations are
triggered by implicit dependencies such as property bindings. However, implicit dependencies in a nested
blueprint do not always trigger update processes.
While IaaS architects, application architects, and software architects can all assemble blueprints, only
IaaS architects can configure machine components. If you are not an IaaS architect, you cannot configure
your own machine components, but you can reuse machine blueprints that your IaaS architect created
and published.
To successfully add software components to the design canvas, you must also have business group
member, business group administrator, or tenant administrator role access to the target catalog.
Configuring vRealize Automation
VMware, Inc. 518