If you are doing something with OpenVZ, like consulting, services, training course, make sure to add a note to Partners page.
Containers/Guarantees for resources
From OpenVZ Wiki
This page describes how guarantees for resources can be implemented.
How to guarantee a guarantee
It's not obvious at the first glance, but there are only two ways of how a guarantee can be provided:
- reserve desired amount in advance
- limit consumers to keep some amount free
The first way has the followong disadvantages:
- Reservation is impossible for certain resources
- such as CPU time, disk or network bandwidth and similar can not be just reserved as their amount instantly increases;
- Reserved amount is essentially a limit, but much more strict
- cutting off X megabytes from RAM implies that all the rest groups are limited in their RAM consumption;
- Reservation reduces containers density
- if one wants to run some identical containers, each requiring 100Mb on 1Gb system, reservations can be done for only 10 containers, and starting the 11th is impossible.
On the other hand, limiting of containers can provide guarantees for them as well.
Providing a guarantee through limiting
The idea of getting a guarantee is simple:
if any group gi requires a Gi units of resource from R units available then limiting all the rest groups with R − Gi units provides a desired guarantee
For N groups in the system this implies solving a linear equation set to get limits Li like this:

In a matrix form this looks like

where

and thus the solution is

Skipping boring calculations, the reverse matrix
is

This solutions looks huge, but the L vector is calculated in O(N) time:
void calculate_limits(int N, int *g, int *l)
{
int sum;
int i;
if (N == 1) {
l[0] = R;
return;
}
sum = 0;
for (i = 0; i < N; i++)
sum += R - g[i];
for (i = 0; i < N; i++)
l[i] = (sum - (R - g[i]) - (N - 2) * (R - g[i]))/(N - 1);
}
Disadvantages of this approach
This approach has only one disadvantage: O(n) time needed to start a new container.

