Abiquo 5.0

Skip to end of metadata
Go to start of metadata

This section describes how to prepare templates for export to public cloud.

AWS Templates

Please see the AWS documentation for information about prerequisites and compatible images at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/VMImportPrerequisites.html

In AWS there may be a small charge for an AWS instance. This is because AWS only supports import of disks to create an AWS instance. So Abiquo will create the instance, take a snapshot of the instance and then terminate it. The snapshot will then be available in the Abiquo Apps library for you to deploy from. To create the AWS instance, Abiquo will automatically select a hardware profile based on the template’s architecture (i386 = m1.medium or x86_64 = m3.medium), and depending on your AWS pricing plan, you may be charged for the instance while it is momentarily deployed to create the snapshot.

Azure Templates

Users must prepare the templates according to the Microsoft documentation for each guest operating system. The following links are provided for convenience, but please see Azure documentation for information about prerequisites and compatible images.

Abiquo recommends that you create a copy of your virtual machine and prepare the copy for export

  • A virtual machine that you have prepared following Microsoft's steps (e.g. sysprep) might not start up in Abiquo.
  • A template that you have prepared for export might not deploy in Abiquo

You can prepare the virtual machine template inside or outside of Abiquo. After you create the template outside of Abiquo, you can upload it to Abiquo and export it.

If you decide to prepare your virtual machine within Abiquo it is NOT necessary to work with a virtual machine template in VHD format or deployed on Hyper-V. It is not necessary for you to have a Hyper-V hypervisor installed in your Abiquo datacenter.

As part of the export to Azure, Abiquo will automatically convert your template to the VHD format that is compatible with Microsoft Azure. See AZURE LINK

Prepare Linux VMs

For a compatibility table of endorsed distributions, see https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-endorsed-distributions/

The following links are provided for convenience only. Always check Azure documentation before performing an export. 

Prepare the image following the link for each endorsed distribution in step 1. See https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd/

Although Microsoft only recommends uploading endorsed distributions, there are also some generic Linux distribution steps. See https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-create-upload-vhd-generic/ 

If you are working in Abiquo, create an instance of the VM to save it as a template in the Apps library.  

Prepare Windows VMs

For a compatibility table, see https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-create-upload-vhd-windows-server/

The following links are provided for convenience only. Always check Azure documentation before performing an export. 

 Prepare the image following the Microsoft instructions. At the time of writing, these can be summed up as follows: run the default sysprep of the machine with the OOBE, generalized and shutdown options.

If you are working in Abiquo, create an instance of the VM to save it as a template in the Apps library. 

Rackspace templates

If you are preparing a template for Rackspace, the template must have the following correctly installed:

  • XenServer tools
  • nova-agent

So for example, you could create an instance of your virtual machine and deploy it on XenServer, install the tools and nova-agent, check that they are working, and then create an instance to use for export.

Reference information: