Make jobsub server compatible with FERRY 2.0
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>,
As per Bruno, we need to do two things to make jobsub compatible with FERRY:
- Grab our output from the ferry_output key in the response JSON, rather than just the top level
- 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.
#1 Updated by Shreyas Bhat 3 months 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.
#3 Updated by Shreyas Bhat 3 months 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:
fqan, username, commonname
fqan, username, fullname
fqan, mapped_uname, unitname
fqan, username, unitname
I made those corrections, and tested on my dev server. All looks good. Will open a review request for Dennis.