Hi, ----- Original Message -----
From: "Sven Kieske" <s.kieske@mittwald.de> To: devel@ovirt.org Sent: Wednesday, February 18, 2015 2:12:15 PM Subject: Re: [ovirt-devel] [VDSM] about improved libvirt-python bindings
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.
My point here is libvirt and oVirt have slightly misaligned path. This is absolutely expected and OK, since libvirt should and can not only serve the purposes of oVirt, but a much broader scope! Nowadays we (oVirt, VDSM in particular) just consume the libvirt python API and we fix the mismatches in our own application code. Most often is a no-brainer, sometimes is annoying. Especially also given the recent efforts to improve and enhance the scalability of VDSM, we may need (today or tomorrow) a different approach. The one I'm offering is *a* potential solution (IMVHO pretty fitting), hence my discussion here :) -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani