Project

General

Profile

Feature #20881

set X509_USER_PROXY auomatically for production jobs

Added by Marc Mengel almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
09/19/2018
Due date:
% Done:

100%

Estimated time:
Scope:
Internal
Experiment:
-
Stakeholders:
Duration:

Description

This would reduce errors, and make login-setup settings simpler.
We could store the path template in the experiment, and default it
to "/opt/%(experiment)spro/%(experiment)spro.Production.proxy"
which would be right as far as I know for everyone, but also be modifiable if needed.

This from RITM0728048.

Associated revisions

Revision de5acb72 (diff)
Added by Marc Mengel over 1 year ago

bookkeeping, change for #20881

History

#1 Updated by Stephen White over 1 year ago

What about analysis jobs? Can we fix this once for both?

#2 Updated by Marc Mengel over 1 year ago

It depends what grid security and FIFE folks think we should do about analysis user submissions.
If we have a standard way to authenticate analysis users, clearly we should set that automatically as well; the stumbling block is knowing what that is :-).

#3 Updated by Stephen White over 1 year ago

  • Assignee set to Marc Mengel

also at the same time, poms should setup the products included, see below

export X509_USER_PROXY=/opt/exopro/iexpro.Production.proxy; setup fife_utils v3_2_4; setup poms_client; setup poms_jobsub_wrapper

#4 Updated by Marc Mengel over 1 year ago

  • Status changed from New to Resolved

Added. de5acb7

#5 Updated by Marc Mengel over 1 year ago

  • % Done changed from 0 to 100

#6 Updated by Stephen White over 1 year ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF