Sense available hypervisors (was: Re: [Libvir] RFC: Broadcast our presence with avahi)

[Daniel P. Berrange]

On Fri, Sep 14, 2007 at 08:25:07AM +0100, Richard W.M. Jones wrote:
> Daniel P. Berrange wrote:
> > - I advertise two subtypes, of '_xen.libvirtd._tcp' and 
> > '_qemu.libvirtd._tcp'
> >   What I actually want todo is to be able to probe the libvirt local 
> >   drivers
> >   to auto-discover what virtualization platforms are available. A sort of
> >   lightweight  virConnectOpen which merely returns TRUE/FALSE and doesn't
> >   actually allocate a virConnectPtr object. Need to extend the internal
> >   driver API for this.
> 
> I wanted this feature too, however I don't think the way that you're 
> proposing is right.
> 
> Just as virConnectGetCapabilities returns the capabilities of the 
> current hypervisor, I think there should be a call like 'virGetInfo' (or 
> something like that) which returns the capabilities of the node, which 
> would include what hypervisors are supported.

That would solve the issue of having to have the mdns code hard code the
list of URIs / drivers to probe for. Perhaps virNodeGetCapabilities(). Not
sure what other info we'd want to return besides just a list of usable
connection URIs, or available drivers. 

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|