can we add signing to build process?(we most probably will need to use ovftool for that)
ovftool will be useful also for ova generation.
Also it looks like that VMWare Fusion produce more slim image

ls -lah vyos-1.1.7-1a/
total 505696
drwxr-xr-x+ 5 syncer  staff   170B  7 mar 05:09 .
drwxr-xr-x+ 5 syncer  staff   170B  7 mar 06:03 ..
-rw-r--r--+ 1 syncer  staff   247M  7 mar 05:09 vyos-1.1.7-1a-disk1.vmdk
-rw-r--r--+ 1 syncer  staff   139B  7 mar 05:09 vyos-1.1.7-1a.mf
-rw-r--r--+ 1 syncer  staff   6,7K  7 mar 05:09 vyos-1.1.7-1a.ovf
ls -lah vyos_vmware_image/
total 656888
drwxr-xr-x@ 4 syncer  staff   136B  7 mar  2016 .
drwxr-xr-x+ 5 syncer  staff   170B  7 mar 06:03 ..
-rwxr-xr-x@ 1 syncer  staff   6,6K  7 mar  2016 vyos_vmware_image.ovf
-rwxr-xr-x@ 1 syncer  staff   321M  7 mar  2016 vyos_vmware_image.vmdk

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

@higebu i think we need to add also signed ovf
ova is great for offline distribution and ovf can be deployed online from within vSphere Client or vCloud Director web

@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.

@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 https://github.com/higebu/vyos-build/releases/tag/1.2.0-higebu6

@higebu after tests it seems that better to use Debian 6 as OS for appliance.
Since for Other it locks some things in vsphere interface(and in vcloud director too)

With "other" operation system it's impossible to add VMXNET3 interface(seems there are filters)
so Debian 6 solve this perfectly

@higebu lets change OS to Debian6 (so we can assign VMXNET3)
and set VMXNET3 adapter by default

Moving this to 1.2 branch
lets implement changes proposed earlier

Hi,

VyOS version 1.1.7 works very well with vmware and with network card vmxnet3, but for high performance on that platform you need do some system tunning.
Have you got any plan to add that performance tunning to default vmware image?

High performance tunning needs:

• enable multi queue on vmxnet3 card ( multipule vcpu needded),
• enable large buffers on vmxnet3,
• enable large buffers at linux,
• disable gro tso gso at linux

regards
TomekC.

Thank you for the effort. I always liked the VMWare template installation. I also tried it for VyOS 1.2.x on ESXi 6.5. I followed the WiKi instructions which worked like a charm!

Hello @TomekC
you can provide some references?
or even commands?
Thanks!

I'm upgrading my vmware cluster with vyos routers and are doing some tests. My production environment is running on 1.1.7.

enable gro tso gso at linux makes the performance drop to half of the troughput testing with iperf3 using two hardware machines with 10GE.

I can't see the point of having large buffers in routers, then you will introduce jitter and thats bad.

Modern vmxnet3 have default enabled multi queue, but the ethtool in 1.1.7 is to old to support fiddeling with it.

But disable of flowcontrol in the hypervisor is probably a good thing, but cant be done in the guest so this is not applicable.

For the record: I'm using "old" hp dl380 G8 with two E5-2670 and 128GB RAM 1600 MHz for hypervisors and a vyos with 2 vCPU is giving a throughput on 8-9 gigabit on vmware 6.5.

In T14#8787, @aopdal wrote:

I'm upgrading my vmware cluster with vyos routers and are doing some tests. My production environment is running on 1.1.7.

As vell you can perform test on beta version of vyos. This vyos is on modern debian version.

enable gro tso gso at linux makes the performance drop to half of the troughput testing with iperf3 using two hardware machines with 10GE.

you should disable it.
/sbin/ethtool -K eth0 tso off gro off gso off
/sbin/ethtool -K eth1 tso off gro off gso off

I can't see the point of having large buffers in routers, then you will introduce jitter and thats bad.

When you use vyos as VPN concentrator. :)

To enable large buffers you can use ethtool and ifcomand, for voice traffic it can be not a good idea as you said.

/sbin/ifconfig eth0 txqueuelen 16000
/sbin/ethtool -G eth0 rx 4096
/sbin/ethtool -G eth0 tx 4096

Modern vmxnet3 have default enabled multi queue, but the ethtool in 1.1.7 is to old to support fiddeling with it.

Yes to do that I use a bash script witch you can find it at google.
/usr/local/sbin/set_irq_affinity.sh eth0

But disable of flowcontrol in the hypervisor is probably a good thing, but cant be done in the guest so this is not applicable.

Yes it is a good thing.

For the record: I'm using "old" hp dl380 G8 with two E5-2670 and 128GB RAM 1600 MHz for hypervisors and a vyos with 2 vCPU is giving a throughput on 8-9 gigabit on vmware 6.5.

@TomekC @syncer just wondering ... should we maybe add those commands to VyOS CLI?

Optimize a routers defaults should be targeted to the usecase of a router and not for some special use.
If you want to use a vyos as a VPN concentrator - well then configure if for this case. If the defaults are not optimized for general purpose, then you must tweak it for the "main usecase" as a router.

This testing is for verification of my VMWare upgrade, so you will not get any results for the beta version of vyos in my production environment.

@higebu here is latest ovf that i used for official ova -

@higebu have a time to chat on this.
i think we need to add several changes to image specific to vmware (we want use custom config there)

@syncer we can put the changes into the image after T650. I'll work for T650 tomorrow.

@robinelfrink I'm sorry but I deleted the task for open-vmdk. I fixed it.

@syncer I read this: https://twitter.com/vyos_dev/status/1055037448093425664?s=19
so we should use cloud-init for VMware image too?
https://cloud-init.io/

@higebu yes, @UnicronNL already have it in backlog

@syncer @UnicronNL sorry. I did it right now on https://github.com/vyos/vyos-vm-images/commit/00a5684ba31ed5c68d168290fb45a35bf5d58177
And it seems there are two styles of VM image build. ansible playbooks in vyos-vm-images and shell scripts in vyos-build.

the test image with cloud-init is here. https://dev.vyos.jp/vyos/images/rolling/current/amd64/vyos-1.2.0-rolling-201810250337-vmware.ova

ovf/ova must be with properly configured ovf environment and cloud-init package @UnicronNL made into vyos repository

I tested with only NoCloud.
I understand ovf/ova must include ProductSection with some properties like this https://github.com/cloud-init/cloud-init/blob/master/doc/sources/ovf/example/ubuntu-server.ovf
Where is the ovf @UnicronNL made?

In T14#23659, @higebu wrote:

I tested with only NoCloud.
I understand ovf/ova must include ProductSection with some properties like this https://github.com/cloud-init/cloud-init/blob/master/doc/sources/ovf/example/ubuntu-server.ovf

yes, exactly

Where is the ovf @UnicronNL made?

it does not exist yet :)

It seems the ovf I made works good.

vmtoolsd --cmd 'info-get guestinfo.ovfEnv' returns "No value found"...