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

[Alexandre DERUMIER]

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

it's not possible to have 2 vxlan vtep with same vxlan-id.

auto vxlan2
iface vxlan2 inet manual
    vxlan-id 2

auto vxlan3
iface vxlan3 inet manual
    vxlan-id 2

# ifup vxlan2
# ifup vxlan3
warning: vxlan3: vxlan add/set failed: cmd '/bin/ip link add dev vxlan3 type vxlan id 2 dstport 4789' failed: returned 2 (Error: A VXLAN device with the specified VNI already exists.



But for vlan, it's possible indeed.


----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 13 Décembre 2018 08:31:14
Objet: Re: [pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

> >>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 ?