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

[Alexandre DERUMIER]

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


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



----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "Alexandre Derumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mercredi 12 Décembre 2018 18:33:43
Objet: Re: [pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

> >>That "transport zone" looks interesting. 
> 
> >>We you just mark physical interfaces (or bridges?) as part of a transport zone. 
> >>Then we have everything to setup the vxlan (each vlan belong to a zone)? 
> 
> yes, it should work. (interface could be better I think). 
> 
> /etc/network/interfaces 
> iface eth0 
> transportzone 1 
> address 192.168.0.1 

Do we want to name "transport zones"? And do they have additional 
associated setting? If so, can/should we store them in /etc/pve/network.cfg? 

/etc/pve/network.cfg 
------------------------ 
zone: network1 
comment: 100Gbit local net for Customers 
... 

vlan : mycustombridge 
transportzone network1 
... 
------------------------- 

?? 

> for vlan 
> -------- 
> /etc/pve/network.cfg 
> 
> vlan : mycustombridge 
> transportzone 1 
> vlan 2 
> bridge-vlan-aware 1|0 (for QinQ) 
> 
> This create 
> 
> iface mycustombridge 
> bridge-ports eth0.2 
> .... 
> 
>