Update virtual components in cloud computing environments to dramatically improve monitoring efficiency

Itmfve (IBM http://www.aliyun.com/zixun/aggregation/13966.html ">tivoli Monitoring for Virtual Environnement) is an SCM Core components to monitor the implementation of virtual components in the cloud architecture. This article focuses on deployment and integration of Itm/itmfve and TADDM (Tivoli creator Dependency Discovery Manager) to show you how to implement updates to virtual components in a virtual environment (such as: Virtual machine creation, deletion, Move), thus greatly improving the monitoring efficiency.

We all know that cloud computing is already an irreversible trend in the IT industry, although the cloud is still in its infancy, but it also represents more opportunities and challenges. IBM launched Cloud computing Services (smart Cloud) and related products SCF (smart Cloud Foundation) by the end of 2011. This portfolio is designed to help businesses and customers quickly deploy private clouds or transform their existing virtualized systems into more efficient cloud computing platforms. SCM (Smart Cloud monitoring) is an important part of SCF, whose primary goal is to provide a complete solution for monitoring the health of the cloud and virtual environments. IBM Tivoli has a major advantage in traditional data center management, and SCM is bundled with ITM (IBM Tivoli Monitoring) and Itmfve (IBM Tivoli Monitoring for Virtual Environnement), which makes SCM is more efficient at monitoring cloud and virtual environments. To extend the monitoring scope, SCM integrates TADDM, TPC, Omnibus, System p Director, enabling SCM to dynamically perceive changes in virtual environments such as VMware, Hyper-V, IBM System p, and so on.

Overview

Based on the above background, this article will focus on the integration of Itm/itmfve and TADDM (Tivoli creator Dependency Discovery Manager) to describe how they implement virtual environments in SCM, such as the creation, updating, Delete, and so on.

Figure 1 shows the three-tier architecture of the current SCM:

Figure 1. SCM Solutions Overview Map

In this schema, ITM is located at the SCM server layer. ITM provides enterprise users with a centralized monitoring solution that detects bottlenecks and potential problems in the enterprise environment by managing the performance and availability of the enterprise's distributed systems and applications, and automatically responds to events to help manage business applications. The ITM agent is installed on a system/subsystem that requires data collection and monitoring. Its role is to collect data for monitoring and to transmit data to the server (Hub tems or Remote tems) to which it is connected, and the agent compares the monitored data values with the set thresholds, if the current value exceeds the threshold, The agent passes the alert information to tems. The ITM agent belongs to the SCM agent layer. For virtual Environment monitoring (VMware, Hyper-V, IBM System P, etc.), ITM provides itmfve monitoring agent, responsible for collecting virtual environment performance data for ITM management. While Itmfve provides the core monitoring capabilities for SCM, SCM is broader. To make the SCM more competitive, you must take full advantage of Tivoli's monitoring area to extend the scope of SCM monitoring by embedding or integrating other Ibm/tivoli products. TADDM is used to extend the monitoring scope, providing robust automated application mapping and discovery capabilities to build an application, configuration, and dependency list to help organizations understand the impact of change. In the SCM architecture, TADDM provides SCM with detailed configuration and change management of virtual environments, and SCM utilizes TADDM sensors to detect a wider range of virtual environment components.

TADDM provides an external proactive Updates interface based on the Tivoli general data model. This article focuses on the integration of Itm/itmfve and TADDM, through ITM Workflow (Workflow) to TADDM proactive Updates interface to send requests to implement the dynamic update TADDM view. The deployment of the entire SCM environment is not covered in this article.