[pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

[Dietmar Maurer]

> >>Do we want to name "transport zones"? 
> maybe, not a big fan of id without meaning.

I just noticed that can have v(x)lan IDs multiple times,
once for each transport zone? So we need a better 
naming scheme, for example:

vxlan2 in zone1 => z1vxlan2
vxlan2 in zone2 => z2vxlan2

Network device name lengths ar limited, so we need
to keep those names as short as possible. So it may be a 
good idea to keep integer number for zones.

zone: 1
  name: network1 
  comment: 100Gbit local net for Customers 
  ... 

> 
> 
> >>And do they have additional associated setting? If so, can/should we store them in /etc/pve/network.cfg?
> 
> maybe do we want to retrict vlan/vxlan type, +vlan/vxlan id we can used on this transport zone (this is what vmware is doing)
> It's more if we want to give differents permissions,
> 
> - root admin role can define transport zones with allowed vlan/vxlan.
> - customer can add his own vxlan in this transport zone

Yes. But this is a permission setting in user.cfg ?