[pve-devel] [PATCH common] network interfaces code is split into syntax dependent and independent parts

[Igor Vlasenko]

On Wed, May 18, 2016 at 7:57 AM, Dietmar Maurer <dietmar at proxmox.com> wrote:
>> I am trying to port PVE to ALT Linux. It use etcnet as network
>> configuration subsystem
>> instead of /etc/network/interfaces.
>
> Where can I find reasonable documentation for that? I only found:
> https://www.altlinux.org/Etcnet
> Is there an english version?

There is a bunch of README* in source tree, see
http://git.altlinux.org/gears/e/etcnet.git?p=etcnet.git;a=tree;f=docs;h=1a4f2fa688b6a26427d0a87ad75639683bc52040;hb=f687bcc531d6de32bf1bd926be8edeb7286671d9
starting with
http://git.altlinux.org/gears/e/etcnet.git?p=etcnet.git;a=blob_plain;f=docs/README;hb=f687bcc531d6de32bf1bd926be8edeb7286671d9

In short, etcnet is declarative type network configuration system,
Where declarative is the same idea as
in maven (declarative build tool) or rails (declarative web site).
It is adopted in ALT Linux as the default network configuration sysem,
but not yet widespread.

I do not hope to have support for etcnet included officially.
I just hope to make API for network configuration calls to become a
bit more abstract (not too tied to the existence of
/etc/network/interfaces).
It will not only help to support my unofficial port of PVE to ALT Linux
but also will help to port PVE to other network configuration systems
if necessary.