Re: [cpx] Quotas (was Separation of Roles)

[AlpineWeb <news.list@xxxxxxxxxxxxx>]

Hi Ric,

> I don't believe I claimed that in the current CPX the Domain Admin's
> quota is "affected" by its end users, just that perhaps it *should*.

I just quoted you. If you meant "should", then you should have used that
word rather than "affected".


> Please correct me if I'm misunderstanding something here

You have a major mis-conception about CPX and the Domain Admin quota for 
user quota management.

Try looking at it another way:

A Domain Administrator is created and assigned a quota of 1000MBs and
the ability to create 10 end users. The Domain Administrator now has the
ability to create 10 users whose total, combined quotas are
"constrained" to 1000MBs. The end users quotas are not in addition to
the Domain Admins quota but rather constrained by it.

In other words, a Domain Administrator cannot assign (for end users or
otherwise) more total disk space to quotas than its own disk quota.


> I'm guessing in most setups, there is a significant asymmetry between
> the disk resource requirements of "end users" versus Domain Admins.

Once you grasp the Domain Admin quota concept, it should clear
things up.


> Of course, all of this could also be solved if I could push the web
> file space off to one of the end user accounts.  That brings us back
> to separation of roles again.  I would like to be able have a Domain
> Admin account that does nothing but manage permissions, quotas, and
> email mappings for the domain and a "end user" account that handles
> the domain's web file space.  And if I could disable the other Domain
> Admin's privileges (Mail, FTP, File Management, Shell Access) without
> still allowing the ability to the *grant* these privileges to the "end
> user" accounts, then CPX would be a much better match for my use case.

If your Domain Administrator could only "manage permissions, quotas, and
email mappings for the domain" how would end user accounts be created
and deleted, passwords changed, etc.

My hunch is that once you better understand how CPX works in regard to
managing end users, quotas, etc, CPX will make more sense.

You could also submit a request/suggestion to the CPX development team.


Cheers,
Uwe Schneider

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
AlpineWeb Design ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://AlpineWeb.com/
603-356-8797 ~~~~~~~~~~~~~~~~~~~~~~~~~~ http://AlpineWeb.com/helpdesk/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Ricardo Newbery wrote:
> At 11:05 AM -0500 1/28/06, AlpineWeb wrote:
>
> > Hello Ric,
> >
> > You have it backwards. A "Domain Admin" is not "affected" by it's end 
> > users but rather the other way around. If you allocate 1000MBs disk 
> > quota for the Domain Admin then the sum total quota for ALL end users 
> > managed by said Domain Admin would be 1000MBs.
> >
> > HTH's
> >
> > Cheers,
> > Uwe Schneider
>
>
>
>
> I don't believe I claimed that in the current CPX the Domain Admin's 
> quota is "affected" by its end users, just that perhaps it *should*.
>
> Please correct me if I'm misunderstanding something here but the "end 
> users" quota count doesn't include the Domain Admin account which is 
> where the domain's web files reside.  So if the disk quota for the 
> Domain Admin account is *still* 1000 MB after you've allocated 1000 MB 
> to all the "end users" then you've effectively *doubled* the total 
> amount of allocated disk space.
>
> I'm guessing in most setups, there is a significant asymmetry between 
> the disk resource requirements of "end users" versus Domain Admins.
>
> Suppose I need to allocate 1 GB for web file space and 2 mail-only end 
> users.  With the current model, that would be a 500 MB mail quota for 
> each account IN ADDITION to the 1 GB quota for the web file space.
>
> Or conversely, what if I need to setup 200 email accounts with 20 MB 
> quotas?  I would need a Domain Admin with a 4,000 MB quota for a total 
> of 8,000 MB, of which a large portion would be 
> overallocated/underutilized web file space -- assuming I've actually got 
> 8 GB of real disk space.
>
> Of course, all of this could also be solved if I could push the web file 
> space off to one of the end user accounts.  That brings us back to 
> separation of roles again.  I would like to be able have a Domain Admin 
> account that does nothing but manage permissions, quotas, and email 
> mappings for the domain and a "end user" account that handles the 
> domain's web file space.  And if I could disable the other Domain 
> Admin's privileges (Mail, FTP, File Management, Shell Access) without 
> still allowing the ability to the *grant* these privileges to the "end 
> user" accounts, then CPX would be a much better match for my use case.
>
> Ric
>
> ======================================================================
> This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
> Before posting a question, please search the archives (see above URL).

======================================================================
This is <cpx@xxxxxxxxxxxxx>      <http://www.groupmail.org/lists/cpx/>
Before posting a question, please search the archives (see above URL).