1. 06/08/10 P-GRADE Portal and MIMOS P-GRADE portal developments in the framework of the MIMOS-SZTAKI joint project Mohd Sidek Salleh MIMOS Berhad Zoltán Farkas MTA SZTAKI

2. 06/08/10MIMOS and P-GRADE Portal 2 Outline Introduction About the project MIMOS infrastructure Developments Accounting solution SLA solution: Static Dynamic Split GUI and runtime Summary

3. 06/08/10MIMOS and P-GRADE Portal 3 Project description 1 year duration started at 03.10.2009 3 main actitity groups: Trainings: Grid application developer, P-GRADE Portal developer (I and II), application specific module developer Developments: Accounting-related developments SLA-related developments Split GUI and runtime Support: Up to 12 MM second-level support for P-GRADE Portal

4. 06/08/10MIMOS and P-GRADE Portal 4 MIMOS infrastructure

5. 06/08/10MIMOS and P-GRADE Portal 5 In focus: main development tasks I. Accounting: Keep track of user activities Rely on gLite services Extend P-GRADE Portal with user and administrator interface SLA: Two phases: static and dynamic Static: predict job start time based on static values Dynamic: prefict job start time based on the infrastructure's status Users may ask for and SLA: jobs will be submitted to HA resources

6. 06/08/10MIMOS and P-GRADE Portal 6 In focus: main development tasks II. Split GUI and runtime: User interface is detached from runtime Delays of runtime layer do not increase response time Multiple runtime installation may be used to increase throughput

7. 06/08/10MIMOS and P-GRADE Portal 7 Accounting I. Additional portlet for keeping track of computing resources consumed by users Two operations: Sysadmin: able to query every users' data Normal user: ability to query data belonging to proxies possessed by the user Based on gLite's APEL accounting system

8. 06/08/10MIMOS and P-GRADE Portal 8 Accounting II. - APEL

9. 06/08/10MIMOS and P-GRADE Portal 9 Accounting III.

10. 06/08/10MIMOS and P-GRADE Portal 10 SLA I. Service Level Agreement Present users an estimated startup deadline for their workflows before submission If a user accepts the deadline, their jobs will be submitted to high-availability resources If not, jobs are sent to normal resources Static SLA: calculated deadline depends on static values Dynamic SLA: deadline depends on the system's status

11. 06/08/10MIMOS and P-GRADE Portal 11 SLA II. - Dynamic SLA Properties changing deadline: Application (workflow) properties Job properties Tier 1 site properties Jobs running on Tier 1 sites according to BDII Jobs running on Tier 1 sites according to P-GRADE Portal P-GRADE Portal's status: Number of workflows running Number of running jobs

12. 06/08/10MIMOS and P-GRADE Portal 12 SLA III. - Formula

13. 06/08/10MIMOS and P-GRADE Portal 13 SLA IV. - User Interface extensions

14. 06/08/10MIMOS and P-GRADE Portal 14 Split GUI and runtime I. Provide a way to install GUI and runtime components on different machines Offer the possibility to install a number of runtime components This way, a heavily loaded runtime component doesn't increase the response time of the user interface

15. 06/08/10MIMOS and P-GRADE Portal 15 Split GUI and runtime II.

16. 06/08/10MIMOS and P-GRADE Portal 16 Split GUI and runtime III. Workflow storage is common through a shared filesystem GUI component sends user requests to runtime components using XML-RPC Runtime components are periodically „pinged” Runtime components are used in a round-robin method.

17. 06/08/10MIMOS and P-GRADE Portal 17 Summary Additional developments for P-GRADE Portal to increase its usability Accounting: keep track of resources consumed by users in a convenient way SLA: „one-click” way to have a guarantee for the workflow's startup time Split GUI and runtime: increase user experience by detaching from overloaded runtime