@olivierlambert Sure!

By way of example, when a new XCP-ng host is setup, all interfaces are created with an MTU of 1500 (even 10G interfaces).

If I create a bond interface on top of two of the 10G interfaces, the default MTU is set to 1500.

If I then create a VLAN interface on top of the bond interface, and set the MTU to 9000, XO happily lets me do so, but jumbo packets over it don't work because the MTU on the underlying interfaces is still 1500 (e.g. ping -s 1700 via the new interface fails).

If I destroy and re-create the underlying interface (bond0) with an MTU of 9000, then re-create the VLAN interface on top with an MTU of 9000, then things work much better (ping -s 1700 via the new interface succeeds).

Does this help?

Thanks

@lukasz-engel said in Feature request - VM folders:

My 2 cents as current vSphere user (searching for replacement after new VMware prices knocked my socks off):

Tags in XO are currently only "view filtering feature", nothing more.
There is no method in XO to (without selecting each vm separately):

attach ACL to group of vms select group of vms for backup job

Tags are also error-prone, as I have to manually enter tag name each time (for each vm) and possibly make a typo (there are not even "hints" from current tag names).
I would like to add vm to "group" and this should cause deriving ACLs from "group" and adding to backup job assigned to "group", etc; whatever this "group" would be - folder/tag.
As I have ~500 vms, grouping is "must have" for me.
I'll live if "groups" are tags not folders.
But not having this at all in XO is BIG disadvantage for me. 😞
(without this I quite like what I found in xcp-ng/xo).

For me - something like folder seems more natural for such things than tags, but I am biased (as vSphere has folders...).

And generally - in current situation (new prices for vSphere) I suspect there may be more users like me, searching for vSphere replacement, and making XO more friendly for them would be advantage for them...

I do think a lot of this 'group' idea could be made possible using the self service resourceSets, especially if we were able to maybe set "Operator" ACLs on said resourceSet. Maybe even allow tags to be applied to a resourceSet so things like backups would be applied to entire resourceSets vs. an individual VM?