Project

General

Profile

Feature #7886

Support jobsub client actions without any role

Added by Parag Mhashilkar about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Parag Mhashilkar
Category:
-
Target version:
Start date:
02/17/2015
Due date:
% Done:

0%

Estimated time:
Stakeholders:

Operations

Duration:

Description

Right now all the actions some how assume that default role is Analysis. Default role should be made configurable and if no role is specified role is either None or configured default role.

TASK0044410/RITM0115369

History

#1 Updated by Parag Mhashilkar about 6 years ago

  • Target version changed from v1.2 to v1.1.1

#2 Updated by Parag Mhashilkar about 6 years ago

  • Assignee changed from Parag Mhashilkar to Dennis Box

#3 Updated by Dennis Box about 6 years ago

  • Status changed from New to Feedback
  • Assignee changed from Dennis Box to Parag Mhashilkar

#4 Updated by Dennis Box about 6 years ago

  • Status changed from Feedback to Resolved

merged after review and testing

#5 Updated by Dennis Box about 6 years ago

Notes on testing:

1)set default_voms_role = Analysis in default section of jobsub.ini
verified that regression test ran same as v1.1.0 submitting with --role=Analysis and --role=Production had same effect as before

2) commented out default_voms_role
Verified in the server logs that generated proxies used by jobs had role=None
submitting with --role=Analysis and --role=Production had same effect as before

3) set default_voms_role = Production in default section of jobsub.ini
Verified in the server logs that generated proxies used by jobs had role=Production and jobs ran as 'novapro' or 'lbnepro' by default. --role=Analysis in jobsub_submit had expected result

4) tested default_voms_role in both 'default' and 'nova' sections.
verified that nova default was different than other experiments default.

#6 Updated by Parag Mhashilkar almost 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF