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

Alexandre DERUMIER aderumier at odiso.com
Thu Apr 4 20:18:14 CEST 2019


>>I agree. Also that low level C/corosync hacking is no real fun ...
>>
>>Another option is to use pve-daemon to apply the settings.

I wonder if we could re-use the pve-firewall daemon, and transform it to something global for all network things.

for now network config, but they are also frr router, why not in the futur: distributed dhcp server, nat, ....

----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "Stoiko Ivanov" <s.ivanov at proxmox.com>, "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Jeudi 4 Avril 2019 13:57:27
Objet: Re: [pve-devel] rfc : pve-network : idea to generate and reload config accross the nodes

> On 04 April 2019 at 12:16 Stoiko Ivanov <s.ivanov at proxmox.com> wrote: 
> 
> 
> On Thu, 4 Apr 2019 11:57:38 +0200 (CEST) 
> Alexandre DERUMIER <aderumier at odiso.com> wrote: 
> 
> > > But how does it work ? who is currently listening for changes in 
> > > pmxcfs ? (through inotify?) 
> > 
> > >>This is low-level C-code inside pmxcfs (corosync). Please not that 
> > >>INotify does not work at all on /etc/pve/ - instead, we use 
> > >>versions numbers to track changes (see /etc/pve/.version). 
> > ok great ! 
> > 
> > And how can we generate the config && reload network from here ? 
> > Can we call an external perl script ? 
> > 
> From a quick glance - we do this with `corosync-cfgtool -R` when the 
> corosync.conf changes 
> (https://git.proxmox.com/?p=pve-cluster.git;a=blob;f=data/src/dcdb.c;h=6585a3443f0a8239cf668bb10eee1482b0859149;hb=HEAD#l409) 
> 
> However I would keep in mind that perl-scripts (especially if they pull 
> in many modules and dependencies) can take a rather long time (and many 
> disk-hits) when being loaded - not too sure, but could imagine that 
> pmxcfs blocks until the run has completed. 

I agree. Also that low level C/corosync hacking is no real fun ... 

Another option is to use pve-daemon to apply the settings. 




More information about the pve-devel mailing list