| 58 | | [[Image(Gemini_instrumentize_passive.png, 60%)]] [[BR]] |
| 59 | | |
| 60 | | Both version of the instrumentation code will talk to the GENIDESKTOP Parser Service to obtain User information, Slice/Slice Credential Information and Manifest information thus making the instrumentation process somewhat independent of the Control Frameworks. NO communication between AMs/SAs and the User's instrumentation code is required since this now the work of the Parser service. A Detailed list of the Parser API and its return values is provided in this document [attachment:ParserAPI.pdf]. [[BR]] |
| | 58 | [[Image(Gemini_instrumentize_passive.png, 80%)]] [[BR]] |
| | 59 | |
| | 60 | * Instrumentize script runs in Use Workspace [[BR]] |
| | 61 | |
| | 62 | * Both version of the instrumentation code will talk to the GENIDESKTOP Parser Service to obtain User information, Slice/Slice Credential Information and Manifest information thus making the instrumentation process somewhat independent of the Control Frameworks. |
| | 63 | |
| | 64 | * NO communication between AMs/SAs and the User's instrumentation code is required since this now the work of the Parser service. |
| | 65 | |
| | 66 | * A Detailed list of the Parser API and its return values is provided in this document [attachment:ParserAPI.pdf]. [[BR]] |
| | 67 | |
| | 68 | Issue: where does Parser service run? in User Workspace, where it has access to certs/credentials? |
| | 69 | |
| | 70 | * But then, how can GN get access to Parser service, since the UW is not necessarily reachable? |
| | 71 | |
| | 72 | * Option: Parser in UW could push info to GN |
