Changes between Version 29 and Version 30 of 020513_GEMINI_Demo
- Timestamp:
- 02/04/13 11:20:16 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
020513_GEMINI_Demo
v29 v30 29 29 30 30 + summary of demo steps [[BR]] 31 There will be two version of the demo due to state of the code being worked on. Hussam's version of the instrumentize will have all code related to active measurement installation, configuration disabled, where as Ezra's version of the same instrumentation script will have the active measurements with the AA Stuff enabled. 31 There will be two version of the demo due to state of the code being worked on. Hussam's version of the instrumentize will have all code related to active measurement installation, configuration disabled, where as Ezra's version of the same instrumentation script will have the active measurements with the AA Stuff enabled.[[BR]] 32 32 33 33 + current interfaces to other entities, and message flows (like “AA-workflow”) [[BR]] 34 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 [ [File(ParserAPI.pdf)]].34 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]] 35 35 36 36 + features available now (2/5) [[BR]] 37 * All previous Passive data collection functionality still available. 38 * Drupal CMS to display passive data collected on the GN available 39 * Passive data archive to irods using GSI and proxy certs 37 * All previous Passive data collection functionality still available.[[BR]] 38 * Drupal CMS to display passive data collected on the GN available[[BR]] 39 * Passive data archive to irods using GSI and proxy certs [[BR]] 40 40 41 41 + features expected to be available by GEC16 (3/19) [[BR]] 42 * Convert Parser API backend to use OMNI inorder to make it compatible with different Control Frameworks and AMs 43 * Add new Parser API call to allow the parser to store the AM list provided by the user. This is required since OMNI requires that user provide this list or else it polls every AM in its list obtained from the Clearing House, which would slow down the parser. 42 * Convert Parser API backend to use OMNI inorder to make it compatible with different Control Frameworks and AMs[[BR]] 43 * Add new Parser API call to allow the parser to store the AM list provided by the user. This is required since OMNI requires that user provide this list or else it polls every AM in its list obtained from the Clearing House, which would slow down the parser.[[BR]] 44 44 45 45 + issues that need to be resolved before GEC16 (3/19) [[BR]] 46 * Deploy and test the complete merged Active and Passive instrumentation code in the User Workspace and from the GeniDesktop. 46 * Deploy and test the complete merged Active and Passive instrumentation code in the User Workspace and from the GeniDesktop.[[BR]] 47 47 48 48 … … 110 110 111 111 + current interfaces to other entities, and message flows (like “AA-workflow”) [[BR]] 112 Uses proxy certs generated during the instr mentize process and copied onto the GN Node.112 Uses proxy certs generated during the instrumentize process and copied onto the GN Node. [[BR]] 113 113 114 114 + features available now (2/5) [[BR]] 115 * Current version on archives passive measurement data and metadata. 116 * There is no web interface for the user to run this archive process117 * I am not sure if the web interface supports GSI authentication to view the data and metadata. If this feature is not available, then it would be a really huge task for the user to view the data and metadata since the icommands are complicated form a user's viewpoint.118 * Irods account creation is outside the scope of the GEMINI Instrumentize process. The user is expected to have this account before hand. 115 * Current version on archives passive measurement data and metadata.[[BR]] 116 * There is no web-interface for the user to run this archive process[[BR]] 117 * I am not sure if the web-interface supports GSI authentication to view the data and metadata. If this feature is not available, then it would be a really huge task for the user to view the data and metadata since the icommands are complicated form a user's viewpoint.[[BR]] 118 * Irods account creation is outside the scope of the GEMINI Instrumentize process. The user is expected to have this account before hand.[[BR]] 119 119 120 120 + features expected to be available by GEC16 (3/19) [[BR]] 121 * Web-interface to initiate the archive process [[BR]] 121 122 122 123 + issues that need to be resolved before GEC16 (3/19) [[BR]] 124 * If there are plans for archiving Active measurement data, then that itself is a huge amount of work.[[BR]] 123 125 124 126 === Features needed by GEC16 (3/19) ===