1. A Framework to Test Autonomic Containers Brittany Parsons and Ronald Stevens July 6, 2006 REU Sponsored by NSF

2. 2 Outline of Presentation 1. What are we trying to accomplish? 2. What is an Autonomic Container? 3. What is the architecture of an Autonomic Container? 4. What testing tools are being used for this project? 5. Future Work

3. 3 1. What are we trying to accomplish? 1. What are we trying to accomplish?  In this project, we are trying to address a way to test autonomic systems.  In order to create an application simple enough to test autonomic characteristics, we have come up with the idea of an autonomic container.

4. 4 2. What is an Autonomic Container?  An Autonomic Container is a data structure that can be dynamically changed during run time.  A container a is structure used for object holding or collecting.  It must contain the four characteristics of Autonomic Computing: self healing, self protecting, self optimizing, and self configuring.

5. 5 Testing within the Autonomic Manager  In order to properly test an Autonomic Container, we would like to implement a test set up in the autonomic element.  Taking knowledge already known about Autonomic Computing, we would like to add to the existing architecture.

6. 6 Touchpoint Manager for an Autonomic Computing System

7. 7 Touchpoint Manager for an Autonomic Container Test Controller

8. 8 Touchpoint Manager for an Autonomic Container Test Monitor Test Controller

9. 9 Touchpoint Manager for an Autonomic Container Test Monitor Test Analyzer Test Controller

10. 10 Touchpoint Manager for an Autonomic Container Test Monitor Test Analyzer Test Planner Test Controller

11. 11 Touchpoint Manager for an Autonomic Container Test Monitor Test Analyzer Test Planner Test Executor (Runner) Test Controller

12. 12 Completed Autonomic Container Touchpoint Manager

13. 13 3. Architecture of an Autonomic Container

14. 14 Our Contribution  We are in charge of working on the managed element and the test executer.  For the Autonomic Container, we need to be able to make a copy of the managed element that will run parallel to the original element.  During runtime, the copy of the element will be tested on and updated as the original element is updated.

15. 15  When a change is requested, the contents of the managed element copy are switched with the original element.

16. 16 Implementation of an Autonomic Container  In order to implement the Autonomic Container, we need a simple application to run.  The simple application we have chosen to run is a stack.  This stack is a simple data structure written in Java that contains the functions push, pop, and resize.

17. 17 4. What testing tools are being used for this project?  To test this project we will be using two testing tools. They are JUnit and the Rational Functional Tester.

18. 18 What is JUnit?  JUnit is a unit testing framework for Java.  JUnit is part of a family of unit testing frameworks [1]  PyUnit (Python language version)  fUnit (Fortran language version)  CPPUnit (C++ language version)  Collectively referred to as xUnit frameworks.

19. 19 What is Rational Functional Tester?  An automated functional and regression testing tool for testing and GUI development that can be used with Java and Microsoft VisualStudio  Can be used with web-based applications

20. 20 Demonstration

21. 21 Sources  [1] Wikipedia – JUnit http://en.wikipedia.org/wiki/JUnit http://en.wikipedia.org/wiki/JUnit  [2] IBM – Rational Functional Tester http://www-306.ibm.com/software/awdtools/tester/functional/