On Wed, Apr 16, 2008 at 03:58:16AM -0400, Daniel Veillard wrote: > > One thing we have in mind is driver/software version numbers. For > > example, the control tools may change the domain configuration based on > > whether a certain driver has the support for a new feature. If we > > create the domain's xml with the driver information, we can make this > > decision quickly, on the fly, in dom0. > > Taking the specific example of driver support I think it's far better to > express that as part of the device description of the domain. There's a wider usage case though. Management tools can often need to track assets, and the UUID is not necessarily sufficient for that. Tools want to be able to associate textual descriptions of the asset, or define ownership. All of these are higher-level values that don't necessarily have any meaning to the v12n technology itself. More crucially they can be specific to the management tool, and lack any reasonable generalization. > > This gives the control tools someplace to store that information, rather > > than having to create some separate storage for each domain. > > I think every new addition to the structure need to be examined on a case > by case basis, in order to keep libvirt API and the tools buit on top of > them coherent. I agree with this personally... regards john -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list