FTS3 backend: pass priority as copyjob param

[nikmagini]

In FTS3, when using the json copyjob format, it should be possible to specify the priority as a job parameter:

http://fts3-docs.web.cern.ch/fts3-docs/fts-rest/docs/bulk.html

{ "files": [...], "params": { "priority": 3 } }

Proposing to use this method to select priority in the FTS3 backend instead of running 'fts-set-priority' when use-json is true.

[alberto-sanchez]

Currently the cli fts-client does not support the "params" option. I already, but it failed. It took me awhile to understand until I found the actual code which parses the json. See:

https://gitlab.cern.ch/fts/fts3/blob/master/src/cli/BulkSubmissionParser.cpp#L76

only one array is expect at the moment with name "Files". Anyway I will look how to use these features.

[nikmagini]

Hi Alberto,

thanks for checking - then we can postpone this feature until FTS3 devs add support for 'params' in the json in the CLI; or until we implement direct submission to the REST API in PhEDEx.

Cheers, Nicolò

[nikmagini]

Hi,

FTS3 devs will add support for 'params' in the CLI, but this will be done after FTS release 3.5:

https://its.cern.ch/jira/browse/FTS-648

When this is done, we can resume work on this ticket.

Cheers N

[nikmagini]

Hi,

the latest versions of the client (3.5.1+) include support for "Params" in the json.

This is also needed to specify other parameters e.g. "ipv6":true

In fact, we might even let the site admins pass arbitrary parameters through the agent config (using a hash config option --copyjob-params )

Cheers N

[bbockelm]

Is there a host-wide FTS config that we could put this in? For example, gfal2 obeys the settings in /etc/gfal2.d: is there something similar for the FTS client?

[nikmagini]

Is there a host-wide FTS config that we could put this in? For example, gfal2 obeys the settings in /etc/gfal2.d: is there something similar for the FTS client?

Not as far as I'm aware.