1. G RID R ESOURCE BROKER FOR SCHEDULING COMPONENT - BASED APPLICATIONS ON DISTRIBUTED RESOURCES Reporter : Yi-Wei Wu

2. A BSTRACT This paper presents design and implementation of seamless integration of two complex systems ProActive Gridbus Resource Broker ProActive → Leverage the economy-based and data-intensive scheduling algorithm Gridbus Broker → Use component-based distributed applications. 2

3. O UTLINE Introduction Background Knowledge Integration Challenges System Implementation Validation Remarks of the Integration Conclusion 3

4. I NTRODUCTION Grid The job includes requirements and submit to a Grid Return the result of the execution What’s need? Dynamically vary the parameter space Grid as a unified platform Component-based application 4

5. INTRODUCTION ProActive Use functions for handling the heterogeneity and dynamicity of Grid resources This paper An integration of Gridbus Broker and ProActive framework 5

6. BACKGROUND KNOWLEDGE ProActive Grid Scheduler Gridbus Broker Scheduling Infrastructure 6

7. PROACTIVE GRID SCHEDULER What is ProActive? An open source java library (GPL2) For parallel, dist- ribution application 7

8. 8

9. PROACTIVE GRID SCHEDULER 9 Why Integration? lack of advanced scheduling algorithm

10. GRIDBUS BROKDER SCHEDULING INFRASTRUCTURE 10

11. INTEGRATION CHALLENGES ProActive Can leverage the economy-based and data-intensive scheduling algorithm Gridbus Broker Can utilise the programming environment especially the component-based programming concept 11

12. INTEGRATION CHALLENGES ProActive + Gridbus Broker = Challenge? 1. Identify is on the potential impact of the integration on both systems. There should be no or minimum impact on both systems 1. The reuse of existing infrastructure and codebase provided by both systems. Maxmise reusability and avoid modifying the existing source code 12

13. SYSTEM IMPLEMENTATION 13 Replacing the existing scheduling infrastructure dynamically Responsible for wrapping the ProActive terms into the Broker’s terms that can be scheduled and managed

14. SYSTEM IMPLEMENTATION 14

15. VALIDATION The integration solution is valid unless the following two conditions are satified 1. Legacy applications developed should work without changing and recompiling the source code 2. The dependencies between each system should be minimized 3. Reuse the existing infrastructure at both sides without adding new features. 15

16. VALIDATION C3D application Java benchmark application Measure the performance of a 3D raytracer renderer over several JVM 16

17. VALIDATION 17

18. REMARKS OF THE INTEGRATION Impacts on ProActive Impacts on Gridbus Broker 18

19. REMARKS OF THE INTEGRATION- IMPACTS ON PROACTIVE System level- Scheduler add a new overload start method Application level- The client applications developed using the ProActive framework Last notable- Check how many extra dependencies 19

20. REMARKS OF THE INTEGRATION- IMPACTS ON GRIDBUS BROKER The broker role as a middle-man who is responsible for matching job to heterogeneous resources. Various types of runtime Grid middleware can be plugged into runtime environment of broker at runtime via the configuration 20

21. CONCLUSION AND FUTURE WORK 1. A schedule component-based applications on global Grids by utilising the Gridbus resource broker 2. The solution follows the object-oriented design principles 3. Legacy application running without modifying and recompiling the source code 4. Focus on other types of runtime environments 21

22. THE END Thanks for your attention 22