P-GRADE Portal and GEMLCA: A workflow-oriented portal and application hosting environment

1. P-GRADE Portal and GEMLCA: A workflow-oriented portal and application hosting environment Miklos Kozlovszky m.kozlovszky@sztaki.huMTA SZTAKI (Hungarian Academy of Sciences) www.portal.p-grade.huwww.cpc.wmin.ac.uk/gemlca

2. Contents • Motivation of creating the tools • P-GRADE Portal and GEMLCA in a nutshell • Lifecycle of GEMLCA / P-GRADE applications • Services provided for application developers • Introduction to the hands-on exercises • Hands-on

3. Application Application toolkits, standards Higher-level grid services (brokering,…) Basic Grid services:AA, job submission, info, … Context Graphical interface Middleware independent services and interfaces of P-GRADE/GEMLCA Middleware specific clients Grid middleware services

4. Current situation and trends in Grid computing • Fast evolution of Grid systems and middleware: • GT2, OGSA, GT3 (OGSI), GT4 (WSRF), LCG-2, gLite, … • Many production Grid systems are built with them • EGEE (LCG-2  gLite), UK NGS (GT2), Open Science Grid (GT2  GT4), NorduGrid (~GT2) • Although the same set of core services are available everywhere, they are implemented in different ways • Data services (file management) • Computation services (job submission) • Security services (proxy based single sign-on) • Brokers (not in every middleware, but e.g. in gLite - WMS)

5. TODAY’S FOCUS P-GRADE Portal in a nutshell • General purpose, workflow-oriented computational Grid portal. Supports the development and execution of workflow based Grid applications – a Grid orchestration environment • Based on GridSphere web portal framework • Functionalities are accessed through portlets • Easy to expand with new portlets (e.g. application-specific portlets) • Easy to tailor to end-user or community needs • Developed by SZTAKI (1.0 in 2003, now 2.5) • Grid services supported by P-GRADE Portal 2.5: Solves Grid interoperability problem at the workflow level

6. GEMLCA extension of theP-GRADE Portal • P-GRADE Portal extended with GEMLCA Grid service back-end • To share jobs and legacy codes as application components with others • A step towards collaborative e-Science • Developed by the University of Westminster (London) • Support for Globus 4 grids (besides GT2 and EGEE) • Available on the NGS and OGF GIN LCG / gLite VOs P-GRADE Portal Globus 2 VOs GEMLCA job job job job Globus 4 VOs

7. Related projects The development, operation and training of P-GRADE Portal and GEMLCA is supported by the following projects: • SEE-GRIDwww.see-grid.eu Development, application support • Coregrid www.coregrid.net Research, development • EGEEwww.eu-egee.org gLite training, application development • ICEAGEwww.iceage-eu.org Grid training and education

8. A Grid application in the GEMLCA / P-GRADE Portal • A directed acyclic graph where • Nodes represent jobs or services (a batch program executed on a computing resource) • Ports represent input/output files the components expect/produce • Arcs represent file transfer operations • Semantics of the workflow: • A job can be executed if all of its input files are available • Responsibility of the built-in workflow manager

9. Parallel execution inside a workflow node • Parallel execution among workflow nodes Multiple nodes can run parallel The job/service can be a parallel code Three levels of parallelism within a P-GRADE Portal application Multiple instances of the same workflow process different data files • The workflow concept of the GEMLCA/ P-GRADE Portal enables the efficient parallelization of complex problems • Semantics of the workflow enables two levels of parallelism: • Parametric sweep execution of the workflow (SIMD)

10. Workflow-level Grid interoperability:The GIN Resource Testing portal Grid Interoperability Now VO Portal: OGF effort to demonstrate workflow level grid interoperability between major production Grids and to monitor these resources

11. SAVE WF / PS REUSE WORKFLOW COMPONENTS START EDITOR The typical user scenarioPart 1 - development phase MyProxy servers Gridservices Portal server OPEN & EDIT or DEVELOP WORKFLOW or PS WF

12. TRANSFER FILES, SUBMIT JOBS DOWNLOAD PROXY CERTIFICATES MONITOR JOBS VISUALIZE JOBS and WORKFLOW PROGRESS DOWNLOAD (SMALL) RESULTS DOWNLOAD (SMALL) RESULTS The typical user scenarioPart 2 - execution phase MyProxy servers Gridservices Portal server Keep large files on Grid storage resources

