Daniel P. Berrange wrote:
I think it is unavoidable that every impl is going to express the schedular parameters in a completely different way. Thus if we're going to have an API for fetching/updating schedular parameters then I think we need to have a weakly typed system which is extensible to an new arbitrary fields without requiring any API changes.
Eeeek, weak.typing--If there is a point at which we have to say, 'sorry but libvirt does not cover this very specialised functionality of this particular hypervisor', then this may be it.
At the moment there is only really one hypervisor with scheduling: Xen. The Linux scheduler exists and is used by qemu/kvm but also by many other processes in the whole system, so it may be better for libvirt not to fiddle with it.
By choosing not to support this in libvirt *at this time*, we aren't preventing people from issuing direct xm commands. We're also not closing off future possibilities. If in the future other hypervisors come along which also have schedulers, then we can look at whether it is possible to abstract something across all of them, and implement it in libvirt.
This is, of course, just IMHO. Rich. -- Emerging Technologies, Red Hat http://et.redhat.com/~rjones/ 64 Baker Street, London, W1U 7DF Mobile: +44 7866 314 421 Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland)
Description: S/MIME Cryptographic Signature