1 / 35

ER-flow is supported by the FP7 Capacities Programme under contract No. RI-261585

Building an E uropean R esearch Community through Interoperable Work flow s and Data ER-flow project Gabor Terstyanszky, ER-flow Project Coordinator 05 July 2013. ER-flow is supported by the FP7 Capacities Programme under contract No. RI-261585. ER-flow Project. Partners:.

mandek
Download Presentation

ER-flow is supported by the FP7 Capacities Programme under contract No. RI-261585

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. Building an European Research Community through Interoperable Workflows and DataER-flow projectGabor Terstyanszky, ER-flow Project Coordinator05 July 2013 ER-flow is supported by the FP7 Capacities Programme under contract No. RI-261585

  2. ER-flow Project Partners: Technology providers: CNRS, EGI.eu, MTA-SZTAKI, UoW Research Communities: Astro-Physics INAF Computational Chemistry LMU + TUD Helio-Physics TCD + UCL Life Science AMC Duration: September 2012 – August 2014 2

  3. Project Aim and Services Aim: • To provide a simulation platform for research communities to enable seamless execution of workflows of different workflow systems through workflow interoperability • To investigate data interoperability issues in the workflow domain and propose solutions Services: • To support the whole workflow lifecycle: editing, uploading, browsing downloading and executing workflows • To provide coarse-grained workflow interoperability solution • To provide GUIs to manage workflows Key actors: • researchers workflow engine developers workflow developers

  4. ER-flow & Research Communities Supported research communities: • Astro-Physics 14 workflows • Computational Chemistry 20 workflows • Helio-Physics 14 workflows • Life Science 20 workflows Supported research communities: • number of users: minimum: 250 • Number of executed workflow: 3000 Further research communities: • at least four more research communities • Hydrometeorology, Seizmology • ??? 4

  5. Coarse-Grained Interoperability: CGI concept workflow configuration workflow engine configuration concrete workflow abstract workflow abstract workflowengine concrete workflowengine workflow engine workflow engine formal description workflow formal description

  6. Coarse-Grained Interoperability: submitting non-native workflow Workflow of Workflow Engine B Workflow Engine A Submission Service Workflow Engine B Workflow Engine A WF DCI • non-native workflow: WF • - non-native workflows are black boxes which are managed as legacy code applications 6 6

  7. Coarse-Grained Interoperability: meta-workflow submission Workflows of Workflow Engine A Workflow of Workflow Engine B J1 WF2 DCI WF3 Workflow Engine A WF4 Submission Service Workflow Engine B • native workflows: J1, J3 and WF2 • non-native workflows: WF4 • - black boxes which are managed as legacy code applications Workflow Repository

  8. ER-flow Development Environment: SHIWA Simulation Platform (SSP) SHIWA Repository DCIs WF1 WFn SHIWA Science Gateway Unicore DCI ARC DCI SHIWA Portal GEMLCA admin gLite DCI Globus DCI GEMLCA Repository WS-PGRADE Workflow editor WF1 WFm ASKALON WE Galaxy WE Triana WE WE1 WEp Taverna WE WS-PGRADE Workflow engine GWES WE Kepler WE GEMLCA with GIB Proxy Server Pegasus WE MOTEUR WE GEMLCA Service SHIWA Proxy Server ProActive WE PGRADE WE Workflow Engines

  9. SHIWA Portal: Editing Workflow 9 9

  10. SHIWA Portal: Configuring Workflow 10

  11. SHIWA Portal: Executing Workflow 11

  12. Exporting Workflow (1):Select the SHIWA Repository 12

  13. Exporting Workflow (2):Authentication 13

  14. Exporting Workflow (3):Display Workflow Data and Submit it 14

  15. Importing Workflow (1):Select the SHIWA Repository 15

  16. Importing Workflow (2):Select the Workflow and Import it 16

  17. Importing Taverna Workflows 17

  18. Robot Certificate Management

  19. Workflow Execution Statistics

  20. SHIWA Repository: Table View 20 20

  21. SHIWA Repository: Table View

  22. SHIWA Repository: Browse View 22 22

  23. SHIWA Repository: Browse View

  24. CGI Developer Scenario: Specifying Workflow Engine SHIWA Repository step 1specify WE data WF1 WFn SHIWA Science Gateway SHIWA Portal workflow engine developer GEMLCA admin GEMLCA Repository WS-PGRADE Workflow editor WF1 WFm step 2upload WE binary, dependencies WE1 WEp step 3deploy WE WS-PGRADE Workflow engine Proxy Server GEMLCA with GIB SHIWA Proxy Server GEMLCA Service 24

  25. CGI Developer Scenario: Specifying Non-Native Workflows SHIWA Repository WF1 WFn step 1specify WF data SHIWA Science Gateway step 3deploy WF workflow developer SHIWA Portal WF1 WFm step 2upload WF WE1 WEp WS-PGRADE Workflow editor Proxy Server GEMLCA Repository GEMLCA with GIB SHIWA Proxy Server WS-PGRADE Workflow engine GEMLCA Service 25 25

  26. CGI User Scenario: PGRADE as Native WE DCIs Unicore DCI gLite DCI ARC DCI Globus DCI SHIWA Science Gateway SHIWA Repository ASKALON WE Galaxy WE WF1 WFn Triana WE Taverna WE GWES WE step 1search WF Kepler WE step 3retrieve WF data GEMLCA Repository Pegasus WE SHIWA Portal MOTEUR WE WF1 WFm step 2 edit WF WE1 WEp ProActive WE PGRADE WE WS-PGRADE Workflow editor step 5retrieve WF WE + WF Workflow Engines WF list e-scientists WS-PGRADE Workflow engine GEMLCA with GIB step 7 run WF step 6retrieve proxy GEMLCA Service step 4submit WF Proxy Server SHIWA Proxy Server

  27. CGI User Scenario: MOTEUR as Native WE DCIs SHIWA Science Gateway Unicore DCI gLite DCI ARC DCI Globus DCI step 1search WF SHIWA Repository ASKALON WE Galaxy WE Triana WE Taverna WE WE + WF GWES WE Kepler WE user step 5retrieve proxy step 4retrieve WF step 6 run WF Pegasus WE MOTEUR WE Proxy Server Submission service WF1 WFm ProActive WE PGRADE WE WE1 WEn SHIWA Proxy Server GEMLCA Service step 2 edit WF Workflow Engines MOTEUR Workflow editor step 3submit WF MOTEURWorkflow Engine GEMLCA Client GEMLCA UI 27

  28. SSP: Execution Infrastructure 28

  29. ER-flow Research Communities

  30. End User View 30 30

  31. End User View 31

  32. End User View 32

  33. End User View 33

  34. User Tailored View (ASM) 34

  35. User Tailored View (ASM) 35

More Related