Details
-
Type: Dev Sub-task
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Fix Version/s: Vz7.0-Update-next
-
Component/s: Containers::Userspace
-
Security Level: Public
Description
In order to use project quota for simfs-based Containers, we need modified userspace on the host: quota-tools and e2fsprogs.
Li Xi prepared a patched version of required tools:
http://thread.gmane.org/gmane.linux.kernel.api/14088
Link to tools themselves:
https://github.com/ddn-lixi/project_quota_ext4_utils
So what should be done:
1) we need to decide if we want separate binaries to simfs-based Containers or use patched "fresh" quota-tools and e2fsprogs (from mainstream) for all Containers
The decision is based on the fact what version of tools can be used. If only latest mainstream version of tools can be used - we'll have to have separate binaries for project quota management.
In case there is a version of tools which
a) is used in some popular distrib (and thus we can assume it's tested well)
and
b) patches from the link above are applicable on that version
in this case we can think about using these rather "new" patched tools _instead of_ stock RedHat/CentOS ones.
2) after decision on 1) is made, need to prepare repos for tools (separately for each package) and a spec for it so it can be built.
Li Xi prepared a patched version of required tools:
http://thread.gmane.org/gmane.linux.kernel.api/14088
Link to tools themselves:
https://github.com/ddn-lixi/project_quota_ext4_utils
So what should be done:
1) we need to decide if we want separate binaries to simfs-based Containers or use patched "fresh" quota-tools and e2fsprogs (from mainstream) for all Containers
The decision is based on the fact what version of tools can be used. If only latest mainstream version of tools can be used - we'll have to have separate binaries for project quota management.
In case there is a version of tools which
a) is used in some popular distrib (and thus we can assume it's tested well)
and
b) patches from the link above are applicable on that version
in this case we can think about using these rather "new" patched tools _instead of_ stock RedHat/CentOS ones.
2) after decision on 1) is made, need to prepare repos for tools (separately for each package) and a spec for it so it can be built.