On Sun, Aug 08, 2004 at 04:27:38PM +0100 or thereabouts, Alessandra Forti wrote:
> >What exactly do you want to achieve?
>
> I just wanted to publish a local queue that is not available to all the
> VOs, but only to local users independently from the VO they belong which
> has a higher precedence than any other VO queue. If the job doesn't look
> like as coming from the UI but only from the RB certainly this is useless.
> Restricting to the local users DNs can become cumbersome.
Hi Alessandra
There are a couple of ways I can think off, run your own VO server
with your local users in. Things like permissions becomes a bit of a
headache.
Andy was looking at a mechanism a while back for setting up a local VO.
In fact if you have the mapping of DN to local users from this then
you can just grant more priority to these named users with a scheduler
that can do more such as maui.
From your previous answer I am assuming you want you local user to
grid submit rather than qsub, that is good idea since then they make
use of the consistent interface.
Steve
>
> thanks
>
> cheers
> alessandra
>
>
> On Fri, 6 Aug 2004, Burke, S (Stephen) wrote:
>
> >Testbed Support for GridPP member institutes
> >>[mailto:[log in to unmask]] On Behalf Of Alessandra Forti said:
> >>Can the value of GlueCEAccessControlBaseRule be *.hep.man.ac.uk or
> >>something similar?
> >
> >Not usefully. What exactly do you want to achieve? The jobs will always
> >come
> >from the RB, how could you tell which UI they came from? What you could do
> >is restrict access to the certificates of local users. It used to be the
> >case that the AccessControlBaseRule was a list of explicit DNs. I would
> >think that support for that is still there, although I don't know, so you
> >could try that.
> >
> >Stephen
> >
--
Steve Traylen
[log in to unmask]
http://www.gridpp.ac.uk/
|