Hi,
In preparation for upcoming production I`m exercising the system at full
scale. This time around there is a lot more unofficial production
activity, and I`m wondering how Atlas can enforce the intra-VO fair-share.
For example, we might want 90% of the Atlas resources to be for official
production. In this case that means the user mapped from
/C=CA/O=Grid/OU=westgrid.ca/CN=Rodney Walker
should get 90% of the Atlas share.
Currently there is no way to express Atlas policy and no way to enforce
it, and I`m looking for a short term solution. My feeling is that this can
only be enforced at the site level, e.g. in the Atlas group part of
the Maui config file.
The long promised voms will be able to say this is a production user, but
what next? The 'what next' will be the same whether we have voms or you
just believe me that Rodney Walker is the only production user(for this
test).
So I`m thinking looking up the user mappings and adjusting the fair-share
of atlasXXX - periodically and perhaps looking up atlas policy on some web
page. The mechanism is not so tough, but I think we`ll need it for
upcoming productions - it`s probably sufficient if a few big sites do
something so I`m not proposing on-the-fly middleware development for all.
Ideas?
Right now I`ve 1200 running with 1800 queued, where the number queued per
site is vaguely proportional to the number of cpus. So if you`re site has
Atlas 10.0.1, LCG2.6.0, ram>=600MB and no jobs then let me know. FZK has only
1 running job and 80 queued which looks fishy.
Cheers,
Rod.
--
Rod Walker +1 6042913051
|