Re: Virtual networking

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

 



Daniel P. Berrange wrote:  [Tue Jan 16 2007, 10:57:03AM EST]
> 2. The way I was always anticipating remote use of libvirt to work. The
>    app uses libvirt locally which opens a connection to the remote machine
>    using whatever remote management protocol is relevant for the hypervisor
>    in question. eg, HTTP/XML-RPC for Xen, or the TLS secured binary format
>    for the prototype QEMU backend.
> 
>    http://people.redhat.com/berrange/libvirt/libvirt-arch-remote-1.png

So this works to manage a remote host that might not have libvirt
installed...

> 3. The way I think you re suggesting - a libvirt server on every remote
>    host which calls into the regular libvirt internal driver model to
>    proxy remote calls. So even if the hypervisor in question provides a
>    remote network management API, we will always use the local API and
>    do *all* remote networking via the libvirt server
> 
>    http://people.redhat.com/berrange/libvirt/libvirt-arch-remote-2.png

...and this requires each managed host to have libvirt(d).

This is considered a reasonable requirement?

Aron

Attachment: signature.asc
Description: Digital signature


[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]