Ensure your OVF meets the requirements for import that are listed here in our Best Practices and preparation for a virtual machine OVF import KB.
Connect to your CenturyLink Cloud FTP server; instructions detailed here.
- Note: You can import VMs to any available data center in your account; the OVF file is simply stored in your home data center FTP account for initial processing.
In the root directory of your FTP account, create a folder named “import,” if it does not already exist.
Within the "import" folder, create another folder with a name that matches the name of your OVF. Upload the OVF to this location (i.e. "import/sampleovfname"), using your preferred FTP client. Be sure to use only alphanumeric characters in your filename, special characters may result in errors.
- Note: Your VMDK, VMX's, etc must be uploaded to the same location as well. If you export a VM from VMWare, all you need to do is upload the entire folder using the correct folder structure.
- **Note: the VM name cannot include a "." - this will cause import failure.
- Transfer the OVF from your local machine to the subfolder you just created in your FTP account.
- The transfer of the OVF may take several hours, depending on the size of the file and the speed of your connection.
- Any packet loss during the transfer may result in import failure.
When the upload is complete, click Import Server under Infrastructure in the CenturyLink Cloud navigation menu.
You will then see your collection of uploaded OVFs.
- Note: OVFs will be automatically deleted from your FTP server after 5 days. As such, please complete imports shortly after initial upload.
Select the desired OVF to import, and proceed to complete the rest of the Import form, including specifying the data center and group location of the VM. Your OVF must map to one of the operating systems shown below.
Click "Import Server" to initiate the import process.
Upon successful import, your VM will appear in your chosen data center and group location within a few hours.
- Note: Exact timing for the availability of your new VM in the Control Portal depends on several factors, so there is not standard availability time for imported VMs.
- Note:If your OVA import fails with any of the following errros: "Invalid Ovf manifest entry", "The OVF package is invalid and cannot be deployed" or "The following manifest file entry (line 1) is invalid: SHA256 (xxxxxxx.ovf)" please see the following article for resolution: https://kb.vmware.com/s/article/2151537.