Hi,
I wonder if we could steam the lock status ?
It could be great to display a new icon in pve-manager when a migration occur
or disk is move for example.
Also, I don't known if it's possible, but I could be great to display running
tasks on top of task list.
(Ex: When live migrate a lot
I wonder if we could steam the lock status ?
It could be great to display a new icon in pve-manager when a migration
occur or disk is move for example.
# pvesh get /nodes/localhost/qemu/VMID/status/current
that call provides = 'qmpstatus'
should we distribute that around the cluster?
';
$conf-{lock} = 'backup';
$conf-{lock} = 'snapshot';
$conf-{lock} = 'rollback';
.
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com, pve-devel@pve.proxmox.com
Envoyé: Lundi 15 Juillet 2013 08:16:06
Objet: RE: [pve-devel] stream
From the doc, the status values are:
- status: one of the following values (json-string)
debug - QEMU is running on a debugger
inmigrate - guest is paused waiting for an incoming migration
internal-error - An internal error that prevents further guest
execution has
: [pve-devel] stream lock status in the cluster ?
From the doc, the status values are:
- status: one of the following values (json-string)
debug - QEMU is running on a debugger
inmigrate - guest is paused waiting for an incoming migration
internal-error - An internal error
running = running, migrate , backup, snapshot, rollback
What do you think?
Yes, something like that. (But I don't known if mixing running with other
values could break something in proxmox code)
I introduced 'qmpstatus' for that purpose (instead of using 'status') - to make
sure that
we do
running = running, migrate , backup, snapshot, rollback
What do you think?
Yes, something like that. (But I don't known if mixing running with
other values could break something in proxmox code)
I introduced 'qmpstatus' for that purpose (instead of using 'status') - to
make
sure
';
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Lundi 15 Juillet 2013 09:40:32
Objet: RE: [pve-devel] stream lock status in the cluster ?
running = running, migrate , backup, snapshot, rollback
What
I introduced 'qmpstatus' for that purpose (instead of using 'status')
- to make sure that we do not break something.
Oh, ok, perfect !
So, maybe do we just need to extend:
PVE::QemuServer::vmstatus
# fixme: better status?
$d-{status} = $list-{$vmid}-{pid} ? 'running' : 'stopped';
I don’t want to do that now, so I introduced 'qmpstatus' instead.
Ok, so we just need to put new values in qmpstatus, right ?
yes
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
10 matches
Mail list logo