13. Share workflow components with other users of the same portal Export and share workflows with users of the same, or another portal The typical user scenarioPart 3 - collaborative phase MyProxy servers Gridservices Portal server

14. Optional plug-in: GEMLCA service(WSRF) Inside the portal server Webbrowser Java Webstartworkflow editor Client • Technology specific gateways • File transfer • Proxy management • Load monitoring Tomcat P-GRADE Portal portlets (JSR-168, Gridsphere 2):Workflow, Certificates, Information System, Settings, GEMLCA P-GRADEPortalserver DAGMan workflow manager Mercury API Informationsystemclients CoG API& scripts shell scripts Grid middleware clients Grid middleware services (WMS, LFC, SE, …) Mercurymonitorservice Informationsystems MyProxy server & VOMS Grid

15. Workflow EditorDefining the graph Define a Directed Acyclic Graph (DAG) of jobs and services (GEMLCA jobs): • Drag & drop components:nodes and ports • Define their properties • Connect ports by channels(no cycles, no loops, no conditions…)

16. Workflow EditorProperties of a job component • Properties of a job: • Type of executable • Client side location of the binary • Number of required processors • Command line parameters • The resource to be used for the execution: • Grid (VO) • Resource / broker

17. Workflow EditorDefining broker jobs Select a Grid with broker! (*_BROKER) Ignore the resource field! If default JDL is not sufficient use the built-in JDL editor!

18. Workflow EditorBuilt-in JDL editor for brokered jobs Rank & Requirement JDL  look at the gLite Users’ manual!

19. Workflow EditorProperties of a service component (GEMLCA job) • Properties of a service: • The location of the service: • Grid (VO) • Resource / broker • An application (binary) associated with that resource • Input parameter values for the service

20. Workflow EditorDefining job / service input-output data File properties Type: input:the component reads output:the component writes File type:local: originates from my desktop remote: originates from a grid storage element File: location of the file File storage type (for outputs only): Permanent:final result Volatile:used only for inter-component data transfer

21. Client side location: c:\experiments\11-04.dat LFC logical file name(LFC file catalog is required – EGEE VOs)lfn:/grid/gilda/sipos/11-04.dat GridFTP address (in Globus Grids): gsiftp://somengshost.ac.uk/mydir/11-04.dat Local file Remote file How to refer to an I/O file? Input file Output file • Client side location: result.dat • LFC logical file name(LFC file catalog is required – EGEE VOs)lfn:/grid/gilda/sipos/11-04_-_result.dat • GridFTP address (in Globus Grids): gsiftp://somengshost.ac.uk/mydir/result.dat

22. LOCAL INPUT FILES & BINARIES LOCAL INPUT FILES& BINARIES REMOTE INPUTFILES REMOTE OUTPUTFILES LOCAL OUTPUT FILES LOCAL OUTPUT FILES Binaries of GEMLCA jobs Workflow level file transferby the workflow manager Gridinfrastructure Portal server Storage elements User levelstorage GEMLCArepository Computing elements

23. Generated by the portal LOCALINPUTFILE REMOTE INPUTFILE 1 0 Custom file transfer LOCAL OUTPUTFILE REMOTE OUTPUTFILE 2 3 Generated by the portal Job / service level file transferby the workflow manager 0 1 Gridinfrastructure 2 3 Storage Elements Computing Element Pre script Portal server binary Post script

24. Reminder: grid files in JDL lfn: logical file name RB uses File Catalog to find file location The file itself is NOT transferred by the middleware! Your binary must transfer input/output grid files! • Example JDL file Executable = “gridTest”; StdError = “stderr.log”; StdOutput = “stdout.log”; InputSandbox = {“/home/joda/test/gridTest”}; OutputSandbox = {“stderr.log”, “stdout.log”}; InputData = “lfn:/grid/VOname/mydir/testbed0-00019”; Requirements = other.Architecture==“INTEL” && \ other.OpSys==“LINUX” && other.FreeCpus >=4; Rank = “other.GlueHostBenchmarkSF00”; Higher level tools can tranfer the file for you. E.g. P-GRADE Portal Your code does not have to “speak” storage protocols if it is developed in P-GRADE Portal!

25. Information system portlet tobrowse computing elements Graphical interface for BDII servers

26. Workflow execution Main steps • Download proxies • Submit workflow • Observe workflow progress • If some error occurs correct the graph • Download result

27. Certificate ManagerCertificates portlet • To start your session on the Grid you must create a proxy certificate on the portal server • “Certificates” portlet: • to upload a proxy into MyProxy servers • to download a proxy from MyProxy into the portal server

