Research projects in Autonomic computing.

By reading this paper you can gain the knowledge about Autonomic Computing. I detailed it under the following sub topics.

 1.0 Introduction
 2.0 Why need Autonomic?
 3.0 Major Researches 
           3.1 Research projects in Autonomic computing.
           3.2 University research projects in autonomic computing
4.0 Four basic elements of autonomic computing
           4.4 self-protecting
           AutonomicComputing Vs Current Computing
5.0 Autonomic computing architecture
6.0. Autonomic computing today
           6.1. Initiatives of autonomic computing 
           6.2. Benefits
           6.3. Applications
7.0 What happen if does not have autonomic in the future?
8.0 Autonomic Computing Research Issues and Challenges
9.0 Future direction of Autonomic computing
10.0 Conclusion

3.1 Research projects in Autonomic computing

Listed below are selections of brief descriptions of some of the projects underway at IBM. These projects are at different stages of development or progress. Some of them have already appeared in products. Some are just beginning. This list of projects will grow as new areas of research emerge.

 1. Gryphon: Pub/Sub (Middleware)

This middleware for Publish/Subscribe is used to distribute large volumes of data/content in real time to thousands of clients distributed throughout a large "public" network, such as a wide area extranet or intranet that is too large or complex to be centrally administered to support specific applications.
Gryphon has already been tested and deployed over the Internet for real-time sports score distribution at the U.S. Open, and Australian Open in tennis and Ryder Cup in golf, and for monitoring and statistics reporting at the Sydney Olympics. [4]

 2. HWLM: Heterogeneous WorkLoad Management (Total System)

Workload management, a function of the IBM OS/390 operating system base control program, allows installations to define business objectives for a clustered environment. This business policy is expressed in terms that relate to business goals and importance, rather than the internal controls used by the operating system. The IBM OS/390 ensures that system resources are assigned to achieve the specified business objectives. [17]

 3. LEO: DB2's Learning Optimizer

LEO is a comprehensive way to repair incorrect statistics and cardinality estimates from a query execution plan (QEP). By monitoring previously executed queries, LEO compares the optimizer's estimates with actual at each step in a QEP and computes adjustments to cost estimates and statistics that may be used during future query optimizations.
In practice, LEO actually learns from its past mistakes such as accelerating, sometimes drastically, future executions of similar queries, while incurring a negligible monitoring overhead on query compilation and execution. [18]

 4. SMART: Self-Managing and Resource Tuning DB2 (Middleware)

IBM will be building a SMART (Self-Managing and Resource Tuning) database into upcoming versions of DB2. This database is designed to reduce the human intervention needed to run and maintain a database. For example, the user can opt not to be involved and the database will automatically detect failures when they occur and correct them. The database will also configure itself by installing operating systems and data automatically to cope with the changing demands of e-business and the Internet.
The long-term vision is to offer customers the option of preventative maintenance or zero administration/zero maintenance to reduce the total cost of ownership. LEO is one look at the future of "SMART" databases and how they will operate more effectively. [19]

 5. Storage Tank

Storage Tank is a new file system for storage area networks that is being developed at the IBM Almaden Research lab, located in Silicon Valley in California. Major features of this system include heterogeneous file sharing, policy-based file and storage management, high performance, and scalability. This technology is currently used in IBM's Tivoli's Storage Manager Product. [6]

 6. UFiler: Facilitating Enterprise File Access/Sharing

IBM developed and demonstrated the first Web-based enterprise file system solution with the UFiler project. This solution facilitates access and sharing of files that can be geographically distributed over an entire enterprise or the Internet. It allows access to files anytime and anywhere, and files are protected through fine-grained access-control lists. UFiler desktop clients allow applications to access files stored in UFiler as if they were on a local disk. WebDAV integration is prototyped to allow Windows users to access their UFiler files through WebFolder and other WebDAV-enabled applications such as Office 2000. UFiler's automated backup ensures the integrity of user data. UFiler's back-end design includes SAN-based server clustering. Failover and load balancing among servers can be achieved without moving data. [21]


No comments: