Shell Commands › Utilities › image2class: Virtual Machine Image Import Utility › image2class: Virtual Machine Image Import Utility - Operation

image2class: Virtual Machine Image Import Utility - Operation

Importing an OVF virtual machine as an CA 3Tera AppLogic appliance

The image2class utility creates a new CA 3Tera AppLogic class from an OVA packaged appliance by performing the following steps:

• The OVA package digest and signature are verified (if present).
• If the CA 3Tera AppLogic appliance class is specified as a singleton (that is, my_app:MYCLASS), the application and singleton are created. Otherwise a temporary application is created with a singleton in it.
• The volumes from the OVA package are added to the singleton class. No modifications are made to the volumes at this point.
• The singleton class configuration is modified as follows:
  • Volumes are set to be rw, instantiable. The first volume in the .ovf descriptor, or the one specified by the boot_vol=<id> parameter, is marked as the boot volume.
  • The console is set to ssh:22,text, the most common setting for CA 3Tera AppLogic appliances. This indicates that the appliance provides ssh access through its default interface.
  • The category is set to "image2class"
  • CPU, Memory and Bandwidth resources are configured. Minimum, maximum and default resource assignments are all set to the same value. If specified, the values of command line parameters are used. Otherwise, the values from the .ovf descriptor are used. If no value is present in the ovf descriptor, and a value is not specified as a command line parameter, then the following values are used:
    • CPU: 1.0
    • Memory: 512M
    • Bandwidth: 100Mbps
  • A default network interface is added. If the --external_iface option is given, an external interface is also added. No additional terminals are created on the class boundary. Network configuration from the OVF descriptor is ignored.
  • Properties from the OVF descriptor are added to the CA 3Tera AppLogic class. As required, property names are modified to conform to CA 3Tera AppLogic naming conventions (that is, unsupported characters are replaced so that ip.address becomes ip_address).
  • The description and document URL are set from the configuration in the .ovf file.
• If the --managed option is specified, the hvm2pv utility is executed to convert the singleton into a managed CA 3Tera AppLogic appliance class. See the hvm2pv reference for details.
• If the class option is specified as a catalog class (that is, /user:MYCLASS), the singleton is moved to the specified catalog and can then be used as a regular CA 3Tera AppLogic appliance class.