Changes between Version 52 and Version 53 of 020513_GEMINI_Demo
- Timestamp:
- 02/05/13 12:00:15 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
020513_GEMINI_Demo
v52 v53 24 24 25 25 26 + configuration (figure) [[BR]] 26 ==== configuration (figure) ==== 27 27 Hussam's slice will be pre-created and look like [[BR]][[Image(gemini.png,border=1)]] 28 28 29 29 30 + summary of demo steps [[BR]] 30 ==== summary of demo steps ==== 31 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 ==== demo Plan====33 ===== Demo Plan ===== 34 34 * A slice will be pre-created. [[BR]] 35 * GN is loaded with a custom image called “GEMINI_GN”[[BR]]36 * All MP Nodes are loaded with a custom image called “GEMINI_MP” [[BR]]35 * GN is loaded with a custom image called “GEMINI_GN”[[BR]] 36 * All MP Nodes are loaded with a custom image called “GEMINI_MP” [[BR]] 37 37 * Show the scripts that comprise the whole instrumentize process[[BR]] 38 38 * Start the Instrumentize Process [[BR]] 39 * Start gdesktop-init.py [[BR]] 40 * Start gdesktop-instrumentize.py [[BR]] 41 42 Executing the demo: Hussam & Ezra 43 44 ==== current interfaces to other entities, and message flows (like “AA-workflow”) ==== 39 * Start gdesktop-init.py [[BR]] 40 * Start gdesktop-instrumentize.py [[BR]] 41 42 '''Executing the demo: Hussam & Ezra''' 43 44 ==== Current interfaces ==== 45 [[Image(Gemini_instrumentize_passive.png)]] [[BR]] 45 46 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]] 46 47 47 ==== features available now (2/5) ====48 ==== Features available now (2/5) ==== 48 49 * All previous Passive data collection functionality still available.[[BR]] 49 50 * Drupal CMS to display passive data collected on the GN available[[BR]] 50 51 * Passive data archive to irods using GSI and proxy certs [[BR]] 51 52 52 ==== features expected to be available by GEC16 (3/19) ====53 ==== Features expected to be available by GEC16 (3/19) ==== 53 54 * Convert Parser API backend to use OMNI inorder to make it compatible with different Control Frameworks and AMs[[BR]] 54 55 * 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]] 55 56 56 ==== issues that need to be resolved before GEC16 (3/19) ====57 ==== Issues that need to be resolved before GEC16 (3/19) ==== 57 58 * Deploy and test the complete merged Active and Passive instrumentation code in the User Workspace and from the GeniDesktop.[[BR]] 58 59