Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Kostas Georgiou said:
> I am sorry but I fail to see how a pilot job will be able to magically
> find free slots if everything is in use. Pilot jobs or not you aren't
> going to run until a job finishes is free.
If there are tens of thousands of job slots the time to wait for one to
be free is short even if individual jobs are long.
> If a project wants to have it's own priorities they can have their own
> RB that implements this functionality.
As things stand (LCG CE) the RBs can't affect priorities within a site,
e.g. to decide that a given job should be promoted to the front of the
queue. The new CREAM CE may be able to do more, I'm not sure exactly
what it allows. It also supports a pull model, pulling from the CE
rather than the WNs, so you don't have to build up queues at the sites.
However, we have no experience with it yet as it hasn't been released.
> > The transfer, storage and type of proxies is one of the reasons why
a
> > review of the multi-user pilot job frameworks are necessary and it
is
> > one of things that will be checked.
>
> And what happens when it's found that it can not be done in a
> secure way?
> Are we going to scratch the glexec idea?
There is no fundamental reason why it can't be secure, after all the
current job submission system already stores and distributes proxies.
However, each framework is supposed to demonstrate that it is secure in
practice, and complies with the security policies, so if that fails it
presumably won't be allowed.
Stephen
|