Hi all,
I'm the primary virt-install/virtinst developer. I'd like to make a
recommendation that koan switch away from using the virtinst library and
just calling out to the virt-install command.
Basically virtinst as a library is crap :) It really became an API by
historical accident. I'm considering in the future discontinuing it's
public API status and just moving it wholesale into the virt-manager
codebase (but it's a low priority and I would make sure all API users
could cope before making that change).
If koan just called out to the virt-install command, and even did
something like virt-install option passthrough via the koan CLI, you
would immediately gain the benefit of all upstream virt-install work.
I'd also say virt-install is an even more stable API then virtinst is:
far more people out there have old virt-install scripts that need to
keep working, but virtinst has only a handful of users and the primary
ones (virt-manager and virt-install) change with it in lockstep, so API
back-compat breakage is a real possibility, though we obviously try hard
to avoid it.
Any thoughts? Possible problems I didn't consider?
Thanks,
Cole
Show replies by date