7.2

To map a dependency on your design canvas, you draw a line from the dependent component to the
component you are depending on. When you are finished, the component you want to build second has
an arrow pointing to the component you want to build first. For example, in the Controlling the Build Order
by Mapping Dependencies figure, the dependent machine is not provisioned until the primary machine is
built. Alternatively, you can configure both machines to provision simultaneously but draw a dependency
between the software components.
Figure 4‑7. Controlling the Build Order by Mapping Dependencies
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, 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.
Scenario: Assemble and Test a Blueprint to Deliver MySQL on
Rainpole Linked Clone Machines
Using your application architect, software architect, or IaaS architect privileges, create a blueprint to
combine your MySQL component with the vSphere CentOS linked clone blueprint you created.
You are here
Configure
Tenant
Configure IaaS
Resources
Design On-
Demand Services
Prerequisites
n
Create a Software component to install MySQL on Linux machines. See Scenario: Create a MySQL
Software Component for Rainpole.
n
Log in to the vRealize Automation console as a member of the Rainpole architects custom group.
See Scenario: Create a Custom Group for Your Rainpole Architects.
Configuring vRealize Automation
VMware, Inc. 486