[Libvir] Re: [PATCH 1/2] virDomainMigrate implementation (Xen only, no remote, no qemu, no virsh)
Richard W.M. Jones
rjones at redhat.com
Mon Jul 16 16:28:23 UTC 2007
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
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3237 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20070716/d3240d75/attachment-0001.bin>
More information about the libvir-list
mailing list