----- Original Message ----- > From: "Itamar Heim" <ih...@redhat.com> > To: "\"René \"Koch (ovido)\"\"" <r.k...@ovido.at>, "Doron Fediuck" > <dfedi...@redhat.com> > Cc: "ovirt-users" <users@ovirt.org> > Sent: Sunday, October 6, 2013 10:41:27 PM > Subject: Re: [Users] so, what do you want next in oVirt? > > On 09/05/2013 11:31 AM, René Koch (ovido) wrote: > > - Resource pools > > At the moment only Quotas are available (which is great, btw), but in > > some cases it's necessary to implement resource pools. E.g. Limit CPU, > > Memory and Network for group of test vms, but give full resources to > > production vms. Maybe this could be done with cgroups? > > So e.g. I don't want to give a compile machine a full cpu core, but only > > 1 core with 500MHz or limit the bandwith to e.g. 10Mbit/s. > > doron - doesn't cpu shared provide this? >
CPU shares provide better prioritization, but not hard constraints. So for 3.3 you should be able to use it to prioritize CPU consumption and hopefully we'll get to cgroup limitations in the coming version(s). As for network, we have in master (but not in 3.3) Network QoS, which gives the limitations you were asking for. Current gaps are completing CPU limitations, memory and storage. The latter has an API in VDSM we need to verify and utilize. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
