Imported Template Guidelines
Before you create a template for import, you must make certain of the following:
Target server can only have a single volume attached. We do not support VM templates with more than one volume.
Network adapter cannot be configured with a static address. It must be configured for DHCP.
Network adapter must be bound to a common driver such as E1000. If in doubt, ask first.
Server must be dismounted from any external connections such as logical mappings to other servers, NFS or SMB mounts, or iSCSI connections.
Server must be unattached from iso images or any other external software media.
Server must allow access via ssh (Linux) or rdp (Windows). You may have to revise your current ACLs or enable the appropriate service.
Agents, tools, drivers, or management software specific to your current infrastructure must be disabled or removed.
Software that could interfere with normal communication, such as firewalls, anti-virus scanners or intrusion detection, must be disabled or removed.
Peripheral components that do not have a cloud equivalent, such as floppy disk, secondary NICs or serial port devices, must be disabled or removed.
The general rule of thumb is to simplify your server as much as possible before you attempt to export it. The simpler it is, the better your chances are of successfully migrating it to Stratosphere..
To import a private template, you will need to host, on an HTTP server, either a QCOW2 image--the "QEMU Copy On Write" format needed for the Stratosphere Cloud, or a single-disk OVA--the VMware "Open Virtual Appliance" format needed for Stratosphere EPN. You cannot import images into Stratosphere in any other format or with any other protocol.
Once you have the file hosted on an HTTP server, make certain that server is accessible to the following addresses: