[pve-devel] [PATCH v8 pve-network 09/25] api2: increase version on apply/reload only
aderumier at odiso.com
Sun Sep 27 08:27:57 CEST 2020
>>But, do you think complex setups could outgrow the 512k pmxcfs file limit for
I think it should be enough,
zones/controllers/ipam/dns should be small, vnets + subnets should be the biggest part.
around 50bytes by vnet and around 80bytes by subnet with all options.
so around 150bytes for 1vnet+1subnet., this should give use around 3000vnets/subnets.
I think it's enough the current cluster size (20-40nodes max), so maybe 5000vms max
by cluster, 3000vnets should be enough.
----- Mail original -----
De: "Thomas Lamprecht" <t.lamprecht at proxmox.com>
À: "Alexandre Derumier" <aderumier at odiso.com>
Cc: "Proxmox VE development discussion" <pve-devel at lists.proxmox.com>
Envoyé: Samedi 26 Septembre 2020 08:51:42
Objet: Re: [pve-devel] [PATCH v8 pve-network 09/25] api2: increase version on apply/reload only
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
More information about the pve-devel