[pve-devel] rfc : pve-network : idea to generate and reload config accross the nodes

[Alexandre DERUMIER]

>>I don't really get why you want to do that? There are so many ways to damage a network, and
>>I doubt that we can reliable verify that....

ifupdown2 have a dry-run too, it's working not too bad (but not 100% complete)

But I would avoid some basic mistakes, 
like a vlan interface already defined and enslaved in another bridge for example,
or look to not enslave an interface with ipmanagement in a bridge (try to not break cluster connectivity)


But I don't want to manage rollback across all nodes. 
(config correctly applied on 1 node, another node fail, I don't want to rollback the first node)
It's more best effort, if 1 node have failed, it's simply report the error in his status file.





>>Also, what if some nodes are offline ...
We could make an exception, if a node is offline (down, network daemon down,...),
Then don't wait for validation, and apply config.

Then the local deamon will try to apply config when node is up again.
In case of error, It'll report it through his status file.

----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "Alexandre Derumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Lundi 1 Avril 2019 12:00:13
Objet: Re: [pve-devel] rfc : pve-network : idea to generate and reload config accross the nodes

> maybe better: 
> 
> in gui, at network,datacenter level 
> 
> at each change, make a 
> /etc/pve/networks/vnet.cfg.<randomversion> 
> 
> 
> on local node, the daemon detect the new version,make verification, 
> and update /etc/pve/nodes/<node>/.networkconfigstatus 
> 
> version:<randomversion> verify:ok 

I don't really get why you want to do that? There are so many ways to damage a network, and 
I doubt that we can reliable verify that.... 

Also, what if some nodes are offline ...