CMDB Reflection 1

Because, basically has completed one period of function development, therefore must continue the CMDB development work.

Recently saw a lot of CMDB related articles, but also think a lot, the back will be thinking (relatively shallow) record.

Found a lot of content is recorded on The Wiz, the time to organize into the blog.

Seven ask the CMDB http://blog.vsharing.com/xqscool/A1267069.html

The CMDB is just a system, and configuration management is a process, and the CMDB is important, but the process of maintaining it is more important. In view of the Division I, only in the beginning of the CMDB construction in accordance with the configuration management process, the construction of the end of the time began to redeploy the manpower of the configuration management process to other processes, and finally whether the configuration management or other processes are not done-the configuration management process is almost obsolete, the CMDB data is no longer accurate, So far, it is still the case that the implementation of the configuration management must include the implementation of the CMDB, the enterprise implemented one of them, will be in scale expansion, the user is more astute encounter a series of problems-such as customers want us to provide daily PC number and distribution area,   Customers want us to provide maintenance of the amount of storage and remaining storage space, storage space changes and so on, the lack of configuration management above the information provided has become empty talk. In the past, when we do configuration management always focus on surface information, such as server model, server hardware configuration and so on, we ignore the Tomcat published port, configuration file content and other such intrinsic information, so that we can only limited information on the premise of accurate data mining CMDB information value.   Although these surface information can solve the problem of the management to provide information externally, but it does not bring any value to the operation and maintenance work, is this the reason why the System/network administrator has refused to configure the management process for a long time? The cloud may be able to address these issues because the timeliness requirements of cloud services provide a requirement for overall configuration, which is to say that when you start designing a cloud service, you need to incorporate that into configuration management (perhaps not the name in the cloud). I Siyun service Bottom is a brand-new system, which also led to the status quo, the cloud itself is running well, but not to the so-called traditional operations have a glimmer of impact-the system can not be migrated, the components can not be reused, cloud band many benefits to operations, many dreams, but there are many problems can not be solved-these traditional operations,   The problem at the infrastructure level is the key to operational change. Speaking of which, I would like to talk about the age problem--age is not a problem, the concept is the problem, but the age will lead toRejectnew things, this is the concept of the problem.