[libvirt] [PATCH] daemon: Dynamically create worker threads when some get stuck

Daniel P. Berrange berrange at redhat.com
Mon Jun 20 13:20:30 UTC 2011


On Mon, Jun 20, 2011 at 01:41:41PM +0800, Daniel Veillard wrote:
> On Fri, Jun 17, 2011 at 01:26:06PM +0100, Daniel P. Berrange wrote:
> > On Fri, Jun 17, 2011 at 12:46:33PM +0200, Jiri Denemark wrote:
> > > On Fri, Jun 17, 2011 at 10:55:43 +0100, Daniel P. Berrange wrote:
> [...]
> > What I do think we need is an administrative interface to libvirtd. We ought
> > to be able to connect to libvirtd without opening a hypervisor connection,
> > and do various admin operations. In particular I'd like to be able to change
> > logging filters + outputs on the fly & kill off active client connections.
> > We could also make it possible to increase the thread limits on the fly.
> 
>   yes that's would be a welcome addition, agreed.

Another thing is that if we had the fine grained access control system
I described in another thread last week, then we could create some kind
of "super admin" account which could issue API calls, ignoring the request
and thread limits, as a means to a recover a system, or abort a troublesome
migration job etc, while still controlling normal libvirt users.

Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|




More information about the libvir-list mailing list