VMware Realize Orchestrator OVF Transfer Plug-In Version 3 released

I am pleased to announce a new Version of the popular OVF Transfer Plugin. The new mayor release Version is 3. My colleague Sascha Bitzer made a lot of Improvements for the plugin.

In this version we include some bugfixes and also new feature. Here are some Highlights:

The OVA/F Transfer plug-in allows you to import and export virtual machines as OVF/OVA template to/from the VMware vCenter via the VMware vCenter/vRealize Orchestrator.

This plug-in provides actions and workflows to use the OVF/A functionalities directly in

your own workflows. It also supports the automated creation of OVF/A Import Workflows, based on provided ovf/ova files.

Nowadays this plugin also supports new features like vRA-Integration, Authentication and simple File upload

Transfer1

This plug-in includes amongst others following features:

[Export] Export of virtual machines as OVF templates
[Import] Import of virtual machines as OVF or OVA templates
[Import] Automated creation of Import workflows based on OVF/A
[Import] Support for vSS and vDS PortGroups
[Import] Support for multiple vNics
[Import] Support for OVF properties and Deployment Options, e.g. used for virtual appliance imports
[Import/Export] Supported sources/destinations: Locale file, HTTP, HTTPS,FTP, CIFS
[Import] Import OVF/A using vCAC/vRA – Service Blueprint
[Import/Export] Support for Basic and Digest authentication
[Import] Upload of any file to datastore (e.g. ISO)

Transfer2

This plug-in contains two ready to use workflows for importing and exporting virtual machines. It also contains one workflow for extracting and displaying all available OVF

properties usable for the import workflow. For a wizard like experience there is also a workflow for an automated generation of import workflows based on the provided

OVF/A files. This automatically generated workflow will contain all input parameters and options for the given OVF/a file. In addition to those workflows you will now find

two new workflows. The first one is used to upload any kind of file to a target datastore.

This workflow can therefore be used to manage the upload of ISO files/images. The second workflow enables you to integrate the process of importing an OVF/A into your

vRA environment. Now it’s possible to import OVF/A directly with vRA. You can find those workflows in the Workflows folder: SVA/OvaTransfer

Transfer4

The Plugin can be found at the VMware Solution Exchange. Here is the URL:

https://solutionexchange.vmware.com/store/products/vmware-realize-orchestrator-ovf-transfer-plug-in

Have fun and orchestrate the World 😉

Idan

I try to export a virtual machine from a vCenter to the orchestrator appliance.
With the previous version (version 2) with orchestrator 5.5 everything works fine.
But now, after upgrading orchestrator to version 7.2 the export failed.
I tried to upgrade the plugin to version 3. but still the export is not working.

I receive the following error:
[2017-02-12 17:27:39.597] [E] OVF export failed! Error: /data/ovfstore/Win2k12R2Std64bit.ovf/Win2k12R2Std64bit/Win2k12R2Std64bit-disk1.vmdk (No such file or directory)
[2017-02-12 17:27:39.680] [E] (de.sva.vco.plugin.ovatransfer/exportVM) Error in (Dynamic Script Module name : exportVM#86) OVF export failed! Error: /data/ovfstore/Win2k12R2Std64bit.ovf/Win2k12R2Std64bit/Win2k12R2Std64bit-disk1.vmdk (No such file or directory)
[2017-02-12 17:27:39.715] [E] Workflow execution stack:
***
item: ‘Export a Virtual Machine as OVF/item1’, state: ‘failed’, business state: ‘null’, exception: ‘OVF export failed! Error: /data/ovfstore/Win2k12R2Std64bit.ovf/Win2k12R2Std64bit/Win2k12R2Std64bit-disk1.vmdk (No such file or directory) (Dynamic Script Module name : exportVM#86)’
workflow: ‘Export a Virtual Machine as OVF’ (b9685ce8-dd5f-4747-b6cb-0ece4921b394)
| ‘input’: name=destinationPath type=string value=/data/ovfstore/Win2k12R2Std64bit.ovf
| ‘input’: name=virtualMachine type=VC:VirtualMachine value=dunes://service.dunes.ch/CustomSDKObject?id=’vcdev.dev.tase/vm-64884’&dunesName=’VC:VirtualMachine’
| ‘input’: name=ovfName type=string value=Win2k12R2Std64bit
| ‘input’: name=ovfDescription type=string value=
| ‘input’: name=destinationPathType type=string value=Local
| ‘input’: name=destinationHostname type=string value=vmorcodc
| ‘input’: name=destinationPort type=number value=21
| ‘input’: name=authUsername type=string value=
| ‘input’: name=authPassword type=SecureString value=__NULL__
| ‘input’: name=useAuthentication type=boolean value=false
| ‘input’: name=destinationRequestMethod type=string value=POST
| ‘no outputs’
| ‘no attributes’
*** End of execution stack.
- Christian Strijbos
  
  Hi Idan, I have some guess about the problem. This line “/data/ovfstore/Win2k12R2Std64bit.ovf/Win2k12R2Std64bit/Win2k12R2Std64bit-disk1.vmdk (No such file or directory)” shows the problem. There are some possible things which can lead to this error:
  1) After the upgrade of the vCO Appliance the permissions on the file system were reset. Can you check the permissions on the vCO Appliance?
  2) Is the chosen path still valid and reachable?
  
  Regards
  Christian
- Idan
  
  You are right!
  I changed the permission on the vCO Appliance.
  Thanks!

VMware Realize Orchestrator OVF Transfer Plug-In Version 3 released

Related

Official vCenter Orchestrator Training

Categories

Free vCO Training Videos

Recommended Reading