>>we close connection immediately, so I guess events arrive later (so we miss
>>them).
So currently, each process/workers/daemons try to access concurrently to same
qmp socket, then need to close it fast to not block other
process/workers/daemons right ?
Maybe can we improve that (not for proxmox 3.0 because I think it's a big task).
Something like a qmp proxy, keeping the connection always open with qmp socket,
queueing incoming requests from daemons and parsing continuously the result.
Something like
-----------------------
process-----(http/json?)-------->| QMP PROXY |
workers------------------------->| queuing request |----always
open--------> /var/run/qemu-server/vmid.qmp
daemons------------------------->| |
| |
<-------------------------| response |<---always
open----------
<-------------------------| |
<-------------------------|------------------------
|
|events handler
syslog/other<---------------------------|
What do you think about this ?
----- Mail original -----
De: "Dietmar Maurer" <diet...@proxmox.com>
À: "Alexandre DERUMIER" <aderum...@odiso.com>
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 6 Mai 2013 19:03:13
Objet: RE: [pve-devel] qemu-server : drive-mirror : die if stats are empty.
> I had tried to syslog the current qmp response in qmpclient.pm, I got
> nothing,
> except events for vm stop, vm cont and cd eject.
we close connection immediately, so I guess events arrive later (so we miss
them).
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
