[pve-devel] [PATCH v8 pve-network 09/25] api2: increase version on apply/reload only

[Thomas Lamprecht]

On 26.09.20 07:29, Alexandre DERUMIER wrote:
> I was thinking about another way, where user could also manualing edit /etc/pve/sdn/*.cfg files
> (or with some automations tools like puppet,ansible,... to manage their network).
> 
> I was think about this:
> 
> sdn/*.cfg  are the pending config,  we don't increase any version counter here
> 
> when when apply config, we increase version but also we generate a json dump of configurations (vnets,zones,controllers,subnets,...).
> (instead .version file, maybe create a .running-config file, with the json + version in the json)
> 
> 
> This json dump of configuration with be the source to generate the local configuration of each node.
> 
> 
> Like this, we could also display pending change for each vnets,zones,...(or a simple display a "status:pending" in a new column in the config grid for a specific element)
> and user is still able to modify *.cfg manually.
> 
> what do you think about this ?


sounds good to me.

But, do you think complex setups could outgrow the 512k pmxcfs file limit for
big setups?