The prototype of the CMDB started on the 25 th has basically been completed in the second draft.
The first draft is purely a data structure design. Manually add data for mental verification. The first draft only configures the modeling data structure, and does not involve the configuration instance.
The second draft is a prototype verification of the data structure and Preliminary Exploration of the required technology. The process has been repeated several times because it is a field of thinking and writing.
Here we record some simple ideas:
What is configuration management? What is the essence of Configuration Management? Configuration Management: In the concept of O & M, it is the process of collecting and managing all external variables (information that can be adjusted and changed) related to running. It is inseparable from O & M activities such as changes, events, problems, and launch. It contains a wide variety of content, including hardware and software information. As long as the operation is related, the O & M activities may be affected and can be changed by the O & M activities, it can be recorded as configuration. Typical configurations include: host type, host vendor, Host IP address, configuration file, Kernel Parameter, CPU type, CPU serial number, and so on. Usually it can be composed of configuration items-Configuration value pairs: for example, Host Name
: = Myhostname host vendor
: = HP is more complex. The configuration can be structured, for example, host ID.
: = Myserver1 Host Name
: = Myhostname Nic 1
: = Intelip address
: = 192.168.0.1mask
: = 255.255.255.0 Nic 2
: = Wanip address
: = N/amask
: = N/A of course, the application is configured, and usually appears in the configuration file. XX app
: = Xxapp. ini configuration management is not configured for configuration purposes. It is a secondary system and serves other management activities. Configuration Management alone has no significance (maybe it can be used for asset management ). Considering configuration management, you must consider changes, events, problems, and other activities. This is the essence of configuration management and the most difficult point of O & M management. Simply put, if a change involves modifications to the configuration, which configuration is modified, the scope of impact, and whether the configuration is complete/consistent (no missing or inconsistent items) you should find the answer from configuration management. Whether or not the O & M Unit has established formal Configuration Management, as long as the change control is implemented, there must be conscious/unconscious configuration management. To help with impact analysis, configuration management requires modeling and analysis of existing configuration projects, that is, creating a three-dimensional configuration model, which is the essence of configuration management. Where is the problem with configuration modeling? It is easy to configure and model a specific system for a specific purpose. For example, it is easy to model the network of a host, that is, host/Network/NIC configuration. Each layer has a specific configuration item. The following is a simple model: Host layer: Host Name: Network 1: Guest network 192.168.0. * Nic 1: intelmac: PCI slot Network 2: Remote network 10.0.0. * Nic 2: intelmac: PCI slot: therefore, the impact analysis of this configuration change is easier to perform in layers, for example, the impact scope of NIC change, IP address change, and host name change (for the impact on this host, the network to which the host belongs is not) is easy to determine. If you need to analyze the impact of the entire network, you need to model the entire network. For example, if it is determined that a network is composed of two hosts, one switch and one firewall, and the topology is determined, then after modeling, the network configuration is quite easy to describe, it is also easy to conduct impact analysis. It is obviously very difficult to try a model that applies to any network structure. Therefore, the question of configuration modeling is how to easily create a model that describes the existing system. That is to say, the first task of configuration management is configuration model management, followed by configuration item management. The configuration model is used to describe the system structure, and the configuration item is used to configure model instantiation. For example, the configuration model can be described as XX type network: Network Information (IP segment, purpose, etc) the host type contains the composition information of the firewall type (including the number of hosts, vswitches, and interconnection modes ). The component information is difficult to use and can be described by a short program (SCRIPT. Configuration management can be instantiated Based on the configuration model to become a configuration item. The Configuration Model + configuration item can easily provide reliable impact analysis for change control. The two-day work summary learned about CLR/C ++ programming and tried to create a dynamic interface. MySQL encapsulation, seamless integration of Python, and the use of C ++/Python data structures .. Net CLR is a good thing. MySQL is also good. The configuration model management is implemented, and the model relationship definition and implementation of inheritance, reference, and inclusion are completed. The configuration project management is implemented, and the configuration model is instantiated. When the configuration item is instantiated, the inheritance adopts the included implementation method. Try to change the traditional habit of operating directly in the database by load to the memory, completing the operation, writing SQL files, and executing SQL file submission. The next step is to start the third draft. Objectives: 1. Rebuild the current implementation code and clear the model-instance from the architecture. 2. Take the complex configuration model as an example to implement configuration model = instantiation, impact analysis, and other operations. 3. Configuration Management introduction status, online --> checkout for change --> check in for review check --> change online --> online verification after launch --> online
