Add ability to configure via OVF

[rylarson]

RBvomi supports importing an OVF. It would be awesome if we could package vsphere boxes as a tar with an OVF and if no template is specified, use the OVF packaged in the box file.

The template having to be in vsphere already is not conducive to treating the box files like individual artifacts.

[rylarson]

Looking at the rbvmomi code, this will probably require an rbvmomi change as well. It appears rbvmomi expects a url for curl to download and then pipes that into a curl upload. For this to be useful for a box file, rbvmomi need to accept a uri to a local package (the OVF contained in the box file).

[GregDomjan]

+1

[RoadRunnr]

+1

It appears as if rbvmomi is able to handle file:// URL's for local files just fine (tested with curl 7.37.1). rbvmomi also seems to support this (see OvfManager.rb Line 105 ).

So, actually deploying OVF and OVA images should be doable.

[rylarson]

Revisiting this because I have been messing around a lot with ovftool. What do you think about changing the vsphere provider box file format to optionally package an OVA or OVF.

If an OVA/OVF was present in the box file, the plugin could deploy the OVA/OVF to the vcenter server as the named VM as configured in the Vagrantfile.

Thoughts?

[mkuzmin]

Also look at vagrant-vcenter plugin.

[kubrat]

+1