Re: [Libvir] Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)

Anthony Liguori wrote: > For instance, let's say at a university they use an ldap directory to > authenticate users and they decide to implement a migration handler > that uses that for authentication. They may name this "uni://" and > it'll just work. How would they get at this in libvirt without > exposing URIs directly? My latest proposal[1] has a transport parameter (a string) which covers this, in as much as it would allow you to construct URIs which are: <transport>://<hostname>:<port>

Anything more complex than this simple pattern would not work. I think there will always be a conflict within libvirt between allowing the full features of every hypervisor to be expressed, and allowing simple programs to be written which are hypervisor independent. Rich. [1] https://www.redhat.com/archives/libvir-list/2007-July/msg00227.html