About deploying virtual assets

The Virtual Guest Package (VGP) and Virtual Guest Job (VGJ) let you to create a new virtual machine according to a specific configuration that you define or one you base on an existing virtual asset.

As a virtual infrastructure administrator, you may have requests for new virtual machines. Depending on the request, you can create the new virtual machine and add it to the host server in any of the following ways:

Base the new machine on the characteristics of an existing virtual machine. See Deploying virtual systems based on existing virtual systems.
Create a VGP that describes the new virtual machine you want to add. For example, you can base the VGP on a VMware vCenter template, or create the VGP using values of your own, if you do not have an existing machine or template on which to base the configuration. See Deploying virtual systems using a Virtual Guest Package.

After you have built the new virtual machine, you can apply compliance checks to it to ensure that it was built according to policy. The VGP and VGJ are available for the following virtualization environments:

Virtual Environment	What's supported
VMware vSphere	You can create a new virtual system based on a VMware vCenter template or virtual machine, or on parameters that you define by creating a VGP in the Depot workspace. You can then use the VGJ to deploy a new VMware virtual machine on the VMware vCenter server (which must be a BMC Server Automation managed server).
IBM PowerVM	You can create a new LPAR or VIO based on an existing LPAR or VIO server, or based on parameters that you define by creating a VGP in the Depot workspace. You can then use the VGJ to deploy a new LPAR/VIO on the IBM frame server, which must be a BMC Server Automation agentless managed object (AMO). BMC Server Automation can support objects that do not have an RSCD agent installed, such as an IBM frame. BMC Server Automation calls these objects AMOs The system manages AMOs through other servers that are equipped with a custom configuration object that can communicate with the agentless device. This documentation refers to those other servers as AMO proxies.
Solaris Zones	You can create a new non-global zone based on parameters that you define by creating a VGP in the Depot workspace. You can then use the VGJ to deploy a new non-Global Zone on the Solaris global zone server (which must be a BMC Server Automation managed server).
Red Hat Enterprise Virtualization	You can create a new virtual machine based on an existing virtual machine or on parameters that you define by creating a VGP in the Depot workspace. You can then use the VGJ to deploy a new virtual machine on the RHEV Manager server (which must be a BMC Server Automation managed server).
Red Hat KVM	You can create a new domain based on an existing domain or on parameters that you define by creating a VGP in the Depot workspace. You can then use the VGJ to deploy a new domain on the Red Hat KVM server (which must be a BMC Server Automation managed server).
Citrix XenServer	You can create a new virtual machine by creating a VGP in the Depot workspace, based on a XenServer template, a custom template or a virtual machine. You can then use the VGJ to deploy a new virtual machine on the XenServer host (which must be a BMC Server Automation AMO).
Microsoft Hyper-V	You can create a new virtual system based on a Microsoft Hyper-V template, or on parameters that you define by creating a VGP in the Depot workspace. You can then use the VGJ to deploy a new virtual machine on the Microsoft System Center Virtual Machine Manager (VMM) server (which must be a BMC Server Automation managed server).

About deploying virtual assets

BMC Server Automation 8.2

On this page