1 / 50

Advanced features of the P-GRADE portal

Explore the advanced features of the P-GRADE portal for grid interoperability and collaborative grid application development. Supports job submission in 2nd and 3rd generation grids, legacy code service invocation, and transition between different grid technologies.

shawnv
Download Presentation

Advanced features of the P-GRADE portal

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. Advanced features of the P-GRADE portal Peter Kacsuk, Gergely SiposMTA SZTAKI Tamás KissUniversity of Westminster www.lpds.sztaki.hu/pgportal pgportal@lpds.sztaki.hu

  2. Contents • Solving Grid interoperability • Supporting collaborative Grid application development • Classification of Grid portals

  3. Grid interoperability

  4. Grid interoperability 1 • P-GRADE portal supports job submission in 2nd generation Grids: • LCG – EGEE • GT2 – UK NGS and US OSG • NorduGrid • P-GRADE Portal enables: • Connecting 2nd generation production Grids

  5. Proxy Job User Workflow Leeds Job Job Job Connecting 2nd generation production Grids UK NGS GT2 Certificate server Manchester SZTAKI Portal Server P-GRADE Portal v2.3 EGEE-VOCE LCG-2 Budapest Supports both direct and brokered job submission LCG-2broker Poznan Brno

  6. Grid interoperability 2 • P-GRADE Portal with GEMLCA supports legacy code service invocation in 2nd and 3rd generation Grids: • LCG, gLite – EGEE • GT2, GT4 – UK NGS • Combination of jobs and legacy code services enables P-GRADE Portal to support: • Extending 2nd generation Grids with legacy code services

  7. Executable User Executable EGEE/VOCE Leeds Poznan Executable Budapest Extending 2nd generation Grids with legacy code services NGS GT2 UoW Portal Server GEMLCAP-GRADE Portal Manchester Job Repository (GEMLCA)

  8. Grid interoperability 3 • Combination of jobs and legacy code services enables P-GRADE Portal to support: • Transition from 2nd generation Grids to 3rd generation Grids: • Extending 2nd generation production Grids with 3rd generation volunteer Grid sites • Connecting 2nd generation production Grids with 3rd generation volunteer Grids • Connecting 2nd generation and 3rd generation production Grids

  9. UoW Portal Server P-GRADE NGS GEMLCA Portal Executable User Executable Executable Service Invocation UoW site – GT4 with GEMLCA Service Extending 2nd generation Grids with 3rd generation volunteer Grid sites UK NGS GT2 Manchester Westminster Oxford GEMLCA Repository

  10. Extending the NGS with legacy code services and GT4 Resources GT2 Job submission to Rutherford GEMLCA Legacy code submitted to Oxford GT4 Service Invocation at UoW GT2 Job submission to Manchester

  11. UoW Portal Server P-GRADE NGS GEMLCA Portal Executable User WestFocus GT4 Grid Leeds Executable UoW Brunel Extending 2nd generation production Grids with 3rd generation volunteer Grids NGS GT2 Grid Manchester Service Invocation GEMLCA Repository

  12. Executable Executable User EGEE LCG/gLite Service Invocation WestFocus GT4 Grid Executable Leeds Poznan Executable UoW Budapest Brunel Connecting 2nd generation and 3rd generation production Grids NGS GT2 UoW Portal Server GEMLCAP-GRADE Portal Manchester Job Repository (GEMLCA)

  13. Plan: Connecting major Grids by GEMLCA and the P-GRADE Portal In test phase Available

  14. Regional coverage of using P-GRADE Portal + GILDA For education & training

  15. Conclusion:Easy-to-use, technology-neutral Grid portal for e-Scientists • The P-GRADE Portal hides differences ofGrids • Globus 2 and 4 – LCG2 – gLite Grid interoperability • Transparent switching between Grid technologies • Graphical tools for application development, execution and monitoring • Sequential & parallel components can be integrated into large Grid applications • Direct or broker-based resource allocation • Your code does not have to contain grid specific calls

  16. Collaborative work support

  17. Defineapplication Gridapp. Executeapplication Get results Grid usage Browser Special client Portal Grid portal Grid middleware and resources Grid

  18. The problem • Grids have been designed for highly complex applications (The overhead is too big to execute small programs…) • How can a single person define highly complex applications?

  19. Browser Special client Defineapplication Gridapp. Portal Executeapplication Get results Grid The solution today… E-mail, phone, skype, MSN, …

  20. Browser Special client Defineapplication Gridapp. Portal Executeapplication Get results Grid The solution today… E-mail, phone, skype, MSN, … How can I integrate the knowledge of many people into a single and consistent entity in the shortest time?

  21. Similar problems have been already solved… • Concurrent editing of Web pages: WIKI, MediaWiki • Concurrent editing of documents: Online collaboration tool in MS Word • Concurrent editing of tables: Online collaboration tool in MS Excel • …

  22. The solution: collaborative Grid portals • Grid portals that support • concurrent engineering of applications • concurrent management of application execution Portal Gridapplication Grid

  23. edit edit submit results results The Collaborative P-GRADE Portal Browser Special client Browser Special client P-GRADE Portal Grid

  24. edit edit submit results results The Collaborative P-GRADE Portal No time-consuming communication… Browser Special client Browser Special client …only efficient, workflow-oriented collaboration! P-GRADE Portal Grid

  25. Collaborative Grid workflows • Integrate knowledge – development phase • Generate and distribute results – execution phase Collaborative workflow

  26. Input protein molecules Topology of the graph Protein foldingalgorithm Experiment results An e-Science example Collaborative workflow

  27. Input for the market prediction application Graph topology Market prediction model Results of the prediction workflow A business example Collaborative workflow

  28. Collaborative workflow development • The portal has to guarantee that the result is a consistent workflow • Protect against data loss  locking mechanisms • As real-time as possible!  to increase parallelism during development

  29. Workflow development model • Locking workflow components (jobs) exclusively • First come first served • Only the owner can edit the component

  30. Workflow development model • Locking workflow components (jobs) exclusively • First come first served

  31. Workflow development model • Locking workflow components (jobs) exclusively • First come first served

  32. Screenshot Locked for somebody else Locked for me Unlocked

  33. Lockrequest Lockaccepted Requesting a lock Workflow editor #1 Portal server Workflow editor #2

  34. Push updatedlocal view Pull global view Synchronizing the different views Workflow editor #1 Portal server Workflow editor #2

  35. Result of the collaborative development Job Grid resource data data Job Job Grid resource Grid resource data data data data Job Job Job Grid resource Grid resource Grid resource

  36. Grid 1 Grid 2 P1 P2 P3 Grid 3 Executing collaborative workflows • Concurrent control requests It can happen in single-user case too (multiple browsers are opened) • Different users’ proxies to be used to execute different workflow nodes

  37. Conclusions • Extend the single-user version of the P-GRADE Portal: • Concurrent engineering of workflow-based grid applications • Application execution by multiple users in a concurrent fashion • Prototype version already available

  38. Classification of Grid portals

  39. Two orthogonal aspects of Grid portals usage • Number of accessible Grids • Single isolated Grid (SI) • Multiple isolated Grids (MI) • Multiple collaborative Grids (MC) • Collaborative vice not collaborative usage • Multiple isolated users (MI) • Multiple collaborative users (MC)

  40. Portal classification

  41. MISI Portal: P-GRADE portal 1.0 LCG-2 P-GRADE-Portal Rome London Athens

  42. Multi-Grid portals Portal classification

  43. MIMI Portal: P-GRADE portal (2.1) GridLab P-GRADE-Portal SEE-Grid London Rome Athens

  44. Portal classification

  45. MIMC Portal: P-GRADE portal (2.1) GridLab P-GRADE-Portal SEE-Grid London Rome Athens

  46. Portal classification

  47. MCMC Portal: P-GRADE portal (3.0) GridLab P-GRADE-Portal SEE-Grid Rome London Athens

  48. P-GRADE 3.0+ P-GRADE 2.3 Summary of classification

  49. Conclusions • xxMC portals: execute a workflow simultaneously in many Grids • P-GRADE portals 2.1 - 2.3 already work as xxMC portal providing service for several production Grids: • HunGrid • SEE-Grid • VOCE • UK NGS www.lpds.sztaki.hu/pgportal • MCxx portal: Enables to collaborate through workflow applications! • Collaborative P-GRADE Portal: Prototype was demonstrated at SC05 exhibition

  50. Thank you for the attention! Questions… kacsuk@sztaki.huwww.lpds.sztaki.hu

More Related