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

Alexandre DERUMIER aderumier at odiso.com
Tue Dec 11 16:51:47 CET 2018


>>Another way, could be make somekind of template on each local host. (as we only need to duplicate them for each vlan/vxlan). 

for vlan, 
---------
keep using an vmbr a template

auto vmbr0
iface vmbr0 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0



Maybe it could be possible to reuse ifupdown2 native template too ?

%for v in [1,2]:
  auto vmbr0v${v}
  iface vmbr0v${v}
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

%endfor

not sure if we could define the vlan/vxlan id in a list/variable somewhere, an simply reuse them.


/etc/pve/interfaces.vlanlist 

$mylist=[1,2]

then in
/etc/network/interfaces

include /etc/pve/interfaces.vlanlist 

%for v in $mylist:
  auto vmbr0v${v}
  iface vmbr0v${v}
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
%endfor


or for vxlan


%for v in $mylist:

auto vxlan${v}
iface vxlan${v} inet manual
      vxlan-local-tunnelip 192.168.0.1
      bridge-learning off
      bridge-arp-nd-suppress on
      bridge-unicast-flood off
      bridge-multicast-flood off

auto vmbrvx${v}
iface vmbrvx${v}
        bridge-ports vxlan${v}
        bridge-stp off
        bridge-fd 0

%endfor

----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mardi 11 Décembre 2018 10:49:57
Objet: Re: [pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing

>>IMHO this looks like a hack - I wonder how VMware associates the global net to 
>>local devices on the host? 

>From what I have seen, the wizard when you create global net, is able to do local configuration of all hosts interfaces too. (and associate them to global switch). 


Another way, could be make somekind of template on each local host. (as we only need to duplicate them for each vlan/vxlan). 

I need to check, they have a concept of "transport zone", seem to be an abstraction between distributed switch and physical host.(and some kind of vrf/vlan isolation) 
https://www.youtube.com/watch?v=Lsgz88OvxDk 






----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Mardi 11 Décembre 2018 10:16:54 
Objet: Re: [pve-devel] [PATCH pve-docs 0/1] vxlan l3 routing 

> I'll have time to work again on /etc/pve/network.cfg idea. 
> 
> I don't known if you have some time to check my idea about using ifupdown2 "alias" 

IMHO this looks like a hack - I wonder how VMware associates the global net to 
local devices on the host? 

> BTW,talking with students on last training (a lot coming from vmware world), 
> they think it could be great to be able to define global network (distributed virtual switch/ dvs in vmware), 
> for vlan or vxlan, and be able to make permissions on it. (maybe be able to add them in a proxmox pool). 

Yes. Would be great if you work on that. 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 




More information about the pve-devel mailing list