This is great news! Thanks everyone for your support.
And special thanks to Tomas for leading the development effort
and OPW project that brought us this far.
Martin
- Original Message -
From: Tomas Jelinek tjeli...@redhat.com
To: Donny D do...@cloudspin.me
Cc: Brian Proffitt
On 02/14/2015 02:39 AM, Cameron Norman wrote:
Hello,
Hi,
Well I think there shouldn't be anything broken if you would remove it,
as we do reference everything by name everywhere.
The reason for hard-coding it is that we have it on fedora and RHEL in
the setup package See:
Hi,
This is about the changes introduced by patch
http://gerrit.ovirt.org/#/c/35281 (restapi: adjust api to new
graphics representation).
There are a couple of issues with the VM's display type value:
(1) the display - type value of the VM in the REST API seem to
map to different
Hi,
as far as I understand this would make it easier to implement/use
upstreams(libvirt) existing python-bindings in ovirt?
in this case, I think this is a huge improvement.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH Co. KG
Königsberger
Hi,
during my sampling overhaul effort I faced various times a mismatch between
what the libvirt-python API offers for bulk stats and what VDSM needs.
The return value of bulk stats is a something like
[(dom1, {dict_of_bulk_stats1}), {dom2, {dict_of_bulk_stats2}), ...]
While VDSM almost all
