I created Jenkins job for vyos-integration-test: https://ci.vyos.net/job/vyos-integration-test/
It works.

I created initial script for making AMI with importing VMDK. I think this way is more useful for multiple region support.
The commit is here: https://github.com/vyos/vyos-build/commit/3dc5653bbb8133f976e4603c8f78a5f6cf686405
What do you think?

Temporary download site for testing: https://dev.vyos.jp/vyos/images/
Also VMware OVA and Hyper-V image are available.

working job: https://ci.vyos.net/job/vyos-build-vm-images/

I got a physical server with VT enabled for building qemu image and running integration test.

I tested VyOS image for Azure with waagent for Debian. But it doesn't work. The installation script for waagent is here: https://github.com/higebu/vyos-build/blob/c53c52c25979a50c20bfc1225a22eae66a9f031a/scripts/packer-scripts/azure.sh

@UnicronNL Thanks.

And https://ci.vyos.net certificate is invalid.

https://ci.vyos.net/computer/jessie64devel.vyos.net/

Nightly builds are not working again? It seems jessie64devel.vyos.net is down now.

@amos.shapira Thanks!

We need this? https://github.com/hiroyuki-sato/vyos-cfg-zabbix-agent

Related VMware KB: Snapshot quiescing fails on Linux guests after upgrading to ESXi and VMware Tools 5.1 and 5.5 (2038606)

@adestis @dmbaturin We had an issue like this, and the workaround is here:

@syncer https://github.com/higebu/vyos-build/releases/tag/1.2.0-higebu6

I confirmed 4.4.0-1+vyos2+current1 iproute and iproute2 packages in the image. Thanks!

@UnicronNL Thank you.

Why we build only "iproute" package now? I guess we should build both "iproute" and "iproute2". And current iso includes debian packages.
Current iproute and iproute2 version is here:

@syncer UnicronNL added open-vm-tools into iso with this commit: https://github.com/vyos/vyos-world/commit/ecae4cb98704f86b16a5a9935f94fcb6a996326f.
So I removed installing open-vm-tools process from 'build-vmware-image'.
My testing images are here: https://github.com/higebu/vyos-build/releases/tag/1.2.0-higebu5.

@syncer Sorry, I already added support for signed ovf to current branch, but didn't upload my ovf.
And we should rebuild open-vm-tools for VyOS kernel header as T16. I'll tryed to add the rebuild step to OVF build process.

Yes, we can add it to build process with ovfool.
How about "current" image from http://dev.packages.vyos.net/iso/current/amd64/ ?

@syncer OK. I'll fix them.

@syncer I uploaded my image on GitHub: https://github.com/higebu/vyos-build/releases/tag/1.2.0-higebu1

IMHO, other linux is better than Debian, because VyOS is not Debian.

@syncer vSphere 5.0 doesn't reach EOS, but I think we can keep HW version 9 too. Why do you want to use Debian 6 as OS?

I tested it on vSphere 6.0 and it works fine! Also I changed the osType to other26xLinux64Guest for old version of vSphere.

The OVF built on my machine works fine on VMware Workstation 12. I'll test on ESXi soon.

I pushed the fix.

Thanks!