230 likes | 383 Views
Collaborative P-GRADE Portal Gergely Sipos 1 , Gareth J. Lewis 2 , Peter Kacsuk 1 , Vassil Alexandrov 2 1 MTA SZTAKI (Hungary) 2 University of Reading (UK). Contents. Workflow-oriented Grid portals and the P-GRADE Portal Why do we need collaborative portals?
E N D
Collaborative P-GRADE PortalGergely Sipos1, Gareth J. Lewis2,Peter Kacsuk1, Vassil Alexandrov21MTA SZTAKI (Hungary)2University of Reading (UK) GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Contents • Workflow-oriented Grid portals and the P-GRADE Portal • Why do we need collaborative portals? • Collaborative workflow development • Collaborative workflow execution • Conclusion GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
edit Framework Workflow manager submit results Workflow-oriented Grids and Grid portals today Browser Special client Portal Portal Grid Grid GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Offline communication Browser Special client edit Communication through the portal Isolation submit submit results results Duplication Collaborative work? Browser Special client edit Portal Grid GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
General properties of the P-GRADE Portal • Portal for computational grids • Supported services (functionalities) • GT2 GRAM–job execution • Mercury–job monitoring • MyProxy– proxy credential management • Contains a built-in workflow editor • Job-workflow supportusing Condor DAGMan GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
The inner structure of the P-GRADE Portal Java enabled web browser P-GRADE Portal Condor DAGMan Workflow manager Downloadable workflow editor Built-in tools GT2 GRAM … GT2 GRAM Mercury … Mercury MyProxy … MyProxy Supported Grid Services Internet host host host host host host host host host host … GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Offline communication Browser Special client edit Communication through the portal Isolation submit submit results results Duplication Collaborative work? Collaboration? No, thanks! Collaboration? No, thanks! Browser Special client edit Portal Grid GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
edit edit submit results results The solution: workflow-oriented collaboration! Browser Special client Browser Special client Portal Grid GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
The solution: workflow-oriented collaboration! No time-consuming communication… Browser Special client Browser Special client …only efficient real-time collaboration! edit Portal edit submit results results Grid GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Collaborative workflows • Integrate knowledge – development phase • Distribute results – execution phase Collaborative workflow GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Collaborative workflows Content of the “biomedical” nodes Topology of the graph • Integrate knowledge – development phase • Distribute results – execution phase Most suitable resources or services Collaborative workflow Content of the “chemistry” nodes GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Collaborative development • The portal has to: • Result a consistent workflow • Protect against data loss (transaction management) • As real-time as possible! • Provide simple GUI • Guarante group-level security GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Collaborative development model • Locking workflow branches exclusively, “first come first served” • Using transitive data dependence relations GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Collaborative development model • Locking workflow branches exclusively, “first come first served” • Using transitive data dependence relations GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Collaborative development model • Locking workflow branches exclusively, “first come first served” • Using transitive data dependence relations GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
The result graph • Locking workflow branches exclusively, “first come first served” • Using transitive data dependence relations Job/service data data Job/service Job/service data data data data Job/service Job/service Job/service GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Implementation • Extends the single-user version of the P-GRADE Portal: • Globus VOs • Gridsphere-based portal server • Webstart-based workflow-editor • Web browser for execution management GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Lockrequest Updatedglobalview Requesting a lock P-GRADE Portal workflow editor #1 P-GRADE Portal server P-GRADE Portalworkflow editor #2 GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Push updatedlocal view Pullglobal view Synchronising the different views P-GRADE Portal workflow editor #1 P-GRADE Portal server P-GRADE Portalworkflow editor #2 GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
VO 1 VO 2 P1 P2 P3 VO 3 Collaborative workflow management • Concurrent execution control requests • Different persons’ certificates for a single workflow GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
MyProxy server MyProxy server MyProxy server MyProxy access DB P1 P3 P2 Multi-proxy problem & solution • The submitter do not want to wait… • Use MyProxyaccess DB! P-GRADE Portal server VO 1 VO 2 VO 3 GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Conclusions • Collaborate through workflow applications! • Collaborative P-GRADE Portal: Available from June2005 at www.lpds.sztaki.hu/pgportal GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005
Thank you for the attention! Questions… sipos@sztaki.huwww.lpds.sztaki.hu GridSphere Portlets Workshop, Edinburgh, 3-5. March, 2005