1 / 13

TCD and SCI-BUS

TCD and SCI-BUS. Gabriele Pierantoni TCD London – 07.06.11. Content. TCD’s past experience with portals Plans for WS- Pgrade and SCI-BUS Integration with HELIO to build a portal for the Heliophysics community

laddie
Download Presentation

TCD and SCI-BUS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TCD and SCI-BUS Gabriele Pierantoni TCD London – 07.06.11

  2. Content • TCD’s past experience with portals • Plans for WS-Pgrade and SCI-BUS • Integration with HELIO to build a portal for the Heliophysics community • Use WS-Pgrade as the standard user interface to Grid-Ireland’s computational and storage facility.

  3. TCD and portals • Migrating Desktop (2003-2008) • CrossGrid and Grid-Ireland sites • Ganga and Diane (2008-now) • Used to test jobs for the Costas’ arrays. • Genius (2004) • Used with EDG middleware • P-Grade • Deployment with Quattor profiles • GENE-VO applications developed in P-Grade

  4. HELIO - Introduction HELIO is designed to help the scientist in: finding, retrieving and analyzing data regarding the sun, its related phenomena and their effects on: the Earth, and, the other planets of the Solar System. HELIO ???

  5. Technological Challenge Different User’s Profiles • Data and Metadata • from the various instruments are: • Dispersed • Non completely standardized • There is a complex feedback between data and metadata. HELIO • Codes and Computational facilities are: • Dispersed • Non completely standardized

  6. Different users HELIO Access Layer + HELIO API + Community Interaction Service Users that do not possess a Grid Certificate BUT are willing to login to the HELIO portal Users that do not possess a Grid Certificate AND are NOT willing to login to the HELIO portal Users that possess a Grid Certificate Prefer to use IDL code Prefer to use HELIO Portal Prefer to write workflows Security

  7. Different Resources Low Security High Security Authentication Authentication Authorization Simple User Profile Security

  8. HELIO Architecture (Abstract) HELIO Service Resources Access Layer HELIO API HELIO Service Resources HELIO Service Resources • Connects to services independently • Use them in a workflow • Use a GUI • IDL, Java • Decoupling layer • Hides unnecessary Information • Data & Metadata • Storage • Computation • Existing Code • Security • Web Service • Based

  9. The Access Layer and API Workflow Engine (Desktop) Workflow Engine (Server) Service I API HFE Standalone GUI

  10. Overall Architecture

  11. How to merge HELIO and SCI-BUS ? ?

  12. Interesting areas • User access: • Port the Helio Front End into WS-Pgrade ? • How to give access to IDL-Oriented users ? • Resources access: • How to merge the storage and processing services into SCI-BUS ? • How to merge the HELIO security model into SCI-BUS ? • General architecture issues: • How to merge the HELIO API ? • How to merge the other HELIO services ?

  13. WS-PGrade as Grid Ireland User Interface • Move Grid Ireland users to WS-Pgrade. • How to support the users that still wand a text-based approach ?

More Related