I have always tried to avoid such things. They are clumsy and error prone....
> I have thinked about a way to generate config and reload it to differents > nodes > > > " > > make changes in /etc/pve/network/*.cfg > > at datacenter level, network panel , click button ->verify config, > this create a > /etc/pve/nodes/<node>/.networkconfigstatus for all nodes (with something like > verify:pending) > > each local node (daemon) will generate the configuration and validate if they > are no conflict/error > The ok/error with message will be stored in .networkconfigstatus (verify:ok) > > Reporting of status of all nodes is displayed at datacenter level. > > > If all nodes verification state are Ok, we can click a button "apply config", > > then local daemon apply configuration and reload. > status ok/error is reported in /etc/pve/nodes/<node>/.networkconfigstatus > > " > > I think it's better than blindly try to reload networkconfig on each change, > as network is critical, > and sometimes admin need to change multiple parameters and apply it once. > > > What do you think about this ? > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
