[pve-devel] rfc : /etc/pve/networks.cfg implementation
aderumier at odiso.com
Fri Mar 1 08:04:50 CET 2019
>>I see. I just wanted to avoid an additional daemon to save RAM, but ...
Maybe could we reuse pvestatd ?
maybe we could add a version parameter in /etc/pve/networks.cfg, (user need to increment it to apply config on different nodes, like push a button "commit" in gui),
then pvestatd simply need to compare this version with local version (should be fast and non blocking), and fork a background task to do the change ?
----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 1 Mars 2019 06:38:40
Objet: Re: [pve-devel] rfc : /etc/pve/networks.cfg implementation
> On February 28, 2019 at 9:20 AM Alexandre DERUMIER <aderumier at odiso.com> wrote:
> >>Or just activate when needed (at VM start)? But yes, a separate config is preferable.
> Another thing is if we want to update config. (change multicast address, add a new unicast node,....),
> when the vm are already running.
I see. I just wanted to avoid an additional daemon to save RAM, but ...
More information about the pve-devel