vmware_content_deploy_ovf_template - create VMs from OVF templates

[ultral]

SUMMARY

vmware_content_deploy_template doesn't support creating VM from OVF templates "Fixes #113"

ISSUE TYPE

• New Module Pull Request

COMPONENT NAME

vmware_content_deploy_ovf_template

[Akasurde]

Rest LGTM

[Akasurde]

LGTM

[goneri]

Hi @ultral, what do we need to test this module in the CI? Do you have some OVF example that are light enough?

[ultral]

Hi @goneri

what do we need to test this module in the CI?

• vmware vsphere
• content library
• OVF template in the content library
• possibility to import

Do you have some OVF example that are light enough?

Nope, my images are built for dev env by packer, so they are big enough. However for test purpose we can use the smallest image without OS

[goneri]

We use this image to start our test VMs: virt-lightning.org/fedora-open-vm-tools-livecd.iso . I'm not familiar with the OVF template, could we generate a template that uses use it?

[ultral]

We use this image to start our test VMs: virt-lightning.org/fedora-open-vm-tools-livecd.iso . I'm not familiar with the OVF template, could we generate a template that uses use it?

so, please correct me if I'm wrong, we should create an OVF template which boots from the ISO. how do you an template of things like that usually? is automated process and we need a commit? or people upload it somewhere?

[goneri]

We use this image to start our test VMs: virt-lightning.org/fedora-open-vm-tools-livecd.iso . I'm not familiar with the OVF template, could we generate a template that uses use it?

so, please correct me if I'm wrong, we should create an OVF template which boots from the ISO. how do you an template of things like that usually? is automated process and we need a commit? or people upload it somewhere?

Thanks. Do you know if we can we automate the OVF creation process? I don't mind having a OVF somewhere that we maintain ourselves, but I would prefer to have a reproducible way to generate it.

[ultral]

We use this image to start our test VMs: virt-lightning.org/fedora-open-vm-tools-livecd.iso . I'm not familiar with the OVF template, could we generate a template that uses use it?

so, please correct me if I'm wrong, we should create an OVF template which boots from the ISO. how do you an template of things like that usually? is automated process and we need a commit? or people upload it somewhere?

Thanks. Do you know if we can we automate the OVF creation process? I don't mind having a OVF somewhere that we maintain ourselves, but I would prefer to have a reproducible way to generate it.

sure, In my env I use jenkins + packer for creating OVF templates. unfortunately, I can not show the real config, however there is the gist https://github.com/ultral/vmware_centos_packer_contentlibrary_ovf

1. build the VM via packer
2. create OVF template from the VM

if you share info how to your build infrastructure work and how we can create OVF for it i will think how to create the test suites for that module.

[goneri]

We use this image to start our test VMs: virt-lightning.org/fedora-open-vm-tools-livecd.iso . I'm not familiar with the OVF template, could we generate a template that uses use it?

so, please correct me if I'm wrong, we should create an OVF template which boots from the ISO. how do you an template of things like that usually? is automated process and we need a commit? or people upload it somewhere?

Thanks. Do you know if we can we automate the OVF creation process? I don't mind having a OVF somewhere that we maintain ourselves, but I would prefer to have a reproducible way to generate it.

sure, In my env I use jenkins + packer for creating OVF templates. unfortunately, I can show the real config, however there is the gist https://github.com/ultral/vmware_centos_packer_contentlibrary_ovf

1. build the VM via packer

2. create OVF template from the VM

if you share info how to your build infrastructure work and how we can create OVF for it i will think how to create the test suites for that module.

Thanks @ultral!

[goneri]

Thank you @ultral for your contribution :-)