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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 16, 2007 at 10:47:59AM -0500, Anthony Liguori wrote:

> >If we need to express some choice of data channel, TCP, vs SSH, vs SSL/TLS
> >then figure out a way to expose that in the API with an hypervisor agnostic
> >way. Exposing raw QEMU migration URIs is *not* hypervisor agnostic.
> 
> Why?  If nothing but QEMU support ssh:// then exposing an API to do SSH 
> migration isn't really hypervisor agnostic.  It's an API for QEMU.

You're presuming things never change (and that new backends never get
added to libvirt!)

regards
john

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]