[pve-devel] [PATCH pve-network 0/6] RFC: initial pve-network package

Dietmar Maurer dietmar at proxmox.com
Thu Mar 28 12:24:18 CET 2019


> This is a first attempt to create a pve-network package,
> to allowed defined network at datacenter level (vnet)
> with a plugin infrastructure to handle different kind of network (vlan,vxlan....)

Great! I just setup a new repository for this, and applied a few cleanups:

https://git.proxmox.com/?p=pve-network.git;a=summary

> Currently, it's only generate /etc/network/interfaces.d/vnet (ifupdown2 will be required for online reloading).
> Maybe later it could be great to add tap_plug/veth_plug functions if plugins don't use bridge (ovs or another vswitch) or need something like dpdk,...
> 
> a Vnet is a linux bridge, mapped to a transportzone. (with a vlan/vxlan tag)
> a Transportzone is some kind of template for vnet (we can define vxlan peer ip, allowed vlan/vxlan,vrf,...)
> 
> We could add permissions on transportzone.
> Use case : admin have define a transport zone with some allowed vlan for a customer, 
> and customer is allowed to create vnets on this transportzone.
> (Transportzone = tenant)
> 
> Maybe we could move Network.pm and other network apis into this package later ?

Yes, we can consider doing this later.



More information about the pve-devel mailing list