VMware vCloud Government Services OVF and OVA limitations

Products

• VMware

Issue/Introduction

The purpose of this article is to outline the different scenarios that pre-packaged OVF and OVA files could fail with when trying to upload into the VCGS environment.

This assumes an understanding of the OVF and OVA structures. It may also require the ability to modify files locally, or even upload locally to VMware Virtual Center Server, to modify and re-export in preparation for the upload to VCGS.

These limitations apply for any implementation of VMware vCloud Director. As it relates to the way the tenants are isolated in their individual Organizations, and how the technology is layered on top of Virtual Center Server, which the user does not have access to.

Symptoms:

• Uploading an OVF in VMware vCloud Government Service (VCGS) reports:
  
  successfully uploaded
  
  
• The upload has failed.
• When uploading you see the error:
  
  Unable to perform this action. Contact your cloud administrator
  

Resolution

• The OVF or OVA was exported with an ISO image attached and mounted to it:
  
  Even though the packaging of the appliance may include this ISO image, the upload will not succeed as the naming of the ISO and the expected destination datastore will not map as they would in Virtual Center Server. The solution is to edit the OVF or OVA and remove any virtual machine ISO attachments, and then re-export in preparation for the upload to VCGS .
  
  
• The OVF or OVA is 1TB in size:
  
  There will be issues uploading anything larger than the default 300GB (VPC) or 500GB (dedicated) allocation to the transfer zone. The solution is to import this into Virtual Center Server as thin disk and then re-export as thin disk.
  
  Another solution is to remove any data disks that are larger than 500MB for the upload, and re-create them after they are successfully uploaded into your Organization.
  
  
• The OVF or OVA was created with networks that will not exist as they would in Virtual Center Server:
  
  The solution is to modify the networks beforehand, or change the networks as the appliance is deployed, choosing the Organization Network created within your Organization. Ensure you have created sufficient networks, as required by the appliance you are uploading.
  
  
• The OVF or OVA has custom fields that need to be assigned during the import process, but that wizard is not working in VCGS:
  
  The solution is to upload into a local instance of Virtual Center Server, answer the questions in the creation wizard, verify the solution works, then re-export in preparation for the upload to VCGS.
  
  
• The OVF or OVA needs SSL verification to be carried out online:
  The solution is to upload into a local instance of Virtual Center that is on the Internet and can verify the SSL certificate, and then re-export in preparation for the upload to VCGS.

Additional Information

If the modification is too complex, or local import and export is not possible because Virtual Center Server is not available, open a support request with VMware for the vCloud Government Service. Provide as much information as possible to assist troubleshooting. For example:

• The appliance vendor
• Type of file
• Disk size requirements
• Hardware compatibility
• Number of virtual machine networks required.
  
  Note: A link to download the OVF or OVA if possible, may also assist with troubleshooting.
  

For more information, see How to file a Support Request in Customer Connect (2006985).

How to file a Support Request in Customer Connect

Impact/Risks:
The pre-packaged nature of the OVF and OVA, if modified as recommended, might not comply with the intended Implementation and Use Guidance of the vendor or distributor. Take this advice into consideration if errors arise and use best judgement to weigh the risk of upload success and manipulation of the packaged solution.