Previous Topic: image2class: Virtual Machine Image Import UtilityNext Topic: image2class: Virtual Machine Image Import Utility - Usage


image2class: Virtual Machine Image Import Utility - Overview

The image2class utility imports virtual machine images as CA 3Tera AppLogic appliance classes. This makes it easy for users to migrate workloads from existing virtualization deployments into CA 3Tera AppLogic. The virtual machine image that is being imported may be located on either the grid's impex volume or on a remote site accessible over HTTP/HTTPS. The CA 3Tera AppLogic appliance class that is created from the virtual machine can either be unmanaged or managed:

image2class currently supports only virtual machines that comply with the Open Virtualization Format (OVF). For managed appliances, only redhat/debian based OVF images are currently supported. image2class will eventually be extended to support other image formats such as Virtual Hard Disk (VHD). image2class automatically detects the type of image by the file extension of the image.

The image2class utility supports only OVA-style packaging. When importing an OVA image, image2class uses the configuration provided in the .ovf descriptor to generate a class descriptor for the CA 3Tera AppLogic appliance (either a singleton or a catalog class). Because the .ovf descriptor does not provide all of the information needed to properly create an CA 3Tera AppLogic appliance class, image2class provides command line options for specifying/overriding the class configuration (default values are also used where appropriate). If the OVF image contains an CA 3Tera AppLogic appliance class descriptor in ADL format, the utility uses this descriptor for the CA 3Tera AppLogic appliance.