[libvirt] [PATCH] news: Update release notes

[Daniel P. Berrangé]

On Thu, Mar 01, 2018 at 03:41:00PM +0100, Peter Krempa wrote:
> On Thu, Mar 01, 2018 at 14:34:58 +0000, Daniel Berrange wrote:
> > On Thu, Mar 01, 2018 at 03:28:57PM +0100, Peter Krempa wrote:
> > > On Thu, Mar 01, 2018 at 15:12:39 +0100, Michal Privoznik wrote:
> > > > On 03/01/2018 02:15 PM, Peter Krempa wrote:
> > > > > On Thu, Mar 01, 2018 at 14:08:29 +0100, Michal Privoznik wrote:
> > > > >> Signed-off-by: --help <mprivozn at redhat.com>
> 
> [...]
> 
> > > > > Isn't this an internal change not really used for consumption of
> > > > > clients?
> > > > 
> > > > Not really. Try it yourself:
> > > > 
> > > > virsh -c network:///system net-list --all
> > > 
> > > Well, that obviously has to work. But it's not exactly useful for
> > > general usage:
> > > 
> > > $ virsh -c network:///system list --all
> > > error: Failed to list active domains
> > > error: this function is not supported by the connection driver: virConnectNumOfDomains
> > > 
> > > [...]
> > 
> > Note that in general we don't promise *any* API is supported by *any*
> > URI. The set of APIs provided by any given driver are documented in
> > our page
> > 
> >      https://libvirt.org/hvsupport.html
> > 
> > So the fact that the network:/// URI doesn't support the listing
> > of domains is not a bug. It is just an expected gap in the support
> > matrix for that driver.
> > 
> > IOW, this is largely a documentation task - I still need to provide
> > docs for the secondary drivers to describe this better.
> 
> I'm not saying it's a bug. I'm just pointing out that it's not really
> useful by itself to open connection just to anything else than the VM
> driver itself. Libvirt is a library used to manage VMs and that's the
> main reason anybody will install it. I doubt that anybody would install
> libvirt to manage storage or firewall, since there are way better
> options to do so than our network/storage driver.

It isn't so compelling right now, but once we split libvirtd into one
daemon per driver, it will be more useful to use the specific URIs if
wanting to use the secondary drivers. It will let us containerize the
daemons separately. It will also allow the use of real networking for
the qemu://session daemon without setuid helpers. eg virt-manager can
connect to network:///system to setup networking, to go with its connection
to qemu:///session.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|