| | 1 | === Data to be archived === |
| | 2 | |
| | 3 | === Archive Service === |
| | 4 | |
| | 5 | === Steps for accessing iRODS from OML via GSI: === |
| | 6 | |
| | 7 | Prerequisites: |
| | 8 | * iRODS server is built with GSI |
| | 9 | * iRODS client on the OML server is built with GSI |
| | 10 | * Slice owner has an account on the iRODS server |
| | 11 | * Slice owner's account has aua from GENI certificate configured |
| | 12 | |
| | 13 | Prior to setting up the slice, the user must contact the iRODS administrator (via GEMINI mailing list?) |
| | 14 | and provide their username and GENI certificate identity (give the openssl command). An account will |
| | 15 | be established for them in the "GIMI zone" with an aua matching the provided certificate identity. |
| | 16 | |
| | 17 | 1. Set-up tool will generate a proxy certificate from slice owner's GENI certificate. |
| | 18 | 2. Set-up tool will place proxy pem file in appropriate location on the OML server (home directory of user executing the archive service) |
| | 19 | 3. Set-up tool will configure irodsEnv for the user executing the archive service. |
| | 20 | a. host/port - set to the KY iRODS server |
| | 21 | b. zone/resource - a predetermined "GEMINI zone" |
| | 22 | c. username - provided by the user during instrumentize - this MUST match the iRODS account |
| | 23 | d. irods directories - determined from username and zone (e.g. /geminiZone/home/username) |
| | 24 | |
| | 25 | |
| | 26 | === iRODS servers with GSI === |
| | 27 | |
| | 28 | What iRODS server will be used? Is it running 3.2 with GSI? |
| | 29 | |
| | 30 | |
