[pve-devel] [PATCH pve-manager 1/2] pvestatd : broadcast sdn transportzone status

[Alexandre DERUMIER]

>>you would need to save them by a it's own ID independent key? 
yes

>>
>>'sdn/zones' 
>>
>>Then a simple "broadcast_node_kv('sdn/zones')" will delete all. 

yes, that's what my patch is doing currently 
(I push my json->{$zoneid->{status}
               ->{$zoneid}->{status}

to broadcast_node_kv('sdn').


But do you mean I should brodcast each zone to broadcast_node_kv('sdn/zones/$zoneid') ?
  


>>Or do you think a zone state can get to big? We currently can 
>>save 32kb in a kv entry. 
No it's pretty small. (Currently I'm sending a status string "available/ok/error", but I could also send an integer)


----- Mail original -----
De: "Thomas Lamprecht" <t.lamprecht at proxmox.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>, "aderumier" <aderumier at odiso.com>
Envoyé: Mercredi 26 Juin 2019 09:00:06
Objet: Re: [pve-devel] [PATCH pve-manager 1/2] pvestatd : broadcast sdn transportzone status

On 6/26/19 5:36 AM, Alexandre DERUMIER wrote: 
> If I'm using kvstore for broadcast, with columnlist, I think I'll have 1key by transportzone, 
> not sure it'll really clean. (I also don't known how to cleany remove a key if a transportzone is removed from config) 
> 

you would need to save them by a it's own ID independent key? 

'sdn/zones' 

Then a simple "broadcast_node_kv('sdn/zones')" will delete all. 

Or do you think a zone state can get to big? We currently can 
save 32kb in a kv entry. 


> I don't known what is the better/fastest way to store this kind status ? (kv ? rrd ?) 

I think faster is not to important here, for simple state maybe use kv. 

> 
> Also,I don't known if user would like to have network stats ? Maybe for vnets ? 

Highly probably, and for that RRD would then be great too.