Project

General

Profile

Feature #23053

Add attributes that are VO and site dependent

Added by Marco Mambelli about 2 months ago. Updated 4 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
08/03/2019
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Description

Sometimes VOs need to specify attributes that are VO specific may be different depending on the site.
This behavior should be discouraged because the VOs should not worry about where they run (besides receiving the resources they need), but some may be difficult to avoid (e.g. a project ID, billing code, ...).

These attributes could be still specified in the client (Frontend) but be a dictionary of values keyed using the entry or entry_set ID (would take precedence the entry, entry_set, the first one encountered if it is a sorted dict? - needs to be specified).
If there is a default value this should be used if the entry is not matching any of the keys, otherwise, the attribute will be undefined on that entry.

Should there be also Factory attributes keyed using the client/group ID?

A possible implementation could add a new attr flag (is_dictionary) and use string dictionaries (key:val, ... , functions are in singularity_lib.sh)
The factory would do the resolution for parameters attributes, an add_config_line equivalent would do the resolution for file transmitted attributes. Probably it should be a different param file, the entry_set name should be known to the glidein.

History

#1 Updated by Marco Mambelli 4 days ago

  • Target version changed from v3_5_2 to v3_5_3


Also available in: Atom PDF