7.2

Table Of Contents
Pushing Container Templates for Use in Blueprints
You can make a container template available for use in a vRealize Automation blueprint.
A container template can include multiple containers. When you push a multi-container template to
vRealize Automation, the template is created as a multi-component blueprint in vRealize Automation.
The container-specific properties that you add to the container template are recognized in the
vRealize Automation blueprint. See Using Container Properties and Property Groups in a Blueprint.
When you request to provision a blueprint published in the vRealize Automation catalog, you provision
the source container application for that blueprint.
You can add other components to the vRealize Automation blueprint, including the following component
types:
n
Machine types
n
Software components
n
Other blueprints
n
NSX network and security components
n
XaaS components
n
Custom components
You can push a template from Containers to vRealize Automation. Changes that you make to the
vRealize Automation blueprint have no affect on the Containers template.
You can make subsequent changes in the Containers template and push again to overwrite the blueprint
in vRealize Automation. Pushing the template to vRealize Automation overwrites the blueprint, and any
changes made to the blueprint in vRealize Automation between pushes are lost. To avoid losing blueprint
changes, use vRealize CloudClient to clone a new blueprint or to export the blueprint.
Provisioning a Docker Container or Host from a Blueprint
You can create and use vRealize Automation blueprints to provision machines as registered Docker
Container hosts.
For a provisioned machine to be registered as a container host, it must meet the following requirements:
n
The machine is provisioned by a blueprint that contains Containers-specific custom properties.
The required container-specific custom properties are supplied in two property groups. See Using
Container Properties and Property Groups in a Blueprint.
For information about using custom properties and property groups in vRealize Automation, see
Custom Properties Reference.
n
The machine is accessible over the network.
For example, the machine must have a valid IP address and be powered on.
Configuring vRealize Automation
VMware, Inc. 383