A Distributed Self-management Service
•
0 likes•1,688 views
Ioanna-Tsalouchidou_Master-thesis-presentation
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to A Distributed Self-management Service
Similar to A Distributed Self-management Service (20)
More from Ioanna Tsalouchidou
More from Ioanna Tsalouchidou (7)
Recently uploaded
Recently uploaded (20)
A Distributed Self-management Service
- 1. Introduction Architecture Policy language Evaluation Conclusions A Distributed Self-management Service Ioanna Tsalouchidou Universitat Polit`cnica De Catalunya e Kungliska Tekniska H¨gskolan o ioannatsalouchidou@gmail.com Supervisor: Leandro Navarro Moldes July 1, 2013 1 / 31
- 2. Introduction Architecture Policy language Evaluation Conclusions Overview 1. Introduction 2. Architecture 3. Policy language 4. Evaluation 5. Conclusions 2 / 31
- 3. Introduction Architecture Policy language Evaluation Conclusions Autonomic Computing The CONFINE Testbed Motivation Overview 1. Introduction 1.1 Autonomic Computing 1.2 The CONFINE Testbed 1.3 Motivation 3 / 31
- 4. Introduction Architecture Policy language Evaluation Conclusions Autonomic Computing The CONFINE Testbed Motivation Autonomic Computing Self-configuration: install/configure according to policies. Self-optimization: parameter tuning to perform optimally. Self-healing: identify, trace, diagnose and repair the cause failure. Self-protection: anticipate, detect and auto-defend against problems 4 / 31
- 5. Introduction Architecture Policy language Evaluation Conclusions Autonomic Computing The CONFINE Testbed Motivation Overview of the testbed CONFINE: Community Network Testbed for the Future Internet Community networks Scale up thousands of nodes, distributed geographically Users allocate resources to run experiments Multiple experiments run concurrently, sharing resources 5 / 31
- 6. Introduction Architecture Policy language Evaluation Conclusions Autonomic Computing The CONFINE Testbed Motivation Architecture 6 / 31
- 7. Introduction Architecture Policy language Evaluation Conclusions Autonomic Computing The CONFINE Testbed Motivation Motivation Address possible challenges in CONFINE testbed Predefined policies and automatic actions Self-management system for CONFINE testbed Policy specification language 7 / 31
- 8. Introduction Architecture Policy language Evaluation Conclusions Autonomic Computing The CONFINE Testbed Motivation Related Work Self management: MyOps, Puppet Policy languages: KAoS, Rei, Ponder 8 / 31
- 9. Introduction Architecture Policy language Evaluation Conclusions The Monitoring System The Self-management system Overview 2. Architecture 2.1 The Monitoring System 2.2 The Self-management system 9 / 31
- 10. Introduction Architecture Policy language Evaluation Conclusions The Monitoring System The Self-management system The monitoring system Large scale of infrequently-used data Slice and sliver specific information Metrics provided by the operating system or synthesized Receiver-pull model 10 / 31
- 11. Introduction Architecture Policy language Evaluation Conclusions The Monitoring System The Self-management system Architecture of the monitoring system 11 / 31
- 12. Introduction Architecture Policy language Evaluation Conclusions The Monitoring System The Self-management system The Self-management system Self-protection Cooperating with the monitoring system Components on server and research devices Collect, policy and action components 12 / 31
- 13. Introduction Architecture Policy language Evaluation Conclusions The Monitoring System The Self-management system Architecture of the self-management system 13 / 31
- 14. Introduction Architecture Policy language Evaluation Conclusions Theory Syntax Overview 3. Policy language 3.1 Theory 3.2 Syntax 14 / 31
- 15. Introduction Architecture Policy language Evaluation Conclusions Theory Syntax Objectives of the language Simple, extensible, expressive, easy to process Everything allowed unless explicitly prohibited If-then-else logic Describe the stable state of the testbed nodes Define actions when the system exceeds the stable state 15 / 31
- 16. Introduction Architecture Policy language Evaluation Conclusions Theory Syntax The syntax of the language Define the resource of reference CPU, memory, network One general block for each resource Smaller blocks within the general for each policy 16 / 31
- 17. Introduction Architecture Policy language Evaluation Conclusions Theory Syntax Example of the syntax I 17 / 31
- 18. Introduction Architecture Policy language Evaluation Conclusions Theory Syntax Example of the syntax II 18 / 31
- 19. Introduction Architecture Policy language Evaluation Conclusions The Method Scenario CPU Overview 4. Evaluation 4.1 The Method 4.2 Scenario CPU 19 / 31
- 20. Introduction Architecture Policy language Evaluation Conclusions The Method Scenario CPU Method Policy scenarios and experiments No performance metrics Quality of the design 20 / 31
- 21. Introduction Architecture Policy language Evaluation Conclusions The Method Scenario CPU Method Scenarios for CPU Definition of the stable state Actions 21 / 31
- 22. Introduction Architecture Policy language Evaluation Conclusions The Method Scenario CPU Scenario CPU I 22 / 31
- 23. Introduction Architecture Policy language Evaluation Conclusions The Method Scenario CPU Scenario CPU II 23 / 31
- 24. Introduction Architecture Policy language Evaluation Conclusions The Method Scenario CPU Scenario CPU II 24 / 31
- 25. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion Overview 5. Conclusions 5.1 Discussion 5.2 Future Work 5.3 Conclusion 25 / 31
- 26. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion Discussion: Self-management system Self-management system Cooperation with the monitoring system Architecture: server and node side Sliver and slice view 26 / 31
- 27. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion Discussion: Policy language Policy specification language Easy to comprehend, expressive and extensible Define resource, stable state, exceeding duration, action 27 / 31
- 28. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion Future Work Aggregation of data during duration period More fine-grained actions Prioritizing and grouping 28 / 31
- 29. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion Conclusion Autonomic computing CONFINE testbed Self-management system for CONFINE testbed Policy Specification language 29 / 31
- 30. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion References I Confine project. http://confine-project.eu/. T. Koch, C. Krell, and B. Kramer. Policy definition language for automated management of distributed systems. In Systems Management, 1996., Proceedings of Second IEEE International Workshop on, pages 55–64, 1996. Planetlab. http://www.planet-lab.org/. Stephen Soltesz, Marc Fiuczynski, and Larry Peterson. Myops: A monitoring and management framework for planetlab deployments. Gianluca Tonti, Jeffrey M. Bradshaw, Renia Jeffers, Rebecca Montanari, Niranjan Suri, and Andrzej Uszok. Semantic web languages for policy representation and reasoning: A comparison of kaos, rei, and ponder. In International Semantic Web Conference, pages 419–437, 2003. 30 / 31
- 31. Introduction Architecture Policy language Evaluation Conclusions Discussion Future Work Conclusion A Distributed Self-management Service Ioanna Tsalouchidou Universitat Polit`cnica De Catalunya e Kungliska Tekniska H¨gskolan o ioannatsalouchidou@gmail.com Supervisor: Leandro Navarro Moldes July 1, 2013 31 / 31