Re: [Libvir] Virtual networking

Daniel P. Berrange wrote: [Tue Jan 16 2007, 04:54:49PM EST] > > > 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? > > Personally it doesn't worry me too much - by all means though, I'm open to > arguments against it too..... > > The way I currently look at the problem, needing to deploy a small > C based management daemon (merely linked to an SSL library for > secure comms) isn't very onerous in comparison to the enourmous pile > of python code Xen already requires. For non-Xen backends we'll > definitely need a daemon of some form, since QEMU / KVM / UML / etc > don't have any management daemon at all. For administrators there's > a certain benefit to only having to worry about opening up one > daemon to the public network regardless of which virt system in use. What's the gap (if any) between libvirtd and xend capabilities? i.e. could libvirtd eventually allow dom0 to omit the python-based xen mgmt stack to shrink dom0 to a significantly thinner OS instance?