[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-devel] Condor 7.6.1 timeline?
- Date: Sun, 22 May 2011 08:15:17 -0700
- From: Erik Erlandson <eerlands@xxxxxxxxxx>
- Subject: Re: [Condor-devel] Condor 7.6.1 timeline?
On Sat, 2011-05-21 at 14:04 -0500, Brian Bockelman wrote:
> How do subgroups take precedence over parents? The part of our
> solution I'm least happy with is the handling of the US folks as a
> subgroup of global CMS.
Consider something like:
GROUP_QUOTA_cms_users = 500
GROUP_QUOTA_DYNAMIC_cms_users.us = 1.0
GROUP_QUOTA_DYNAMIC_cms_users.us.neb = 1.0
GROUP_ACCEPT_SURPLUS = TRUE
With that configuration, "cms_users.us.neb" is guaranteed all 500 slots
(if asked for) and may be given all the surplus, up to whatever
resources are requested.
However, if "cms_users.us.neb" needs less than all 500, and/or less than
all the surplus from other groups, the remainder can be used by
"cms_users.us", and likewise "cms_users" if any is left over after that.
An alternative configuration that guarantees no group will absolutely
starve would be:
GROUP_QUOTA_cms_users = 500
GROUP_QUOTA_DYNAMIC_cms_users.us = 0.95
GROUP_QUOTA_DYNAMIC_cms_users.us.neb = 0.95
GROUP_ACCEPT_SURPLUS = TRUE
That reserves 500(0.05) slots for cms_users, and 500(0.95)(0.05) slots
for cms_users.us, reserving 500(0.95)(0.95) slots for cms_users.us.neb
Or something similar with static quotas:
GROUP_QUOTA_cms_users = 500
GROUP_QUOTA_cms_users.us = 490
GROUP_QUOTA_cms_users.us.neb = 480
GROUP_ACCEPT_SURPLUS = TRUE