Hi,
the following patches are a third stab at filesystem limits for
containers. With these patches space limits in openvz containers are
printed in the domain config as:
<filesystem type='template' accessmode='passthrough'>
<source name='debian'/>
<target dir='/'/>
<space_hard_limit unit="MiB">1153024</space_hard_limit>
<space_soft_limit unit="MiB">1048576</space_soft_limit>
</filesystem>
The can also be set from the domain xml. I left out inode limits for now
since the unit "Bytes" wouldn't fit there well and I didnt' get around
to update the unit parsing code yet. Changes since last time:
* Add the version we introduced this feature to formatdomain.html.in
* Move the patch that makes virDomainParseMemory use
virDomainParseScaledValue to the front of the queue
* Fix safe_node -> save_node typo
* Make output format consistent with what's used in storage_conf.c
('bytes' not 'B')
* openvz: Check for overflow when parsing DISKSPACE out of the container
config
* openvz: Fix logic that only sets the hard limit when no soft limit is
given and rejects config that only specify a soft limit
Cheers,
-- Guido
Guido Günther (4):
Introduce virDomainParseScaledValue
Introduce filesystem limits to virDomainFSDef
openvz: support file system quota reporting
openvz: add quota argument when creating container
docs/formatdomain.html.in | 14 +++
docs/schemas/domaincommon.rng | 12 +++
src/conf/domain_conf.c | 124 ++++++++++++++++-------
src/conf/domain_conf.h | 2 +
src/openvz/openvz_conf.c | 24 +++++
src/openvz/openvz_driver.c | 58 ++++++++++-
tests/domainschemadata/domain-openvz-simple.xml | 2 +
7 files changed, 199 insertions(+), 37 deletions(-)
--
1.7.10
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list