You can you can provision virtual machines by using an HP Server Automation boot image or by provisioning by cloning and using an HP Server Automation template when you integrateHP Server Automation with vRealize Automation.
You can optionally identify the HP Server Automation policies to make available in vRealize Automation. Machine requestors can select from among these policies to install software on the requested machine, or you can specify HP Server Automation policies in the blueprint to be applied to every machine that is provisioned from that blueprint.
Integration Requirements Overview
The following is a high-level overview of the requirements for integrating HP Server Automation with vRealize Automation:
A system administrator installs Microsoft PowerShell on the installation host prior to installing the agent.
The required version of Microsoft PowerShell depends on the operating system of the installation host and might have been installed with that operating system. See Microsoft Help and Support.
A system administrator installs the HP Server Automation snap-in on at least one host for vRealize Automation external provisioning integration (EPI) installation. See Install the HP Server Automation PowerShell Snap-In.
A system administrator sets the PowerShell execution policy to RemoteSigned. See Set the PowerShell Execution Policy to RemoteSigned.
A system administrator installs at least one EPI agent. See Install an EPI Agent for HP Server Automation.
A system administrator sets up the selected integration method. See Integrating HP Server Automation.
A system administrator enables software installation from HP Server Automation. See Enable vRealize Automation Software Installation from HP Server Automation.
A tenant administrator or a business group manager creates a blueprint that enables the deployment of software jobs. See Creating Blueprints for HP Server Automation.
A tenant administrator or a business group manager publishes the blueprint. See Publish a Blueprint.