Well, one first step has been done already ;)
lcgwms02.gridpp.rl.ac.uk has been configured few weeks ago to allow 'pheno' jobs. David Winn has tried it with some success, but lcgwms03 is still pheno's preferred WMS for submissions. I would like to enforce 'pheno' to use only lcgwms02, but not sure how pheno submissions work: is the Information System used or the WMS hostname is manually entered by pheno users?
(Both) David, any idea? Should I reconfigure lcgwms03 to stop accepting phenol jobs?
I know this is not the ideal solution to this voms proxy issue, but I want also to see if the problem relies indeed on lcgwms03 or elsewhere.
Cheers,
Catalin
> -----Original Message-----
> From: Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of David Grellscheid
> Sent: 24 November 2011 14:19
> To: [log in to unmask]
> Subject: Re: long term *voms* proxies with myproxy
>
> On 24/11/11 14:07, Jeremy Coles wrote:
> > Reversely our funding and focus is on provision of resources and =
> > services for the LHC VOs
>
> Given that all of the Pheno jobs are done for the LHC experiments (just
> not any given one in particular), maybe we should get Pheno
> reclassified
> into that category?
>
> I'm very grateful for everybody's help so far!
>
> David
|