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

image2class: Virtual Machine Image Import Utility - Limitations

Managed Appliances

To create a managed CA 3Tera AppLogic appliance from the specified virtual machine image, the image must conform to the following requirements (or else the import will fail):

• openssh-server or similar should be installed and operational; it needs to be automatically started on boot and configured to allow for root public key authentication.
• The iproute2 utility should be installed and operational.
• The dhclient utility should be installed and operational.
• The wget utility should be installed and operational.
• For Ubuntu appliances, NetworkManager should be disabled/removed.
• For 64-bit Linux-based appliances, the libc6-i386 package should be installed.

General limitations of image2class

• When using the --managed option, only Debian and Redhat based Linux distros are supported
• When using the --unmanaged option, Linux, Windows 2003 and 2008 are supported. If you need to make a windows appliance managed, you need to install the windows server msi, provided with CA 3Tera AppLogic as described in the Windows Installation section of the Appliance Developer Guide.
• After the APK installation is complete, user logins are disabled. Access to a managed appliance is typically done by using SSH public key authentication.
• image2class currently supports only OVA files (single-file OVF packaging) containing a definition of a single virtual machine. OVA files which specify multiple virtual machines are not supported.
• An imported image may have a maximum number of 4 volumes.