On Mon, Jul 16, 2007 at 11:30:33AM -0500, Anthony Liguori wrote: > Richard W.M. Jones wrote: > >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> > > SSH requires: > > ssh://[user@]hostname[:port] > > So that wouldn't work :-( Sure it would - rich was just showing simplified syntax - the URI rules/spec allow for a username and we already use this syntax with a username in the remote driver URIs. eg $ virsh --connect qemu+ssh://root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx/system list --all Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list