Creating the VGP in BMC Server Automation for Hyper-V

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.

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

Before you begin

Review the following sections for requirements and recommendations for creating VGPs.

Requirements

• Create VGPs in the CSM_Virtual_Guest_Packages folder (under Depot) in the BMC Server Automation Console.
• Ensure that Windows templates and Linux templates are created as described in the BMC Server Automation documentation.
• Ensure that the VGP for bare-metal VMs is assigned a larger disk space than the space that is assigned to the system package. Otherwise, the provisioning fails with the somewhat misleading error message OS Not Found.
• Ensure that the guest VM has the latest version of the VMM agent installed and running as a service. For successful Linux provisioning, the guest VM must have the latest version of the VMM agent installed and running as a service. The VMM 2012 SP1 Beta does not ship the VMM agent, so you must use the GA version of Microsoft VMM 2012 SP1. Click here to review the Microsoft online technical documentation for installing the VMM agent.
• Starting with BMC Cloud Lifecycle Management 4.6 and later, for Hyper-V Generation 2 VMs:

  • Only template-based VGPs are supported
  • The following supported guest OSs are based on the OSs supported by Microsoft for Generation 2 templates:
    
    • Red Hat Enterprise Linux version 7.1
    • Microsoft Windows 2012
    • Microsoft Windows 2012 R2

  • For static IP support, BMC Cloud Lifecycle Management uses a static IP pool from System Center Virtual Machine Manager (SCVMM). Therefore, the input IP address in the VGP must be part of the pool defined in SCVMM. For details, see the Microsoft online documentation.

    Warning

    Note

    Linux provisioning with multiple DHCP NICs is not supported for Hyper-V Generation 2 VMs. As a workaround, enable the required number of NICs that you need in the provisioned VM in the base Hyper-V template itself. The same workaround applies to Day1 and Day 2 for NICs.

Recommendations

• 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 by using the Virtual Guest Template Enrollment Job. For more information, see the related topic in the BMC Server Automation documentation.

1. From the Depot folder, right-click the depot folder where you want to add the VGP.

2. From the pop-up menu, select New > Virtual Guest Package and then Hyper-V.

   Warning

   Note

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

3. On the Virtual Guest Package dialog, enter the following:

   Warning

   The VM name and the server name are required. However, BMC Cloud Lifecycle Management overrides these values.
4. Click Next.
5. On the Permissions panel, verify that VirtualGuestPackageHyperV.* permissions is enabled for the VGP.
6. 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 VGP editor is displayed, enabling you to modify the VGP.

1. On each tab in the editor, enter the desired configuration settings for your VGP. The following panels apply to Hyper-V environments:

   • Microsoft Hyper-V - Basic panel

     Click here to see descriptions of the fields.

     Warning

     Only a static memory configuration is supported; dynamic memory configuration is not supported.

     Failed to execute the [excerpt-include] macro.

     Warning

     Note

     If the VGP is based on a template,  you must select the Customize OS checkbox.

   • Microsoft Hyper-V - Storage panel

     Click here to see descriptions of the fields.

     Warning

     The first disk in the VGP should always be type IDE.

     Failed to execute the [excerpt-include] macro.

   • Microsoft Hyper-V - Network panel

     Click here to see descriptions of the fields.

     Warning

     For Microsoft Windows 2003 64 bit systems, the NIC type must be synthetic.

     Failed to execute the [excerpt-include] macro.

   • Microsoft Hyper-V - Advanced panel

     Click here to see descriptions of the fields.

     Failed to execute the [excerpt-include] macro.

   • VM Basic Config - Microsoft Windows panel

     Click here to see descriptions of the fields.

     Failed to execute the [excerpt-include] macro.

   • VM Basic Config - Linux panel

     Click here to see descriptions of the fields.

     Failed to execute the [excerpt-include] macro.

   • VM Computer Settings panel

     Click here to see descriptions of the fields.

     Failed to execute the [excerpt-include] macro.
2. Save the package.

Where to go next

Publishing-the-Product-Catalog