From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: separate project quota from group quota (questions, design issues)
Date: Sat, 4 Sep 2010 19:13:49 +0200 [thread overview]
Message-ID: <201009041913.49849@zmi.at> (raw)
In-Reply-To: <201009041000.55878.arekm@maven.pl>
[-- Attachment #1.1: Type: Text/Plain, Size: 2411 bytes --]
On Samstag, 4. September 2010 Arkadiusz Miskiewicz wrote:
> My goal is to be able to use user, group and project quota at the
> same time. Example usage is a web hosting company which gives some
> space for customer (group quota), customer splits it into accounts
> (user quota) and then each account can have multiple vhosts with own
> quota (project quota).
Nice idea. I'd also like that, but also mixed:
userdir1 -> user quota
userdir2
prjdir1 -> project quota
prjdir2
groupdir1 -> group quota for a group of users
groupdir2 -> for a group of projects
From what you write, I'm sure you can't mix groups with users and
projects, instead it needs to be defined at mount time. It would be very
good if that can be mixed at the same time.
I'd like to say users1-5 can have 500G each, together 2T max. And
projects can have 2T each, but project1+2 together max. 2T. users6-9 can
have 100G each, together 100G max. Currently I defined everything as a
project, and manually check quotas for groups of projects if they cross
the "group max" border.
But I'd also be very interested in what you write above - it would be a
very welcome expansion of quotas which seems good. Just a question for
setup: We use all dirs side-by-side like
domain1
domain2
|- prj1
|- prj2
domain3
Now customer1 can have domain1 and domain2, customer2 has domain3. prj1
and prj2 can have prjquota. Am I right that this is possible with your
approach? Seems like, and I just want to ask to be sure I understand you
correctly.
Just how would you account that? Say each customer gets 20G, each domain
20G, projects 10G each. When above customer1 has 12G in domain1, he has
left 8G for domain2. Are projects also limited to 8G in sum, or is their
10G limit the one that's valid? If prj1 has 5G, is the 8G-5G=3G what's
available for domain2, or are projects completely separate?
I believe there are lots of variations and some people would like to
have it accounted, some not. Can this ever be solved?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Aktuelles Radiointerview! ******
http://www.it-podcast.at/aktuelle-sendung.html
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-04 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 8:00 separate project quota from group quota (questions, design issues) Arkadiusz Miskiewicz
2010-09-04 17:13 ` Michael Monnerie [this message]
2010-09-04 23:30 ` Christoph Hellwig
2010-09-05 17:24 ` Arkadiusz Miskiewicz
2010-09-06 1:12 ` Dave Chinner
2010-09-06 6:28 ` Arkadiusz Miskiewicz
2010-09-06 1:16 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201009041913.49849@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox