Autonomic computing architecture

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.1self-configuring
           4.2self-healing
           4.3self-optimizing
           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

5.0 Autonomic Computing architecture

In an autonomic computing architecture, the basic management element is a control loop, depicted in Figure 5.1. This acts as manager of the resource through monitoring, analysis, and actions taken on a set of predefined system policies. These control loops, or managers, can communicate and eventually will negotiate with each other and other types of resources within and outside of the autonomic computing architecture [14].

Figure 5.1 An example of a basic autonomic control loop.

This collects information from the system and makes decisions based on that data and then issues instructions to make adjustments to the system. An intelligent control loop can provide functionality of autonomous computing, such as the following:

• Requesting additional processing cycles when needed.
• Installing software and upgrades.
• Restarting a system after a failure.
• Initiating backups after daily processing.
• Shutting down systems after detection of an intrusion.

These are many of the self-managing functions that we have been discussing so far. They will be available in embedded software or system tools. An alternative approach is to install control loops in runtime environments for faster responses and actions. When fully operational, control loops will hide complexity from end-users and IT professionals.

In Figure 5.1, we see the control loop is divided into two basic sub elements:
1. The Managed Element— This can be any component in the autonomous system, such as a server, a database, or a file, or it can be numerous related larger elements, such as a cluster of servers, a complete software application, or even a business unit. This means that managed elements are highly scalable. The sensors and effectors control the managed element.
2. The Autonomic Manager— This manages the collection, filtering, and reports of the data collected from the element from the sensors. It also analyzes, models if necessary, and learns about the element, gaining knowledge. With this knowledge, it can predict future situations. The planning part provides the structure the mechanism needs for the actions it takes to achieve the desired goals and objectives of the autonomous system. The planning part also uses the predefined policies that establish the goals and objectives. These policies are described in the system. The execute part of the autonomic manager provides control of the commands being accomplished. It will establish whether the commands completed their required actions.

The sensors provide the mechanisms to collect data on the state of the element. To trigger the sensors will require a "get" instruction—for example, "get the information of the customer database"—or for the element to change in a material fashion, such as volume or time. An example of the last trigger would be "get the transaction information when the database completes the daily update."

The effectors are the mechanisms that change the state of an element. In other words, they act or alter the configuration of the element from the data provided from the sensors. The effectors are a set of software commands, or application programming interfaces (APIs), that alter the element's configuration.

Previous Chapter

Next Chapter