Project

General

Profile

Feature #22733

Pull Jobsub group and global superusers from FERRY

Added by Shreyas Bhat 5 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
JobSub Server RPM
Target version:
-
Start date:
06/13/2019
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Stakeholders:
Duration:

Description

FERRY folks have told us that it (and the SNOW workflows) are nearly ready for services to use the APIs to pull superusers from there. Once the blocking tickets (to be linked) are finished, use the FERRY API to pull jobsub superusers (called BatchSuperusers in FERRY-speak) for experiments.

The API call will look something like this for an experiment:
https://ferry.fnal.gov:8443/getGroupMembers?groupname=nova&grouptype=BatchSuperusers

And like this for the global (one of the linked tickets is to change "global" in the URL to "_global"):

https://ferry.fnal.gov:8443/getGroupMembers?groupname=nova&grouptype=BatchSuperusers

In addition, before calling this done, make sure to document the proper procedure to add superusers in the jobsub wiki (subtask linked):


Subtasks

Feature #22734: Document changes to jobsub superusersNew

History

#2 Updated by Shreyas Bhat 5 months ago

Global superuser value changed to groupname=_global in FERRY

#4 Updated by Shreyas Bhat 3 months ago

Linked the blocking issue from FERRY - there's no point in making this change when the API output will change. We'll just do this after FERRY's standardized its output.

#5 Updated by Shreyas Bhat 2 months ago

Note that the API output from FERRY will change:

Make sure we're looking at the json["ferry_output"]. API structure is now:

{
"ferry_output": {stuff},
"ferry_status": "success|failure",
"ferry_error": [list of errors]
}

Can use ferrydev.fnal.gov:8445 to test (normal is :8443)

#6 Updated by Shreyas Bhat 2 months ago

Another note from Bruno: Check ferry_error to make sure we actually successfully got the info



Also available in: Atom PDF