Page tree
Skip to end of metadata
Go to start of metadata

Currently, OVA functionality is not compatible with CloudBoot.

Starting with version 5.2, OnApp allows you to import VSs created at other virtualization platforms into OnApp. The OVA is the OVF folder contents all zipped into a single file. Open Virtualization Format (OVF) is an open-source standard for packaging and distributing software applications for virtual servers. The OVA import functionality includes OVA files upload and VSs deployment. This process consists of several steps:

  1. Upload of the OVA file
    When you upload the OVA archive, a special template is created in OnApp with the predefined configuration of VS from the OVA file. 

  2. Adding the OVA template to the template store
    It is required to add a template to any group in template store so that it was available to build VSs on it. 

  3. Billing configuration for OVA
    You can also add a template group created at step 2 to a billing plan, so that provide different levels of accessibility for different customers.
     
  4. VS creation from the OVA template
    To complete the import, build a VS based on the OVA template.

Limitations and prerequisites 

  • Be aware, that only one (primary) disk is imported from the OVA configuration. You can add new disks after the VS is created and built. That will be totally new disks without the information from OVA.
  • OVA functionality is supported only for KVM compute resources.
  • It is required to have at least one backup server running on CentOS 6 or CentOS 7 in the cloud to import from OVA.
  • Only the Ext3 and Ext4 file systems are supported for OVAs.
  • Be aware, that OVA functionality is not supported for compute resources with CentOS 5.x.
  • If your cloud deployment is not a fresh installation, make sure that permissions on OVAs are enabled. For more info refer to List of all OnApp Permissions.
  • OVAs based on Windows 10 can be supported if the required CPU flags are enabled on the compute resource where the OVA virtual server will be built.
  • Be aware that import of OVA may fail when the template is created in VMware vCloud Director. For details, refer to Import of OVA fails when the template is created in VMware vCloud Director.
  • It is not possible to create a VS based on OVA using instance packages at this time. 
  • Be aware, that when backup server and OVA use default CentOS, the volume group names are identical and this can cause a conflict.
  • Currently, only VMDK file format is supported for virtual hard disk drives.

Converting OVF to OVA

You can import virtual servers from OVA only. If you want to import from OVF, you should create an OVA from OVF. The OVA file is a TAR archive, containing the .OVF and .VMDK files. Below you can find an example:

[root@OVA ~]# file /OVA/centos6default.ova
/OVA/centos6default.ova: POSIX tar archive (GNU)
[root@OVA ~]# tar -tf /OVA/centos6default.ova
centos6ovalvm.ovf
centos6ovalvm-disk1.vmdk


To create an OVA file (called centos6.ova for example) in Linux via command line, run the following:

[root@OVA OVA]#  tar -cvf centos6.ova centos6ovalvm-disk1.vmdk centos6ovalvm.ovf
centos6ovalvm-disk1.vmdk
centos6ovalvm.ovf


  • No labels