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
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)
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
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 😉
Steve Jin: VMware VI and vSphere SDK
David Flanagan: JavaScript – The Definitive Guide
).
Marijn Haverbeke: Eloquent JavaScript
Cody Bunch: Automating vSphere: With VMware vCenter Orchestrator
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.
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
You are right!
I changed the permission on the vCO Appliance.
Thanks!
Hey,
First of all, great work with putting together this plugin!
I have a problem though, I’m trying to import the .dar file into vRO 7.3, but I get a “IOException – Not a valid package file, dunes-media-inf is missing!”. Is this a general compatibility issue with importing this into vRO 7.3?
Thanks!
Hi defman,
thanks for using the plugin. It is compatibel with vRO 7.3. Do you have the actual version of the plugin from Solution Exchange?
Hey, yes and I got it working just now 🙂
Thanks for the fast reply!
Hello Christian,
I have a quick question regarding the actual OVA deployment workflow. I try running it by using either Local or FTP as source and I get these errors:
– when using a Local source on a Windows machine where I run the vRO client [2017-10-26 07:30:20.792] [I] Loading OVA content…
[2017-10-26 07:30:20.795] [E] (de.sva.vco.plugin.ovatransfer/retrieveOvfProperties) Error in (Dynamic Script Module name : retrieveOvfProperties#4) / (Is a directory)
[2017-10-26 07:30:20.807] [E] Workflow execution stack:
– when using a FTP source: [2017-10-26 07:36:34.748] [E] (de.sva.vco.plugin.ovatransfer/importVM) Error in (Dynamic Script Module name : importVM#4) Unable to retrieve OvfDescriptor! null
[2017-10-26 07:36:34.757] [E] Workflow execution stack:
***
Any thoughts?
Thank you!
Hi defman,
for a detailed response I need more information’s. Logfiles or screen shots about your inputs would be great.
From the “small” Log you provided it seems that you didn’t choose a correct file but instead you provided only the folder as source.
So, if you can share more details we can have a look what is your problem. Do you have downloaded also the documentation for the plugin with some examples?
Regards
Christian
Hi Christian,
Here’s the log:
[2017-10-26 08:58:30.552] [I] Loading OVA content…
[2017-10-26 08:58:30.555] [E] (de.sva.vco.plugin.ovatransfer/importVM) Error in (Dynamic Script Module name : importVM#4) / (Is a directory)
[2017-10-26 08:58:30.567] [E] Workflow execution stack:
***
item: ‘Import a Virtual Machine from OVF/OVA/item1’, state: ‘failed’, business state: ‘null’, exception: ‘/ (Is a directory) (Dynamic Script Module name : importVM#4)’
workflow: ‘Import a Virtual Machine from OVF/OVA’ (b3495573-2c4e-40e9-8abc-a3460b0af0b3)
| ‘input’: name=sourcePathType type=string value=Local
| ‘input’: name=sourceHostname type=string value=
| ‘input’: name=sourcePort type=number value=21
| ‘input’: name=sourcePath type=string value=D:\ftp\VMware-vLCM-Appliance-1.0.0.7-6600137_OVF10.ova
| ‘input’: name=sourceType type=OvaTransfer:ImportType value=dunes://service.dunes.ch/CustomSDKObject?id=’_ova’&dunesName=’OvaTransfer:ImportType’
| ‘input’: name=vmName type=string value=testvm00018
| ‘input’: name=host type=VC:HostSystem value=dunes://service.dunes.ch/CustomSDKObject?id=’VCENTER%2Cid:host-12652’&dunesName=’VC:HostSystem’
| ‘input’: name=datastore type=VC:Datastore value=dunes://service.dunes.ch/CustomSDKObject?id=’VCENTER%2Cid:datastore-12721’&dunesName=’VC:Datastore’
| ‘input’: name=networks type=Array/VC:Network value=#{#VC:Network#dunes://service.dunes.ch/CustomSDKObject?id=’VCENTER%2Cid:dvportgroup-12364’&dunesName=’VC:DistributedVirtualPortgroup’#}#
| ‘input’: name=vmFolder type=VC:VmFolder value=dunes://service.dunes.ch/CustomSDKObject?id=’VCENTER%2Cid:group-v7893’&dunesName=’VC:VmFolder’
| ‘input’: name=ovfProperties type=Array/CompositeType(key:string,value:string):ovfProperty value=null
| ‘input’: name=deploymentOption type=string value=
| ‘input’: name=diskType type=string value=Thin
| ‘input’: name=powerOn type=boolean value=false
| ‘input’: name=authUsername type=string value=
| ‘input’: name=authPassword type=SecureString value=__NULL__
| ‘input’: name=useAuthentication type=boolean value=false
| ‘output’: name=importedVirtualMachine type=VC:VirtualMachine value=null
| ‘no attributes’
*** End of execution stack.
Thanks!
Hi defmann,
Do you try to access the file via FTP or local filesystem?
I can see the port 21 in your request but also a local Windows Path to access.
When you have the vRO Appliance in place. So, the local access from the vRO Appliance is not so easy possible.
If you use a vRO Server installed on Windows you can use the Local Transfer and access the file local C:\myfolder\myfile.ovf
If you use FTP it should work with a the path ftp://myuser:mypwd@mydomain.tld/myOva.ova
Regards
Christian
Hey,
I did see that port 21 in the logs, but ignored it since I definitely selected Local through the wizard. The “Local” option only applies to the local machine where vRO is running? I was kinda hoping it doesn’t, and it means the local user machine, but it kinda makes sense it’s the vRO box. Considering this I think FTP should be the way to go and I’ll focus on using that.
Thanks for all your help!
Regards,
Hi Christian,
Have you ever ran into strange error when running the workflow from vRealize Automation as XaaS: FaultMessage #1: The provided network mapping between OVF networks and the system network is not supported by any host.
It’s so strange as it works flawlessly from vRO itself. I initially thought it was some sort of issue with vCenter and some googling pointed me in that direction, but it works without any problems manually from vRO when using the exact same network.
Thank you!
Regards,
Hi defman,
that’s strange. Which versions of vRA, vRO and vSphere do you use? I will try to recreate your problem.
Regards
Christian
Hi Christian,
Looks like I have the exact same behavior when selecting a dVS portgroup as the VM network in a different test infrastructure as well. What is really odd is the fact that is works flawlessly through vRO, but I have problems when using it as a vRA XaaS item. If I use a Standard vSwitch port group it works. These are two completely different infrastructures.
I use vSphere 6.5, vRA 7.3 and the embedded vRO in both.
Thanks!
Regards,
Def
Hi Christian,
I am experiencing the exact same issue as defman.
We are using dVportgroups and when the vRA sends it to vRO it converts the type to VC:Network where as when you select it from vCO it is a type of VC:DistributedVirtualPortgroup.
I was able to change the generated workflow to be a type of a VC:DistributedVirtualPortgroup, and when the data come from vRA it works normally.
Anyway we can get a choice when we generate the workflow if it is going to be VC:Network or a VC:DistributedVirtualPortgroup?
Thanks,
Tim
Hi Tim,
I will see how we can implement your request in the one of the next versions. Thanks for sharing your solution.
Regards
Christian
Christian,
Great. Do you have any idea when you plan to release a new version?
Thanks,
Tim
Hey anyone else get Java Heap error?
I am uploading a 3.5 GB OVA.
Does it copy the ova to vRO then push it to vCenter?
Any insight will be helpful.
Hello,
I have installed the plugin on vRO version 7.3. Plugins looks to be installed properly but I am unable to see the actions and workflows that come packaged with the plugin. I did restart the vRO service.
Is there something that I might be doing wrong?
Thanks!
Hi Nitesh,
can you please provide the used Version of the Plugin and the vRO?
Thanks!
Hi Christian,
Please find the requested details.
OvaTransfer: 3.2.0.476
vRO Details:
Version: 7.0.1
Build number: 3533702
Build date: Feb 9, 2016
Database version: 1.71
Thanks for your help!
Hi Nitesh,
mmmh the versions should work. we will test it in our lab.
Meanwhile can you please you try to reinstall the Plugin ( vRO –> Troubleshooting –> reinstall Plugin)
Regards
Christian
Hi Christian,
I’m encoutering this error below:
(de.sva.vco.plugin.ovatransfer/exportVM) Error in (Dynamic Script Module name : exportVM#86) OVF export failed! Error: Connection timed out (Connection timed out)
And when I’ve checked it on the vCenter the status of the Export OVF Template task is “The task was caceled by a user.”
Hi Jay,
are there any Firewalls / Routing instances between the vCO Server and the ESX Host or the Share were to place the exported file?
Regards
Christian
Hi Christian,
Yes, there’s a firewall between vCO Server and ESX Host.
Thanks for the help.
Regards,
Jay
Hi Jay,
can you check your Firewall Logs which ports are blocked between the vCO Server and the ESX Hosts?
Regards
Christian