Page Comparison

...

1. Copy the file(s) to the Abiquo NFS repository

   1. Create a separate directory for each OVF Package on the repository file system under the directory for your enterprise ID.
      The folders in the main repository folder match the Enterprise IDs from the Abiquo API. See EnterpriseResource
      We recommend that you use the same base name for the system disk and the OVF file.

      Code Block
      /opt/vm_repository/{idEnterprise}/{myFolder}/myVMTemplate.vmdk /opt/vm_repository/{idEnterprise}/{myFolder}/myVMTemplate_HardDisk.vhd /opt/vm_repository/{idEnterprise}/{myFolder}/myVMTemplate.ovf

      
      

   2. Copy the disk files (e.g. .vmdk, .vdi ...) and the OVF descriptor document (.ovf)

2. Refresh the Appliance Library view of the repository

   Expand
   title Click here to show/hide the screenshot
   In Apps library view, click the refresh button next to the name of your repository in the repository list.

   When you refresh the Apps library, the platform will detect the vm_repository contents (and match them with the OVF description). The platform will convert valid disks to compatible formats for all the installed hypervisors. If there are no hypervisors installed, they will be converted to all formats. The templates will appear in the Apps library view and as soon the conversion files are ready, they will be ready to deploy.

Manually upload an extra disk

You can manually upload a new disk to add to an existing template, but you must also add the disk to the OVF file for that template. When the appliance manager checks the file system, it will detect the new disk, but it will only add the disk to the Abiquo template if the disk is defined in the OVF file.

Manual upload

...

example

In this example we will upload images to the default enterprise repository. The Abiquo default enterprise ID is 1, so the working directory will be: /opt/vm_repository/1.
Create a separate directory for each template to be uploaded and copy it in (using SCP, for example). Here we copy the system disk file and an extra disk.

$ cd /opt/vm_repository/1/
$ mkdir ubuntu-server
$ cd ubuntu-server
$ scp username@10.10.10.10:/home/username/ubuntu_vxxx.vmdk /opt/vm_repository/1/ubuntu-server/
$ scp username@10.10.10.10:/home/username/ubuntu_vxxx_extra_disk.vmdk /opt/vm_repository/1/ubuntu-server/

If you have an Copy the OVF descriptor , copy it too.

$ scp username@10.10.10.10:/home/username/ubuntu_vxxx.ovf /opt/vm_repository/1/ubuntu-server/

Manually upload an extra disk to an existing template

You can manually upload a new disk to add to an existing template, but you must also add the disk to the OVF file for that template. When the appliance manager checks the file system, it will detect the new disk, but it will only add the disk to the Abiquo template if the disk is defined in the OVF file.

Create an OVF descriptor if necessary

Abiquo recommends that you always use an automatically generated OVF file descriptor, but if you do no thave not have one, you can create one following these instructions.

1. Copy the a sample Abiquo OVF file (e.g. OVF Reference#ExampleOVFDescriptor). Name Save the OVF file with the image file name and .ovf extension.
2. Edit the OVF file according to the guidelines in OVF Reference#OVF for Abiquo.
   1. Remember that you need to enter the disk size. See Determine the size of a VM disk file

...