IaaS Integration For HP Server Automation VRealize. 7.3 V Realize 7.0 Iaa S Vrealize 70

User Manual: Pdf vRealize Automation - 7.0 - IaaS Integration for HP Server Automation User Guide for VMware vRealize Software, Free Instruction Manual

Open the PDF directly: View PDF PDF.
Page Count: 26

IaaS Integration for HP
Server Automation
vRealize Automation 7.3
IaaS Integration for HP Server Automation
VMware, Inc. 2
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
If you have comments about this documentation, submit your feedback to
docfeedback@vmware.com
Copyright © 2008–2016 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
Contents
IaaS Integration for HP Server Automation 4
Updated Information 5
1HP Server Automation Overview 6
2Install the HP Server Automation PowerShell Snap-In 8
Set the PowerShell Execution Policy to RemoteSigned 8
3Install an EPI Agent for HP Server Automation 10
4Extend the Default Software Installation Timeout 13
5Integrating HP Server Automation 14
Enable Provisioning from HP Server Automation Boot Images 14
Preparing an HP Server Automation Template for Cloning 15
Prepare a Reference Machine for Linux 15
Prepare a Reference Machine for Windows 16
6Enable vRealize Automation Software Installation from HP Server Automation 18
7Creating Blueprints for HP Server Automation 19
Create a Virtual Blueprint for Creating from an HP Server Automation Boot Image 19
Create a Blueprint for Cloning from an HP Server Automation Template 21
8Custom Properties for HP Server Automation Integration 23
9Publish a Blueprint 26
VMware, Inc. 3
IaaS Integration for HP Server Automation
IaaS Integration for HP Server Automation provides information about integrating HP Server Automation
with VMware vRealize ™ Automation.
This documentation provides information on how you can use an HP Server Automation boot image or an
HP Server Automation template to provision virtual machines by cloning.
Intended Audience
This information is intended for system administrators, tenant administrators, fabric administrators, and
business group managers of vRealize Automation. This content is written for experienced Windows or
Linux system administrators who are familiar with virtualization technology and the basic concepts
described in Foundations and Concepts.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For
definitions of terms as they are used in VMware technical documentation, go to
http://www.vmware.com/support/pubs.
VMware, Inc. 4
Updated Information
This IaaS Integration for HP Server Automation is updated with each release of the product or when
necessary.
This table provides the update history of the IaaS Integration for HP Server Automation.
Revision Description
001844-01 Miscellaneous minor changes.
001844-00 Initial release.
VMware, Inc. 5
HP Server Automation Overview 1
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:
nA 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.
nA system administrator installs the HP Server Automation snap-in on at least one host for
vRealize Automation external provisioning integration (EPI) installation. See Chapter 2 Install the HP
Server Automation PowerShell Snap-In.
nA system administrator sets the PowerShell execution policy to RemoteSigned. See Set the
PowerShell Execution Policy to RemoteSigned.
nA system administrator installs at least one EPI agent. See Chapter 3 Install an EPI Agent for HP
Server Automation.
nA system administrator sets up the selected integration method. See Chapter 5 Integrating HP Server
Automation.
nA system administrator enables software installation from HP Server Automation. See Chapter 6
Enable vRealize Automation Software Installation from HP Server Automation.
nA tenant administrator or a business group manager creates a blueprint that enables the deployment
of software jobs. See Chapter 7 Creating Blueprints for HP Server Automation.
VMware, Inc. 6
nA tenant administrator or a business group manager publishes the blueprint. See Chapter 9 Publish a
Blueprint.
IaaS Integration for HP Server Automation
VMware, Inc. 7
Install the
HP Server Automation
PowerShell Snap-In 2
The HP Server Automation snap-in must be installed on at least one host for vRealize Automation
external provisioning integration (EPI) installation prior to installing the EPI agent.
Prerequisites
nObtain the HP Server Automation Snap-in software from the HP Server Automation installation
media.
nLog in to the vRealize Automation console as a system administrator.
Procedure
1Click Start, right-click Command Prompt, and click Run as administrator.
2Change to the directory that contains the PowerShell snap-in.
3Type msiexec /i OPSWpowershell-37.0.0.5-0.msi.
4Complete the installation by accepting all defaults.
5Select Start > All Programs > Windows Power- Shell 1.0 > Windows PowerShell.
6Type Add-PSSnapin 'OpswareSasPs'.
7Type Exit.
Set the PowerShell Execution Policy to RemoteSigned
You must set the PowerShell Execution Policy from Restricted to RemoteSigned or Unrestricted to allow
local PowerShell scripts to run.
nFor more information about PowerShell Execution Policy, type help about_signing or
help Set-ExecutionPolicy at the PowerShell command prompt.
Prerequisites
nLog in as a Windows administrator.
nChapter 2 Install the HP Server Automation PowerShell Snap-In.
Procedure
1Select Start > All Programs > Windows PowerShell version > Windows PowerShell.
VMware, Inc. 8
2Type Set-ExecutionPolicy RemoteSigned to set the policy to RemoteSigned.
3Type Set-ExecutionPolicy Unrestricted to set the policy to Unrestricted.
4Type Get-ExecutionPolicy to verify the current settings for the execution policy.
5Type Exit.
IaaS Integration for HP Server Automation
VMware, Inc. 9
Install an EPI Agent for
HP Server Automation 3
A system administrator must install at least one vRealize Automation EPI agent to manage interaction
with HP Server Automation. The agent can be installed anywhere, including the vRealize Automation
server or the HP Server Automation server, as long as the agent can communicate with both servers.
Prerequisites
nVerify that the HP Server Automation PowerShell Snap-in is installed on the same host as your EPI
agent. If the EPI agent is installed before the snap-in, then the agent service must be restarted after
the snap-in is installed. See Chapter 2 Install the HP Server Automation PowerShell Snap-In.
nThe agent must be installed on Windows Server 2008 SP1, Windows Server 2008 SP2 (32 or 64-bit),
Windows Server 2008 R2 system, or Windows 2012 with .NET 4.5.
nThe credentials of the agent must have administrative access to all HP Server Automation hosts with
which the agent will interact.
nInstall the IaaS components, including the Manager Service and Website.
nSee Installing vRealize Automation 7.0 for complete information about installing vRealize Automation
agents.
nLog in to the vRealize Automation console as a system administrator.
Procedure
1Select Custom Install and Proxy Agent on the Installation Type page.
2Accept the root install location or click Change and select an installation path.
3Click Next.
4Log in with administrator privileges for the Windows services on the installation machine.
The service must run on the same installation machine.
5Click Next.
6Select EPIPowerShell from the Agent type list.
VMware, Inc. 10
7Enter an identifier for this agent in the Agent name text box.
Maintain a record of the agent name, credentials, endpoint name, and platform instance for each
agent. You need this information to configure endpoints and to add hosts in the future.
Important Do not duplicate agent names unless you are installing redundant, identically configured
agents for high availability.
Option Description
Redundant agent install Install redundant agents on different servers, but name and configure them
identically to provide high-availability.
Single agent install Select a unique name for this agent.
8Configure a connection to the Manager Service component.
Option Description
If you are using a load balancer Enter the fully qualified domain name and port number of the load balancer for the
Manager Service component. For example,
manager-load-balancer.eng.mycompany.com:443. IP addresses are not
recognized.
With no load balancer Enter the fully qualified domain name and port number of the machine where you
installed the Manager Service component. For example,
manager_service.mycompany.com:443. IP addresses are not recognized.
The default port is 443.
9Configure a connection to the Manager Website component.
Option Description
If you are using a load balancer Enter the fully qualified domain name and port number of the load balancer for the
Manager Website component. For example,
website-load-balancer.eng.mycompany.com:443. IP addresses are not
recognized.
With no load balancer Enter the fully qualified domain name and port number of the machine where you
installed the Manager Website component. For example,
website_component.mycompany.com:443. IP addresses are not recognized.
The default port is 443.
10 Click Test to verify connectivity to each host.
11 Click Opsware in EPI Type.
12 Type the fully qualified domain name of the managed server in the EPI Server text box.
Optionally, you can leave this blank to let the agent interact with multiple hosts.
The HP Server Automation server with which the agent interacts when provisioning a machine by
using HP Server Automation depends on the value of the required custom property,
EPI.Server.Name, in the blueprint.
IaaS Integration for HP Server Automation
VMware, Inc. 11
Therefore, if you install a dedicated EPI agent by specifying an HP Server Automation server name
during installation, only machines whose EPI.Server.Name property exactly matches the server
name configured for the agent can be provisioned by that server.
If you install a general EPI agent by not specifying an HP Server Automation server name during
installation, a machine can be provisioned by any server specified in the blueprint EPI.Server.Name
property, that is assuming the agent can contact that server.
Note If no matching agent can be found, or there are no agents with unspecified server values,
Opsware provisioning will wait until a suitable agent is found.
13 Click Add.
14 Click Next.
15 Click Install to begin the installation.
After several minutes a success message appears.
16 Click Next.
17 Click Finish.
What to do next
Determine the type of integration method to use. See Chapter 5 Integrating HP Server Automation.
IaaS Integration for HP Server Automation
VMware, Inc. 12
Extend the Default Software
Installation Timeout 4
When you install the software for the integration product, the software might take longer to install than the
default 30-minute timeout. You can increase the default timeout to a value that allows the installation to
finish.
Procedure
1Navigate to the Manager Service installation directory. Typically, this is %System-Drive%\Program
Files x86\VMware\vCAC\Server.
2Create a backup of the ManagerService.exe.config file.
3Open the ManagerService.exe.config file and locate the
workflowTimeoutConfigurationSection element and increase the value of the DefaultTimeout
attribute from 30 minutes to your desired limit.
4Click Save and close the file.
5Select Start > Administrative Tools > Services, and restart the vRealize Automation service.
VMware, Inc. 13
Integrating
HP Server Automation 5
The steps required to integrate HP Server Automation with vRealize Automation depend on which
provisioning method you want to use and whether you want to enable software installation from
HP Server Automation.
When provisioning virtual machines, you can select from the following integration methods:
nProvision by using a system from which HP Server Automation deploys images that is available on
the network.
nProvision by cloning by using a template that is prepared for HP Server 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.
This chapter includes the following topics:
nEnable Provisioning from HP Server Automation Boot Images
nPreparing an HP Server Automation Template for Cloning
Enable Provisioning from HP Server Automation Boot
Images
A system administrator can use an HP Server Automation boot image to enable vRealize Automation to
provision machines by using that instance of HP Server Automation.
Prerequisites
nA system from which HP Server Automation deploys images is available on the network.
nAn EPI agent installed. See Chapter 3 Install an EPI Agent for HP Server Automation.
nLog in to the vRealize Automation console as a system administrator.
Procedure
1On the EPI/Opsware Agent host, select Start > Administrative Tools > Services, and stop the
vRealize Automation EPI/Opsware Agent.
VMware, Inc. 14
2On the EPI agent installation host, which may be the same as the Manager Service host, change to
the EPI agent installation directory, typically %SystemDrive%\Program Files (x86)\VMware\vCAC
Agents\agent_name.
3Edit the agent configuration file, VRMAgent.exe.config, in the EPI agent installation directory.
a Locate the following line.
<DynamicOps.Vrm.Agent.EpiPowerShell
registerScript="CitrixProvisioningRegister.ps1"
unregisterScript="CitrixProvisioningUnregister.ps1"/>
b Change the line to match the following line.
<DynamicOps.Vrm.Agent.EpiPowerShell
registerScript="CreateMachine.ps1"
unregisterScript="DisposeVM.ps1"/>
4Create an HP SA password file in the Scripts folder.
The credentials you provide for this file must have administrator access to all instances of HP SA with
which the agent will interact.
a Select Start > All Programs > Windows Power- Shell 1.0 > Windows PowerShell.
b Change to the Scripts directory.
c Type \CreatePasswordFile.ps1 username.
d Type the password when prompted.
e Type Exit.
5On the vRealize Automation EPI/Opsware Agent host, select Start > Administrative Tools >
Services, and then start or restart the vRealize Automation EPI/Opsware Agent service.
Preparing an HP Server Automation Template for Cloning
You can use an HP Server Automation template to integrate with vRealize Automation.
To create the HP Server Automation template, you must create a reference machine and add
customization specifications to it.
For Windows, see Prepare a Reference Machine for Windows.
For Linux, see Prepare a Reference Machine for Linux.
Prepare a Reference Machine for Linux
You must prepare a reference machine and convert it to a template for cloning to add software installation
by HP Server Automation to provisioning by cloning.
IaaS Integration for HP Server Automation
VMware, Inc. 15
Procedure
1Add the HP Server Automation agent installation package to the cloning template.
2Copy the HP Server Automation agent installer to the reference machine.
3Create a script to run the installer and install the HP Server Automation agent.
4Copy the script to the reference machine.
5Add the customization required to invoke the agent after provisioning, so that the agent is installed on
each cloned machine.
Note Do not install HP Server Automation on the reference machine. The agent must be installed by
using the customization specification or postinstall script following cloning.
What to do next
nOptionally, identify the HP Server Automation policies to make available in vRealize Automation. See
Chapter 6 Enable vRealize Automation Software Installation from HP Server Automation
nCreate a blueprint for the type of HP Server Automation integration you want to enable. See
Chapter 7 Creating Blueprints for HP Server Automation.
Prepare a Reference Machine for Windows
You must prepare a reference machine and convert it to a template for cloning before you can add
software installation by HP Server Automation to provisioning by cloning.
Procedure
1Add the HP Server Automation agent installation package to the cloning template.
2Copy the HP Server Automation agent installer to the C:\ directory of the reference machine.
3Add the customization required to invoke the agent after provisioning, by adding following line to the
Run Once section of the customization specification.
C:\opswareagentinstaller --opsw_gw_addr opswareipaddress:3001 -s --force_sw_reg
--force_full_hw_reg
This customization also installs the agent on each cloned machine.
4Replace opswareagentinstaller with the name of the HP Server Automation agent installer
executable.
IaaS Integration for HP Server Automation
VMware, Inc. 16
5Replace opswareipaddress with the IP address of the server that is hosting the
HP Server Automation instance that installs the software.
For example:
C:\ opsware-agent-37.0.0.2.61-win32-6.0.exe --opsw_gw_addr 10.20.100.52:3001 -s --force_sw_reg --
force_full_hw_reg
What to do next
nOptionally, identify the HP Server Automation policies to make available in vRealize Automation. See
Chapter 6 Enable vRealize Automation Software Installation from HP Server Automation.
nCreate a blueprint for the type of HP Server Automation integration you want to enable. See
Chapter 7 Creating Blueprints for HP Server Automation.
IaaS Integration for HP Server Automation
VMware, Inc. 17
Enable vRealize Automation
Software Installation from
HP Server Automation 6
A system administrator 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 HP Server Automation policies can be specified in the blueprint to be applied to
every machine that is provisioned from that blueprint.
Prerequisites
nAn EPI agent installed. See Chapter 3 Install an EPI Agent for HP Server Automation.
nLog in to the vRealize Automation console as a system administrator.
Procedure
1Open your blueprint in a text editor.
2Include the custom property in your blueprint
Vrm.Software.IdNNNN=software_policy_name
3Replace software_policy_name with the name of the policy.
For example where you want to install HP Server Automation Windows ISM Tool, HP Server
Automation Linux ISM Tool, or both, the blueprint might contain the following custom property/value
pairs:
Vrm.Software.Id1000=Windows ISMtool
Vrm.Software.Id1001=RedHatLinux ISMtool
4Save your changes and close the blueprint file.
VMware, Inc. 18
Creating Blueprints for
HP Server Automation 7
The type of blueprint you create depends on how you want to enable HP Server Automation integration.
You need to create a blueprint that includes all of the information required for machine provisioning and
the information required for HP Server Automation integration for either of the following integration
methods:
nProvisioning by using a system from which HP Server Automation deploys images.
nProvisioning by cloning from a template that is prepared for HP Server 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.
This chapter includes the following topics:
nCreate a Virtual Blueprint for Creating from an HP Server Automation Boot Image
nCreate a Blueprint for Cloning from an HP Server Automation Template
Create a Virtual Blueprint for Creating from an
HP Server Automation Boot Image
A tenant administrator or business group manager creates a blueprint for using an HP Server Automation
boot image to deploy HP Server Automation software jobs on machines provisioned from it.
Prerequisites
nLog in to the vRealize Automation console as a tenant administrator or business group manager.
nObtain the following information from your fabric administrator:
nThe name of the HP Server Automation server to be used as the value for the EPI.Server.Name
custom property.
nThe name of the HP Server Automation image to be used as the value for the
Opsware.BootImage.Name custom property.
VMware, Inc. 19
nOptionally, information about the custom properties and values to be applied to all machines
provisioned from the blueprint. See Chapter 8 Custom Properties for HP Server Automation
Integration.
Note A fabric administrator can create a property group by using the property set
HPSABuildMachineProperties, which allows HP Server Automation integration in provisioning
by using a boot image, or HPSASoftwareProperties, which allows HP Server Automation
integration in software deployment. These property groups makes it easier for tenant
administrators and business group managers to include this information in their blueprints.
nFor information on creating a virtual blueprint, see IaaS Configuration for Virtual Platforms.
Procedure
1Select Design > Blueprints.
2In the Actions column, click the down arrow and click Edit.
3Click the Properties tab.
4(Optional) Select one or more property groups.
Property groups contain multiple custom properties.
5(Optional) Add any custom properties to your machine component.
a Click New Property.
b Enter the custom property in the Name text box.
c (Optional) Select the Encrypted check box to encrypt the custom property in the database.
d Enter the value of the custom property in the Value text box.
e (Optional) Select the Prompt user check box to require the user to provide a value when they
request a machine.
If you choose to prompt users for a value, any value you provide for the custom property is
presented to them as the default. If you do not provide a default, users cannot continue with the
machine request until they provide a value for the custom property.
fClick the Save icon ( ).
6Click the Build Information tab.
7Select Create and the ExternalProvisioningWorkflow workflow.
8Click OK.
Your blueprint is saved.
What to do next
Publish your blueprint to make it available as a catalog item. See Chapter 9 Publish a Blueprint.
IaaS Integration for HP Server Automation
VMware, Inc. 20
Create a Blueprint for Cloning from an
HP Server Automation Template
A tenant administrator or business group manager creates a blueprint that enables the deployment of
HP Server Automation software jobs on machines provisioned from it.
Prerequisites
nLog in to the vRealize Automation console as a tenant administrator or business group manager.
nObtain the following information from your fabric administrator:
nAn HP Server Automation template. See Preparing an HP Server Automation Template for
Cloning.
nThe clone blueprint that you want to integrate with HP Server Automation.
nOptionally, information about the custom properties and values to be applied to all machines
provisioned from the blueprint. See Chapter 8 Custom Properties for HP Server Automation
Integration.
Note A fabric administrator can create a property group by using the property set
HPSABuildMachineProperties, which allows HP Server Automation integration in provisioning
by using a boot image, or HPSASoftwareProperties, which allows HP Server Automation
integration in software deployment. These property groups makes it easier for tenant
administrators and business group managers to include this information in their blueprints.
nIf a policy is to be applied to all machines provisioned from the blueprint, you must include the
custom property Vrm.Software.IdNNNN where NNNN is a number from 1000 to 1999, and the
value is set to the name of the policy, for example Windows_ISMtool.
nThe name of the customization specification to be added to the blueprint. See Preparing an HP
Server Automation Template for Cloning.
nFor information on how to create a blueprint for cloning by using the template and customization
specification provided to you by your fabric administrator, see IaaS Configuration for Virtual Platforms.
Procedure
1Select Design > Blueprints.
2Locate the clone blueprint that you want to integrate with HP Server Automation.
3In the Actions column, click the down arrow and click Edit.
4Click the Properties tab.
5(Optional) Select one or more property groups.
Property groups contain multiple custom properties.
IaaS Integration for HP Server Automation
VMware, Inc. 21
6(Optional) Add any custom properties to your machine component.
a Click New Property.
b Enter the custom property in the Name text box.
c (Optional) Select the Encrypted check box to encrypt the custom property in the database.
d Enter the value of the custom property in the Value text box.
e (Optional) Select the Prompt user check box to require the user to provide a value when they
request a machine.
If you choose to prompt users for a value, any value you provide for the custom property is
presented to them as the default. If you do not provide a default, users cannot continue with the
machine request until they provide a value for the custom property.
fClick the Save icon ( ).
7Click OK.
Your blueprint is saved.
What to do next
Publish your blueprint to make it available as a catalog item. See Chapter 9 Publish a Blueprint.
IaaS Integration for HP Server Automation
VMware, Inc. 22
Custom Properties for HP
Server Automation Integration 8
vRealize Automation includes custom properties that you can use to provide additional controls for HP
Server Automation integration. Some custom properties are required for HP Server Automation
integration. Other custom properties are optional.
Required Custom Properties for HP Server Automation
Integration
Certain custom properties are required for a blueprint to work with HP Server Automation.
Table 8‑1. Required Custom Properties for HP Server Automation Integration
Property Definition
VMware.VirtualCenter.OperatingSystem Specifies the vCenter Server guest operating system version
(VirtualMachineGuestOsIdentifier) with which
vCenter Server creates the machine. This operating system
version must match the operating system version to be installed
on the provisioned machine. Administrators can create property
groups using one of several property sets, for example,
VMware[OS_Version]Properties, that are predefined to
include the correct VMware.VirtualCenter.OperatingSystem
values. This property is for virtual provisioning.
VirtualMachine.EPI.Type Specifies the type of external provisioning infrastructure.
EPI.Server.Name Specifies the name of the external provisioning infrastructure
server, for example, the name of the server hosting BMC
BladeLogic. If at least one general BMC EPI agent was installed
without specifying a BMC BladeLogic Configuration Manager
host, this value directs the request to the desired server.
Opsware.Software.Install Set to True to allow HP Server Automation to install software.
Opsware.Server.Name Specifies the fully qualified name of the HP Server Automation
server.
Opsware.Server.Username Specifies the user name provided when a password file in the
agent directory was created, for example opswareadmin. This
user name requires administrative access to the HP Server
Automation instance.
Opsware.BootImage.Name Specifies the boot image value as defined in HP Server
Automation for the 32-bit WinPE image, for example winpe32.
The property is not required when provisioning by cloning.
VMware, Inc. 23
Table 8‑1. Required Custom Properties for HP Server Automation Integration (Continued)
Property Definition
Opsware.Customer.Name Specifies a customer name value as defined in HP Server
Automation, for example MyCompanyName.
Opsware.Facility.Name Specifies a facility name value as defined in HP Server
Automation, for example Cambridge.
Opsware.Machine.Password Specifies the default local administrator password for an
operating system sequence WIM image such as
Opsware.OSSequence.Name as defined in HP Server
Automation, for example P@ssword1.
Opsware.OSSequence.Name Specifies the operating system sequence name value as defined
in HP Server Automation, for example Windows 2008 WIM.
Opsware.Realm.Name Specifies the realm name value as defined in HP Server
Automation, for example Production.
Opsware.Register.Timeout Specifies the time, in seconds, to wait for creation of a
provisioning job to complete.
VirtualMachine.CDROM.Attach Set to False to provision the machine without a CD-ROM device.
The default is True.
Linux.ExternalScript.Name Specifies the name of an optional customization script, for
example config.sh, that the Linux guest agent runs after the
operating system is installed. This property is available for Linux
machines cloned from templates on which the Linux agent is
installed.
Linux.ExternalScript.LocationType Specifies the location type of the customization script named in
the Linux.ExternalScript.Name property. This can be either
local or nfs.
Linux.ExternalScript.Path Specifies the local path to the Linux customization script or the
export path to the Linux customization on the NFS server. The
value must begin with a forward slash and not include the file
name, for example /scripts/linux/config.sh.
Optional Custom Properties for HP Server Automation
Integration
Certain custom properties are optional for a blueprint to work with HP Server Automation.
Table 8‑2. Optional Custom Properties for HP Server Automation Integration
Property Definition
Opsware.ProvFail.Notify (Optional) Specifies the notification email address for HP Server
Automation to use in the event of provisioning failure, for
example provisionfail@lab.local.
Opsware.ProvFail.Notify (Optional) Specifies the HP Server Automation user to whom
ownership is assigned if provisioning fails.
IaaS Integration for HP Server Automation
VMware, Inc. 24
Table 8‑2. Optional Custom Properties for HP Server Automation Integration (Continued)
Property Definition
Opsware.ProvSuccess.Notify (Optional) Specifies the notification email address for HP Server
Automation to use if provisioning is successful.
Opsware.ProvSuccess.Owner (Optional) Specifies the HP Server Automation user to whom
ownership is assigned if provisioning is successful.
Custom Properties That Make HP Server Automation
Software Jobs Available
Depending on how your fabric administrator configures HP Server Automation jobs for
vRealize Automation integration, you might have a choice between making all software jobs available to
machine requesters to select, or you can specify jobs to apply to all machines provisioned from your
blueprint.
Table 8‑3. Custom Properties to Make Software Jobs Available
Property Definition
LoadSoftware Set to True to enable software install options.
Vrm.Software.Id (Optional) Specifies an HP Server Automation policy to be
applied to all machines provisioned from the blueprint. NNNN is
a number from 1000 to 1999. The first property must start with
1000 and increment in numerical order for each additional
property.
IaaS Integration for HP Server Automation
VMware, Inc. 25
Publish a Blueprint 9
You can publish a blueprint for use in machine provisioning and optionally for reuse in another blueprint.
To use the blueprint for requesting machine provisioning, you must entitle the blueprint after publishing it.
Blueprints that are consumed as components in other blueprints do not required entitlement.
Prerequisites
n n Log in to the vRealize Automation console as an infrastructure architect.
nCreate a blueprint. See Checklist for Creating vRealize Automation Blueprints.
Procedure
1Click the Design tab.
2Click Blueprints.
3Point to the blueprint to publish and click Publish.
4Click OK.
The blueprint is published as a catalog item but you must first entitle it to make it available to users in the
service catalog.
What to do next
Add the blueprint to the catalog service and entitle users to request the catalog item for machine
provisioning as defined in the blueprint.
VMware, Inc. 26

Navigation menu