Creating a VGP in BMC Server Automation for a vCenter environment

You can build a repeatable process for deploying new virtual systems by using a virtual guest package (VGP). The VGP describes the new virtual system you want to add.

For example, you can base the VGP on an existing 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. Having a base package from which to deploy new virtual machines helps enforce consistency and standards, such as including Antivirus and management software on any new virtual machine.

The following sections describe how to create a VGP in BMC Server Automation:

• Before you begin
• To create a VGP for BMC Cloud Lifecycle Management
• To modify the VGP
• Where to go next

Before you begin

To create a VGP for BMC Cloud Lifecycle Management

This section describes how to create a VGP manually. Beginning with BMC Server Automation 8.2, you can also create VGPs automatically, using the Virtual Guest Template Enrollment Job. For more information, see the related topic in the BMC Server Automation online technical documentation.

1. From the Depot folder, right-click the depot folder where you want to add the VGP. From the pop-up menu, select New > Virtual Guest Packageand then the virtualization platform type for the package (VMware, Citrix XenServer, or IBM LPAR).

   Note

   You should create VGPs in the Depot in the CSM_Virtual_Guest_Packages folder.

2. On the Virtual Guest Package dialog, enter the following:
3. Click Next.
4. On the Permissions panel, enter the permissions for the VGP. The Permissions panel is an access control list granting roles access to this VGP. Access to all objects, including the sharing of objects between roles, is controlled through access control lists (ACLs). Make sure that your role has the VirtualGuestPackage.* permission to create a VGP for a VMware vSphere environment.
5. Click Finish.
    A dialog displays, indicating that the package is being saved to the Depot.

To modify the VGP

After the VGP is saved, the Virtual Guest Package editor is displayed, enabling you to modify the VGP.

1. On each tab in the editor, enter the desired configuration settings for your VGP.

2. The following panels apply to VMware environments:

   Note

   To support hostname configuration in the virtual guest, select the Custom option in the VM Config Type Settings tab. Note that when you create a VGP from a VM template you are not able to select the Custom option. This option is disabled.

   VMware - Config panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   VMware - Settings panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   VMware - Network Connections panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   VM Basic Config - Microsoft Windows panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   VM Basic Config - Linux panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   VM Computer Settings panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   Run Once Script panel - Click here to see descriptions of the fields

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   The virtual machine name and the server name are required. However, BMC Cloud Lifecycle Management overrides these values.

3. Save the package.

   For bare-metal virtual machines, create multiple VGPs for multiple OS platforms and when pointing your virtual machines to multiple datastores. Also, you need to create multiple VGPs to provide the following options in the configuration of the virtual machine: vCenter datastore location, default CPU value, and default RAM value.

Where to go next

Publishing-the-Product-Catalog