1. 1 Introduction to SCI-BUS and WS-PGRADE/gUSE http://www.sci-bus.eu Peter Kacsuk MTA SZTAKI Start date: 2011-10-01 Duration: 36 months SCI-BUS is supported by the FP7 Capacities Programme under contract nr RI-283481

2. 2 Motivations There are many user communities who would like to access several DCIs (grids, clouds, clusters) in a transparent way They do not want to learn the peculiar features of the used DCIs They want to concentrate their scientific application Therefore they need a science gateway

3. 3 How to build a science gateway? 1.Build from scratch –If the gateway is not extremely simple, it requires long time to develop a robust gateway –Requires substantial manpower and development cost –It is very specialized and as users start to use it and come up with new requirements it is difficult to extend in a scalable way –Isolated development without belonging to an open source community

4. 4 How to build a science gateway? 2. Adapt and customize an existing gateway technology –Significantly reduces development time –Requires limited manpower and development cost –Produces a robust and usable service –The open source community is driving force for further development and extensions SCI-BUS provides the required core gateway and customization technology

5. Criteria to select an existing gateway 1.Robustness 2.Sustainability –Will it exist in 3 years time? –How big and trustable the community who develops it? 3.Functionalities 4.How easy to adapt for the needs of the new user community? 5

6. 6 Main objectives of SCI-BUS Create a generic-purpose gateway technology Elaborate an application-specific gateway building technology and customisation methodology Establish production gateway services both for NGIs (horizontal user communities) and various science communities (vertical user communities) Create and maintain a Liferay portlet repository that enables the quick creation of user specific customised gateways Develop business models to guarantee sustainability and commercial exploitation

7. 7 SCI-BUS Project partners NoParticipant organisation namePart. short nameCountryExpertise & Experience 1Magyar Tudomanyos Akademia Szamitastechnikai es Automatizalasi Kutato Intezet MTA SZTAKIHungaryCoordinator in EDGeS, EDGI, SHIWA, developer of WS-PGRADE 2Academisch Medisch Centrum bij de Universiteit van Amsterdam AMCThe NetherlandsGateway developer for the medical user community 3Simsoft Bilgisayar Teknolojileri Ltd. Sti.SIMSOFTTurkeyGateway developer for business process modeling 4E-GROUP Ict Software Informatikai ZrtEGHungaryGateway developer for Web 2.0 5Eidgenössische Technische Hochschule ZürichETH ZurichSwitzerlandGateway developer for bioscience 6Middle East Technical UniversityMETUTurkeyGateway developer for seizmology 7Scaletools Ltd.STSwitzerlandGateway developer for clouds 8Eberhard Karls Universität TübingenEKUTGermanyGateway developer for computational chemistry 9University of WestminsterUoWUKDeveloper of UK NGS P-GRADE 10Universidad de ZaragozaUnizarSpainGateway developer for PireGrid SMEs 11CloudBroker GmBhCBSwitzerlandGateway developer for clouds 124D SOFT SZAMITASTECHNIKAI KFT4D SOFTHungaryGateway developer for ETICS-2 13Istituto Nazionale di AstrofisicaINAFItalyGateway developer for astrophysics 14Laurea-ammattikorkeakoulu oyLaureaFinnlandGateway developer for Blender 15The Provost Fellows & Scholars of the College of the Holy and Undivided Trinity of Queen Elizabeth near Dublin TCDIrelandGateway developer for helio- physics

8. Generic-purpose gateway technology 8 Based on Liferay WS-PGRADE (Web Services Parallel Grid Runtime and Developer Environment) gUSE (Grid User Support Environment) architecture General purpose Workflow-oriented portal framework Supports the development and execution of workflow-based applications

9. 9 WS-PGRADE/gUSE main features Scalable architecture based on collaborating services Seamless access to various types of DCIs: clusters service grids desktop grids clouds Advanced data-flows and workflow concept: Embedded workflows Parametric nodes Legacy codes Web services Advance input data management: Cross product Dot product

10. 3-tier scalable architecture based on collaborating services

11. Seamless access to various types of DCIs WF Graph editor WEB-UI (HTML) Liferay WS- PGRADE portal Liferay WS- PGRADE portal Information System WF Storage File Storage Application Repository WF Interpreter Backend local submitter GT4 submitter Glite submitter ARC submitter Unicore submitter BOINC submitter WS (Axis) submitter GT4 Grid WS DCI-Bridge Client machine Portal Server machine DCIs BES interface BOINC Grid ARC Grid

12. Creating and running WS-PGRADE workflow applications 12 Step 1: Edit workflow

13. Step 2: Configure the workflow

14. Running workflow instance

15. Recent and planned WS-PGRADE releases History from v3.4 Nov 2011: v3.4 (DCI Bridge) Feb 2012: v3.4.1 (usage statistics portlet) March 2012: v3.4.2 (support for new EMI release) April 2012: v3.4.3 (support for Liferay 6.1) May 2012: v3.4.4 (EDGI DCI support) June 2012: v3.4.5 (integrated SHIWA repository and installation wizard) June 2012: v3.4.6 (integrated installation and initialization wizard) Planned July 2012: v3.4.7 (improved user interface) July 2012: v3.4.8 (support for GT5) Sep 2012: v3.4.9 (integrated CloudBroker SaaS)

16. Downloads statistics at sourceforge

17. User access modes 17 ASM API WS-PGRADE UI Customized UI Other, existing UI WS-PGRADE workflow UI

18. 18 SCI-BUS gateways and DCIs Create 11 gateways in the 1 st project year Today Thursday

19. The main selling points of WS-PGRADE/gUSE: Workflow-oriented DCI gateway framework Access to many different DCIs Simultaneous execution of workflow nodes on various grid and cloud resources Separate view and working mode for power-users (application developers) and for end-users (e.g. Autodock gateway) Easy customization to build application specific gateways Access to different community repositories (e.g. SHIWA Workflow Repository) 19 Conclusions

20. Why to select WS-PGRADE/gUSE and join the SCI-BUS community? 1.Robustness –Already large number of gateways used in production 2.Sustainability –The SCI-BUS project and its sustainability and commercialization plan guarantees it 3.Functionalities –Rich functionalities that are growing according to the SCI-BUS and sourceforge community needs 4.How easy to adapt for the needs of the new user community? –Already large number of gateways customized from gUSE/WS- PGRADE 5.You can influence the progress of WS-PGRADE/gUSE 20 Join SCI-BUS as associated member