Cloud CMDB experience sharing – analyzing the design process of the CMDB

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M02/89/DB/wKioL1ggE2ny9XGUAADzBOnP6ko566.jpg "style=" height : auto;vertical-align:middle;border:0px; "title=" 0.jpg "alt=" Wkiol1gge2ny9xguaadzbonp6ko566.jpg "/>

As the core of IT management, CMDB has gradually become a hotspot in the implementation of system management projects. In many cases, the deep application of ITIL has been challenged due to the neglect of the CMDB factors. At the same time, because the CMDB is the concentration of IT management information, the CMDB is also an important tool and means.

In the process of the CMDB landing, it is important to note that the CMDB project is not a simple software installation process, but a comprehensive process of consulting, training, implementation, optimization and close integration, involving platform tools procurement, consulting services, implementation services, training, and even expansion of development and other content. At the same time, a successful CMDB project can not be done overnight, but a gradual, continuous development process, the need for enterprise follow-up and continuous improvement of services.

Broad-Pass software in 2004 began the ITIL landing attempt, and independent continuous research and development accumulation, the formation of the CMDB as the core operation and maintenance solutions, these two years for the General administration of customs, China Airlines, Railway Corporation, Zhejiang Merchants Bank, Heilongjiang Rural credit and other enterprise users, providing professional CMDB consulting design and landing implementation services, Throughout the process, the author deeply realized that the success of the CMDB project, the focus is on the top-level design of the CMDB model, the following for the CMDB design process in-depth analysis.

• Understand corporate policy

Enterprise Policy, is the Action Guide and common Programme of enterprise management, it makes the enterprise in the cognition unify, reduces the unnecessary communication cost, and causes the enterprise in the process execution the multiplier effort. For the building of a CMDB, there are two main types of policies that need to focus on:

• Macro policy: mainly involves the guidance and direction of the IT department, the goal is to form a unified understanding of the IT department from top to bottom, which will benefit the success of the project.

• Operational policies: mainly related to process objectives, people, inputs, outputs, activities and KPIs (key performance indicators) and other elements as well as the coordination of processes, information interaction between the guiding principles, the goal is to enable the process under the guidance of the policy in a sound and effective implementation.

• Determine the scope of the configuration item management

• To determine the CI width and depth, it is recommended that you follow these guidelines:

• Need for enterprise IT services (why implement CMDB)

• The need for IT management of relevant laws and regulations

· The need for it inventory and asset management

• Requirements for the service catalog

• Level of enterprise IT service management (how much can be achieved based on current level of management)

• There are no management rules and regulations related to configuration items

• How many people can participate in management and maintenance

• There is a set of landing change procedures to maintain the necessary CI items

• Enterprise CMDB operation and management costs (how much labor costs can be invested in the latter to maintain and manage)

• To ensure the accuracy of CI items and the freshness of form data, configure the human cost of item maintenance

• Inter-departmental internal communication costs

• Identify the CI life cycle

The ITIL specification believes that CI's life cycle is the whole process from the receiving of CI to the final scrap exit, but in the concrete implementation process, due to the differentiation of the process management subject, different projects will be divided and defined the CI life cycle differently, mainly for the following two questions to determine.

• When to be born? (Identify CI and record to CMDB)

• When to extinguish? (delete the CI record)

• Build a CI model classification that matches your users

Defining Configuration item properties (a Principle + a set of structures)

• One principle: "Fine and not much". If we include a large number of configuration items or attributes into the CMDB, there will be a lot of information that needs to be maintained, which undoubtedly adds to the cost. Conversely, if the property is too small, the maintenance work is reduced, but the effectiveness of the CMDB is greatly reduced. Therefore, "refined but not much" is our balance point, the ' fine ' is mainly embodied in the practical significance for the enterprise.

• Set of structures: we can usually divide the attributes of a CI into five major sources

Model Classification Design Sample:

To determine the properties of a CI item

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M00/89/DE/wKiom1ggE3ORZbsjAAEOxfpQ2B8037.jpg "style=" height : auto;vertical-align:middle;border:0px; "title=" 5.jpg "alt=" Wkiom1gge3orzbsjaaeoxfpq2b8037.jpg "/>

For each CI in the model of the properties of the research, according to the actual needs of the user to adjust, expand or modify, including: What type of property items are reasonable (easy to display and maintenance), users need to provide what information, such as: dictionaries, default values and other information. This process also follows the principle of "fine and not much".

Attribute Design Sample:

Define the relationship between CI items

650) this.width=650; "src=" http://s1.51cto.com/wyfs02/M00/89/DB/wKioL1ggE33RwHExAAN97XE2ZZU669.jpg "style=" height : auto;vertical-align:middle;border:0px; "title=" 6.jpg "alt=" Wkiol1gge33rwhexaan97xe2zzu669.jpg "/>

All configuration items have the meaning of existence, and their intrinsic relationship is one of the important value of the CMDB, the relationship is clear, operations and maintenance personnel can accurately find the relevant entity resources, when the failure can quickly locate the source of failure and its scope of influence, so as to quickly solve various hidden dangers.

There are two common ways to define a configuration item relationship:

• Top-down-usually requires the enterprise to clarify the list of services provided externally, and then comb based on the service catalog according to the order of "Business Service →it Service →it system →it Components"

• Bottom-up-upstream, starting with the internal IT component relationship, and then gradually mapping it components to IT services

CMDB Configuration Item Relationship Design sample (take a business system as an example):

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M00/89/DE/wKiom1ggE4jzobH9AANjS-uvgDI015.jpg "style=" height : auto;vertical-align:middle;border:0px; "title=" 7.jpg "alt=" Wkiom1gge4jzobh9aanjs-uvgdi015.jpg "/>

In the design diagram, a complete display of all the relevant configuration items of a business system, analyzed as follows:

• Logical Relationships--you can see what middleware the business system uses, database users, instances, and table spaces, which operating system is running, what IP addresses are used, etc.

• Physical relationship--can be learned that the business system installed on which PC server, the PC server is connected to the network through which port of the switch, while the PC server and storage how to connect the PC server in which cabinet and computer room, and the PC server is through which circuit breaker and UPS power supply, etc.

The above information for operation and maintenance personnel, can more clearly grasp the normal operation of the business system support points and the context, so as to control the overall situation.

Conclusion:

CMDB design process is a complex and user-interactive process, in this process need to fully understand the concept of the CMDB and related principles, we need to maintain the future of the CMDB may bring the risks and costs to the user to do a good job of communication, so that the user to go to the discretion, consideration and planning, In order to avoid the failure of the CMDB project, it can help the user to optimize and perfect the CMDB management system, define the personnel role, and combine the change process to maintain the accuracy and freshness of the configuration, and help the users to maintain the CMDB, and give full play to the value of the CMDB.

Author's introduction : Cheiatao, the author of this article, is an excellent cloud software

This article is from the "excellent cloud dual-state Operations" blog, please be sure to keep this source http://uyunopss.blog.51cto.com/12240346/1870194

Cloud CMDB experience sharing – analyzing the design process of the CMDB