[pve-devel] applied: [PATCH pve-network 0/3] vnet api && cleanups

[Alexandre DERUMIER]

>>I wonder if it would be possible to use a single vnet config file? 
>>You currently use: 
>>
>>/etc/pve/network/vnet.cfg 
>>/etc/pve/network/transports.cfg 
>>
>>Both implementations use SectionConfig.pm, so it should be easy to merge that 
>>into a single config file? 
>>
>>I am just curious if there other reasons to keep that in separate files? 

It was because firstly for vnet, I had custom

vnet0:
     ...

vnet1:
     ....

But in last patch series, I change that to classic sectionconfig

vnet:  vnet0
        ....

vnet:  vnet1
       ...


So yes, I can merge both files.

/etc/pve/network/vnet.cfg ? /etc/pve/network.cfg ?






----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>, "Alexandre Derumier" <aderumier at odiso.com>
Envoyé: Mercredi 3 Avril 2019 06:28:51
Objet: applied: [pve-devel] [PATCH pve-network 0/3] vnet api && cleanups

applied, some questions below: 

> On 03 April 2019 at 00:19 Alexandre Derumier <aderumier at odiso.com> wrote: 
> 
> 
> add vnet api 
> reorganize plugins to Network/Transport aa Network/Vnet 

I wonder if it would be possible to use a single vnet config file? 
You currently use: 

/etc/pve/network/vnet.cfg 
/etc/pve/network/transports.cfg 

Both implementations use SectionConfig.pm, so it should be easy to merge that 
into a single config file? 

I am just curious if there other reasons to keep that in separate files?