Blueprints define the resources and attributes associated with the provisioning of a virtual, physical, or cloud machine. Blueprints are configured for any machine (VM, vApp, Physical, Cloud) or a combination (multimachine blueprint) that will be available for provisioning in the portal.
Prepare VMs for provisioning
Before proceed creating a blueprint, we have to prepare VMs for provisioning.
- Navigate to the vCloud Automation Center Appliance management console installation page. In my case: https://vcac.qtest.local:5480/installation.
- Download and save the Windows guest agent files.
- Windows guest agent files (32-bit.)
- Windows guest agent files (64-bit.)
- Unpack GugentZip_version in C:\ on the reference machine.
- This produces the directory C:\VRMGuestAgent. Do not rename this directory.
- Configure the guest agent by running the following command in an elevated command prompt:
1winservice -i -h iaas_Hostname_fqdn:portnumber -p ssl
In my case:
1winservice -i -h iaas.qtestlocal:443 -p ssl
- After installation new service should appear in Windows Services called VCACGuestAgentService
- Power server off and convert to template
- Download package from vCAC appliance to Linux server
- Unpack the LinuxGuestAgentPkgs file.
- Navigate to the LinuxGuestAgentPkgs file and locate the subdirectory that corresponds to the guest operating system that you are deploying during provisioning.
- Install the guest agent using the RPM package:
1rpm -i gugent-6.0.0-2025.x86_64.rpm
- Add agent installation path to $PATH
- Change directory to /usr/share/gugent
- Configure the guest agent to communicate with the Manager Service by running
1./installgugent.sh -iaas_Hostname_fqdn:portnumber ssl
Create a Blueprint
- Navigate to Infrastructure –> Blueprints –> Blueprints. Click New Blueprint –> Virtual –> vSphere (vCenter)
- In the Blueprint Information tab:
- Provide a name for the blueprint
- Choose blueprint options. It’s up to you check or not these three boxes.
- Select a reservation policy if you have it
- Accept the default machine prefix or choose your own.
- Specify the number of days to archive machines provisioned from this blueprint
- You can also assign a daily cost for machines provisioned using the blueprint
- In the Build Information
- Select clone from action meu
- If not selected, choose CloneWorkflow in the Provisioning workflow field
- Select template you want to clone from
- Chose a customization specification, if you have one. “A customization specification is required only if you are cloning with static IP addresses. However, you cannot perform any customizations of Windows machines without a customization specification object. For Linux clone machines, you can use a customization specification, an external script, or both to perform customizations”
- You can specify maximum amounts of vCPU, RAM, and HDD space that can be assigned to this blue print. This option gives a user the ability to customize to their specific application.
- In the Properties tab you can attach build profiles and custom properties
- On the actions tab, we can choose what a user can do
- Click OK to finish
Publish a Blueprint
- Navigate to Infrastructure –> Blueprints –> Blueprints
- Point to the blueprint you want to publish and click Publish
- Click OK to confirm
- The blueprint is now a catalog item.