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

2019-06-26 Thread Thomas Lamprecht
On 6/26/19 10:52 AM, Alexandre DERUMIER wrote: >>> 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->{s

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

2019-06-26 Thread Alexandre DERUMIER
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" À: "pve-devel" , "aderumier" Envoyé: Mercredi 26 Juin 2019 0

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

2019-06-26 Thread Thomas Lamprecht
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 the

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

2019-06-25 Thread Dietmar Maurer
> >>So do we want to generate some RRD databases with that data? > > I don't think we need a rrd here, it's a simple status (ok/error/pending/...) > on the transportzone. Ok > I don't want to stream vnet status, because it could be really huge. > (like 20 servers broadcasting 300vnets for exam

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

2019-06-25 Thread Alexandre DERUMIER
Then for detail, click on the transportzone (like the volumes display on the storage on right pane), then query vnets status on the specific node at this time only. But I can use implement colon lists, no problem. - Mail original ----- De: "dietmar" À: "pve-devel" , &

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

2019-06-25 Thread Alexandre DERUMIER
ght pane), then query vnets status on the specific node at this time only. But I can use implement colon lists, no problem. - Mail original - De: "dietmar" À: "pve-devel" , "aderumier" Envoyé: Mardi 25 Juin 2019 08:37:18 Objet: Re: [pve-devel] [PATCH pve

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

2019-06-24 Thread Dietmar Maurer
I am not sure if json is a good idea here. We use colon separated lists for everything else, so I would prefer that. It is easier to parse inside C, which is important when you want to generate RRD databases from inside pmxcfs ... Also, consider that it is quite hard to change that format later, b

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

2019-06-24 Thread Alexandre Derumier
Signed-off-by: Alexandre Derumier --- PVE/Service/pvestatd.pm | 22 ++ 1 file changed, 22 insertions(+) diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm index e138b2e8..bad1b73d 100755 --- a/PVE/Service/pvestatd.pm +++ b/PVE/Service/pvestatd.pm @@ -37,6 +37,12 @