28. Certificate ManagerMulti-grid portal Multi-proxy environment Multiple proxies can be available on the portal server at the same time! Certificate from Hungarian CA: HUNGRID CEs and SEs Certificate from EGEE CA: SEE-GRID CEs and SEs

29. Proxy2 VOMS ext. Proxy2 VOMS ext. Proxy2 Certificates, proxies with gLite VOs:Download MyProxyserver Proxy1 VOMSserver Gridservices I have to do this every time when I want to execute workflows Portal server

30. Workflow Management(workflow portlet) • The portlet presents the status, size and output of the available workflow in the “Workflow” list • It has a Quota manager to control the users’ storage space on the server • The portlet also contains the “Abort”, “Attach”, “Details”, “Delete” and “Delete all” buttons to handle execution of workflows • The “Attach” button opens the workflow in the Workflow Editor • The “Details” button gives an overview about the jobs of the workflow

31. Workflow Execution(observation by the workflow portlet) White/Red/Green color means the job is initial/running/finished state

32. Workflow Execution(observation by the workflow portlet) White/Red/Green color means the job is initial/running/finished state

33. Workflow Execution(observation by the workflow portlet) White/Red/Green color means the job is initial/running/finished state

34. Workflow Execution(observation by the workflow portlet) White/Red/Green color means the job is initial/running/finished state

35. Workflow Execution(observation by the workflow portlet) White/Red/Green color means the job is initialised/running/finished

36. The portal monitors and visualizes parallel jobs(if they are prepared for Mercury monitor) On-Line Monitoring both at the workflow and job levels (workflow portlet) • The portal monitors and visualizes workflow progress

37. Rescuing a failed workflow 1. Read the error log to know why A job failed during workflow execution

38. Rescuing a failed workflow 2. Map the failed job onto a different resource or download a new proxy for it Don’t touch the finished jobs! The execution can continue from the point of failure

39. Downloading the results…

40. Sharing a successfully finished job with other users: GEMLCA repository GEMLCArepository

41. Combine services and your codein the same workflow! Collaborative grid applications Service invocation Service invocation Job submission Service invocation Job submission

42. File Managementthrough LFC and LCG • File / Directory management through LFC and LCG • listing LFC hosts for the selected VO • browsing a LFC directory • creating a new directory • removing a directory/file • displaying details (owner-group info, last modification, access rights) of a directory/file • renaming a directory/file • changing access rights of a directory/file • uploading a (local) file to a storage element • downloading a file from a storage element • listing replicas of a file • replicating a file • deleting a replica of a file In the frame of the Portal Developer Alliance Birsen Omay from the Middle East Technical University has created this new P-GRADE Portal extension.

43. File Managementthrough LFC and LCG LFCHost Portal server Storage Element LFC file and directory management

44. MyProxy Credential ManagerGetting information about a MyProxy credential • MyProxy Credential Management • getting info about a previously stored MyProxy credential • changing passphrase of a MyProxy credential • removing a credential In the frame of the Portal Developer Alliance Birsen Omay from the Middle East Technical University has created this new P-GRADE Portal extension

45. MyProxy Credential ManagerGetting information about a MyProxy credential • MyProxy server access details: • Hostname • Port number • User name (from upload) • Password (from upload) Display information about MyProxy credential

46. Certificates, proxies:Getting information MyProxyserver Gridservices Get information (owner, start date, end date) about the credential stored for “username”from MyProxy Server Portal server Request information about the credential

47. MyProxy Credential ManagerGetting information about a MyProxy credential Information about the credential for username “birsen”

48. Certificates, proxies:Changing Passphrase MyProxyserver Gridservices Modify password of the credential stored for “username” Portal server Change password for “username”

49. Certificates, proxies:Removing a Credential MyProxyserver Gridservices Remove the credential for “username” from MyProxy server Portal server Destroy the credential for “username”

50. How to get access? • P-GRADE Portal service is available: • SEE-GRID infrastructure • Central European VO of EGEE • GILDA: Training VO of EGEE • Many national Grids (UK National Grid Service, HunGrid, Turkish Grid, etc.) • US Open Science Grid, TeraGrid • Economy-Grid, Swiss BioGrid, Bio and Biomed EGEE VOs, BalticGrid • OGF Grid Interoperability Now (GIN) VO portal.p-grade.hu/index.php?m=5&s=0