Deploying virtual systems using a Virtual Guest Package
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.
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 Server Automation supports on all operating systems. This capability allows you to create multiple VGPs, each designed and tailored for a specific use. For example, you can create one VGP that defines a VM for an development SQL server, while another can be tailored for use by QA as a web server.
You can create VGPs in the following ways:
- For VMware, Microsoft Hyper-V, IBM, Solaris, Citrix XenServer, and Red Hat Enterprise Virtualization environments, you can create the VGP manually, as described in Manually creating a Virtual Guest Package.
- For VMware, Microsoft Hyper-V, Citrix Xenserver, and RHEV Manager platforms, you can use a Virtual Guest Template Enrollment Job to automatically discover operating system templates on those systems, and create Virtual Guest Packages for the discovered templates. See Automatically creating a Virtual Guest Package.
See the following topics for information about creating VGPs.