Project

General

Profile

Feature #23242

Make jobsub server compatible with FERRY 2.0

Added by Shreyas Bhat about 1 month ago. Updated about 1 month ago.

Status:
Feedback
Priority:
High
Assignee:
Category:
JobSub Server RPM
Target version:
-
Start date:
09/09/2019
Due date:
% Done:

90%

Estimated time:
Stakeholders:
Duration:

Description

The FERRY developers just told us that they're hoping to have all services transitioned to FERRY 2.0 by October 1. This means we'll need to make a change to how jobsub calls FERRY. The new output from FERRY will look like:

{
"ferry_output": <what we care about, type changes based on API>,
"ferry_status": "success|failure",
"ferry_error": [list_of_errors],
}

As per Bruno, we need to do two things to make jobsub compatible with FERRY:

  1. Grab our output from the ferry_output key in the response JSON, rather than just the top level
  2. Check ferry_error to see if it's 0-length or not. 0-length means there was no error.

We can use ferrydev.fnal.gov:8445 for testing, and eventually, we can use ferry.fnal.gov:8445.


Related issues

Blocked by JobSub - Necessary Maintenance #23249: Review request [commit:61050b584f797bab2ddabc748ca6657310f2a8b6: Forgot to update mapped_uname here for FERRY 2.0]New09/10/2019

History

#1 Updated by Shreyas Bhat about 1 month ago

I've started work on this.

Use this as reference. https://cdcvs.fnal.gov/redmine/attachments/55011/Ferry%202.0.pdf

Note: we need to change mapped_uname in invert_vo_role_uid_map to "username". There may be other such changes.

#2 Updated by Shreyas Bhat about 1 month ago

Test all APIs for names, check against authutils.py functions. We may have some changed names, unfortunately.

#3 Updated by Shreyas Bhat about 1 month ago

  • % Done changed from 0 to 90
  • Status changed from New to Feedback

This is what I mapped out were the differences from FERRY 1.0 to FERRY 2.0:

getAffiliationMembersRoles CHANGED

1.0:
fqan, username, commonname
2.0:
fqan, username, fullname

getGridMapFile CHANGED
1.0:
userdn, mapped_uname
2.0:
dn, username

getVORoleMapFile CHANGED
1.0:
fqan, mapped_uname, unitname
2.0:
fqan, username, unitname

I made those corrections, and tested on my dev server. All looks good. Will open a review request for Dennis.

#4 Updated by Shreyas Bhat about 1 month ago

Note: When this is released, we'll have to have an accompanying change in jobsub.ini to point at the new FERRY server. (ferry.fnal.gov:8445 is what's planned)

#5 Updated by Shreyas Bhat about 1 month ago

  • Related to Necessary Maintenance #23249: Review request [commit:61050b584f797bab2ddabc748ca6657310f2a8b6: Forgot to update mapped_uname here for FERRY 2.0] added

#6 Updated by Shreyas Bhat about 1 month ago

  • Related to deleted (Necessary Maintenance #23249: Review request [commit:61050b584f797bab2ddabc748ca6657310f2a8b6: Forgot to update mapped_uname here for FERRY 2.0])

#7 Updated by Shreyas Bhat about 1 month ago

  • Blocked by Necessary Maintenance #23249: Review request [commit:61050b584f797bab2ddabc748ca6657310f2a8b6: Forgot to update mapped_uname here for FERRY 2.0] added


Also available in: Atom PDF