Creating a VGP using BMC Server Automation
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
Review the following sections for requirements and recommendations for creating VGPs.
About the VGP
A VGP bundles configuration changes so they can be deployed to hosts/clusters using a Virtual Guest Job. A VGP consists of an instruction set and any files needed for implementing configuration changes. Configuration changes can consist of additions, deletions, and modifications to any of the server objects BMC supports on all operating systems. This capability allows you to create multiple VGPs, each designed and tailored for a specific use.
Requirements
- You should create VGPs from virtual machine (VM) templates that adhere to the requirements described in Creating-VM-templates.
- Create VGPs in the CSM_Virtual_Guest_Packages folder (under Depot) in the BMC Server Automation Console.
- To support hostname configuration in the virtual guest, select the Custom option in the VM Config Type Settings tab. For more information, see VMware-Config.
- To make sure the VMs provisioned using the VGPs can be enrolled in BMC Server Automation successfully, the primary DNS server specified on the BMC Server Automation Application Server should be the same DNS server utilized by the vCenter. Otherwise, BMC Server Automation is forced to wait for DNS propagation before it can communicate with the BMC Server Automation agent on the virtual guest.
- Ensure that the VGP for bare-metal VMs is assigned a larger disk space amount than what is assigned to the system package. Otherwise, the provisioning fails with the somewhat misleading error message OS Not Found.
Recommendations
Consider the following general recommendations for creating VGPs:
- Do not include any static IP addresses in the configuration of the VGP.
- Do not include any information that is instance-specific, such as a hard-coded host name.
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.
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).
On the Virtual Guest Package dialog, enter the following:
- Click Next.
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 required permissions to create a VGP for a specific platform. The following table lists the permissions required to create a VGP for each of the supported platforms.
VGP permissions, by platformVirtual environment
Permission
VMware vSphere
VirtualGuestPackage.*
Citrix XenServer
VirtualGuestPackageCitrixXen.*
- 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.
- On each tab in the editor, enter the desired configuration settings for your VGP.
The following panels apply to VMware environments:
The following panels apply to Citrix XenServer environments:
The following panels apply to IBM environments:
Save the package.
Where to go next