To deploy a virtual system that is based on the characteristics of an existing virtual system, you create a BLPackage that is based on an existing virtual system, edit the BLPackage to describe the new virtual system, then deploy the BLPackage to the host server.
Note that the newly created VM does not have an operating system installed on it. However, a VM deployed on a Citrix XenServer may have the operating system cloned from the source VM, depending on how you configure the BLPackage.
This approach is useful when you have an existing VM that represents the standard configuration for a specific use, such as the typical system for a developer, and you want to clone that system for future use. This system may be a high-end system with four CPU and 8 GB RAM, for example. You would create a BLPackage based on this system, and could deploy it whenever a new developer was hired.
Browse to an individual instance of the virtual system, for example VirtualMachineX.
In the case of Citrix XenServer, you can clone only those VMs which are in the "Halted" state.
Right-click the instance and select Add To Depot As > BLPackage.
The Create BLPackage wizard opens. In addition to whatever other BLPackage options you choose, make sure to include the following selections:
Create Package From: Live server objects
Select Server Objects
Click the name of the virtual system on which you are basing the BLPackage.
For more information about filling out the wizard panels, see Adding a BLPackage to the Depot.
Fill out the wizard panels as described in Creating a Deploy Job.
In addition to whatever other Deploy Job options you choose, make sure you select a host server (vCenter server, IBM frame, Solaris global zone, Citrix XenServer, Microsoft VMM host, or RedHat KVM host) as the target on the Targets panel.
The IBM frame and the Citrix XenServer are represented by an agentless managed object. A VMware vCenter server might also be represented by an agentless managed object. Note that the Single-User Mode deploy options (Single-user mode without reboot/shutdown and Reboot/shutdown into single-user mode) of an BLPackage are not supported for agentless managed objects.
Targets must match the environment where you first created the BLPackage that defines the new virtual system. For example, if you started by basing a BLPackage on a virtual machine that resided on a vCenter server, then your target must be a vCenter server.
Deploying virtual assets using a BLpackage is supported only for the virtual assets in the list below. If you attempt to deploy any other node or asset (where the root node is not one of the assets listed below), the job fails, and the following message is written to the job log:
PreCondition check failed.
This list is for assets that are deployable using a BLpackage. Deploy for some other virtual assets are supported using a Virtual Guest Package and a Virtual Guest Job.
Review the following considerations prior to creating a BLPackage based on an existing virtual system:
In addition to whatever other BLPackage options you choose, make sure to include the following selections:
Server Properties: You must specify the location of the new virtual system in the virtual infrastructure hierarchy. To do this, provide values for the following properties: ParentCluster (if applicable), ParentDatacenter, ParentHost.
Make sure these values are correct — you may want to look them up (for example, using LiveBrowse of the server) before setting them here.
Note the following considerations when creating a BLPackage based on an existing virtual machine:
If there are two or more adapters (physical or virtual) in the profile, you can delete an adapter from the list using a BLPackage Deploy Job. However, if there is only one adapter shown in the list, you cannot delete it. Note that the Single-User Mode deploy options (Single-user mode without reboot/shutdown and Reboot/shutdown into single-user mode) of an BLPackage are not supported for agentless managed objects.
To avoid unpredictable results or the creation of multiple disks when you use a BLPackage to create an IBM LPAR with a virtual disk attached, do the following:
In addition to whatever other BLPackage options you choose, make sure to set the Zone Path value to a new, unique name for the new non-global zone.
You can perform the following operations on a virtual guest using a BLPackage:
Add NIC (to modify a NIC, you must first delete the NIC and then add the modification as a new NIC)
Rollback of a deleted disk is not supported in a RHEV environment.
Note the following considerations when creating a BLPackage that is based on an existing virtual machine:
You can perform the following operations on a virtual machine using a BLPackage:
Add or delete NIC
Modifying an existing NIC through a BLPackage is not supported. Therefore, do not edit the MAC Address field in the BLPackage.
If necessary, you can roll back a BLPackage Deploy Job, using the Undo option from the Job Results view.
To roll back a deployment: