This section explains how to collect cloning images.
Use the following methods to collect cloning images:
Collect cloning images from L-Servers with an OS installed
Collect Cloning Images from Templates of Server Virtualization Software
Note
For physical L-Servers, agents must be registered before collecting cloning images.
For details, refer to "D.7.2 Cloning Images" of the "Setup Guide CE".
Use the following procedure to collect cloning images:
Collect cloning images from L-Servers with an OS installed
After installing an OS, right-click the target L-Server in the orchestration tree, and select [Cloning]-[Collect] from the popup menu.
The [Collect a Cloning Image] dialog is displayed.
To use this feature, the following settings must first be defined:
Note
For physical L-Servers, the target L-Server must be operating when cloning images are being collected.
Cloning images cannot be collected from a physical L-Server on which a VM host has been installed.
For virtual L-Servers, the target L-Server must be stopped when cloning images are being collected.
Enter a name to identify the collected cloning image.
For a cloning image name, enter a character string, beginning with an alphabetic character (upper or lower case), and containing up to 32 alphanumeric characters (upper or lower case) and underscores ("_").
Select when specifying the same name as that of a cloning image which has already been collected. Select the cloning image from the list.
For cloning images with the same name, the number that can be retained is the number of cloning image versions.
By default, the maximum number of stored cloning image versions is set to 3.
Select the storage location for cloning images. Clicking <Select> displays the [Select a Location for this Image] dialog.
Select the storage location, and click <OK>.
Select the image pool to register cloning images in.
Enter a comment that identifies the cloning image.
Up to 128 characters other than percent signs ("%"), back slashes ("\"), double quotes ("), and line feed characters can be specified.
Click <OK>.
Cloning images are stored in image pools.
Clicking <Cancel> in the Recent Operations area displays a confirmation dialog and stops the process.
From the command-line, execute rcxadm image create. For details on the rcxadm image create command, refer to "1.4.1 rcxadm image" of the "Reference Guide (Resource Management) CE".
Cloning images (identifiable by their name attribute) can be managed by image version.
Collecting Cloning Images from Templates of Server Virtualization Software
For details, refer to "7.7.1 Virtual Image Resources".
Note
When using MAC license authentication for activation of Windows Server 2008 images, Sysprep can be executed a maximum of three times. Since Sysprep is executed when creating L-Server with images specified or when collecting cloning images, collection of cloning images and creation of L-Servers with images specified cannot be performed more than three times. Therefore, it is recommended not to collect cloning images from L-Servers which have had cloning images deployed, but to collect them from a dedicated master server.
The network parameter auto-configuration function defined in a cloning image cannot be used for Resource Orchestrator.
When the target server of cloning image collection has a redundant NIC configured, release redundancy and then perform collection.
[VMware] [Hyper-V]
The disk space necessary for the collected cloning images can be confirmed from the following display.
Resource list for image pools, or cloning image list in the [Resource Details] window
Resource list for image resources, or version list in the [Resource Details] window
From the command-line, execute rcxadm image list. For details on the rcxadm image list command, refer to "1.4.1 rcxadm image" of the "Reference Guide (Resource Management) CE".
[Xen] [KVM] [Oracle VM]
The disk area necessary for extraction cannot be checked from collected cloning images.
For this reason, include the disk size in the cloning image name or the comment, and check the necessary disk area is available before extracting images.
[VMware]
For details on how to collect cloning images on VMware, refer to "Collecting a Cloning Image" of "E.2.5 Setup" of the "Setup Guide CE".
[Hyper-V]
For details on how to collect cloning images on Hyper-V, refer to "Collecting Cloning Images" of "E.3.4 Setup" of the "Setup Guide CE".
[Xen]
For details on how to collect cloning images on RHEL5-Xen, refer to step 3. in "L-Server Creation" in "E.4.4 Setup" of the "Setup Guide CE".
[KVM]
For details on how to collect cloning images on RHEL-KVM, refer to step 3. in "L-Server Creation" in "E.6.4 Setup" of the "Setup Guide CE".
[Oracle VM]
For details on how to collect cloning images on Oracle VM, refer to "Collect Cloning Images" of "E.5.4 Setup" of the "Setup Guide CE".
Point
[VMware]
When "Default" is specified in the [Collect a Cloning Image] dialog, it is assumed that the virtual storage resource containing the L-Server for collecting cloning images has been specified.
[Hyper-V]
Images are stored in the SCVMM library.
Specify a library which has sufficient available disk space to store the collected images.
When "Default" is specified in the [Collect a Cloning Image] dialog, selection is made from libraries registered with SCVMM, but collection of images may fail as the available disk space of libraries is not managed by SCVMM.
[Xen]
When "Default" is specified for the storage destination of images during cloning image collection, a virtual storage is automatically selected from the same storage pool as the virtual storage containing the target L-Server from which cloning images will be collected.
[KVM]
When "Default" is specified for the storage destination of images during cloning image collection, a disk is selected from the storage pool where disks (which are used by the target L-Server from which cloning images will be collected) are registered.
[Oracle VM]
The storage location for images which was specified in the [Collect a Cloning Image] dialog is disabled.
It is assumed that the virtual storage resource containing the L-Server for collecting cloning images has been specified.
Cloning images (identifiable by their name attribute) can be managed by image version.
If a cloning image is created using VM management software, it can be used as is.
