Machine blueprints are the complete specification for a machine, determining a machine's attributes, the manner in which it is provisioned, and its policy and management settings. Depending on the complexity of the catalog item you are building, you can combine one or more machine components in the blueprint with other components in the design canvas to create more elaborate catalog items that include networking and security,
Software components, XaaS components, and other blueprint components.
Space-Efficient Storage for Virtual Provisioning Space-efficient storage technology eliminates the inefficiencies of traditional storage methods by using only the storage actually required for a machine's operations. Typically, this is only a fraction of the storage actually allocated to machines. vRealize Automation supports two methods of provisioning with space-efficient technology, thin provisioning and FlexClone provisioning.
Understanding and Using Blueprint Parameterization You can use component profiles to parameterize blueprints. Rather than create a separate small, medium, and large blueprint for a particular deployment type, you can create a single blueprint with a choice of small, medium, or large size virtual machine. Users can select one of these sizes when they deploy the catalog item.
Configure a Machine Blueprint Configure and publish a machine component as a standalone blueprint that other architects can reuse as a component in application blueprints, and catalog administrators can include in catalog services.
Machine Blueprint Settings You can define configuration settings and custom properties for the overall blueprint.
Designing Blueprints with NSX Settings If you configured vRealize Automation integration with NSX for vSphere or NSX-T, you can use network, security, and load balancer components configure your blueprint for machine provisioning.
Configuring a Blueprint to Provision from an OVF You can use an OVF to define vSphere machine properties and hardware settings that are ordinarily defined on blueprint configuration pages in vRealize Automation or programmatically by using vRealize Automation REST APIs or vRealize CloudClient.
Using Container Components in Blueprints You can configure and use container components in the blueprint.
Creating Microsoft Azure Blueprints and Incorporating Resource Actions As a cloud or fabric administrator, you can create Microsoft Azure virtual machine blueprints that business group administrators employ as a building block to create customized provisioned machines for consumers. DevOps administrators can also create Azure machine blueprints, or they can use existing Azure machine blueprints when creating composite blueprints.
Adding Configuration Management Capabilities to vSphere Blueprints You can add configuration management components to vSphere blueprints to support configuration management of vSphere virtual machines.
Add RDP Connection Support to Your Windows Machine Blueprints To allow catalog administrators to entitle users to the Connect using RDP action for Windows blueprints, add RDP custom properties to the blueprint and reference the RDP file that the system administrator prepared.
Add Active Directory Cleanup to Your CentOS Blueprint As an IaaS architect, you want to configure vRealize Automation to clean up your Active Directory environment whenever provisioned machines are removed from your hypervisors. So you edit your blueprint to configure the Active Directory cleanup plugin.
Allow Requesters to Specify Machine Host Name As a blueprint architect, you want to allow your users to choose their own machine names when they request your blueprints. So you edit your blueprint to add the Hostname custom property and configure it to prompt users for a value during their requests.
Enable Users to Select Datacenter Locations for Cross Region Deployments As a blueprint architect, you want to allow your users to choose whether to provision machines on your Boston or London infrastructure, so you edit your blueprint to enable the locations feature.