The trouble of definition at a discussion meeting of a system monitoring, I casually raised a question: "How to define a system?" The answer is a variety of results, and the meeting is irrelevant. Why ask this question, because some colleagues feel that a system is relatively large, down into subsystems, components, etc., to the top of the business group. Sometimes a careful look, what business group, is obviously a big system just. Of course, I casually say that I do not have a clear definition of the problem. What I'm trying to say is that these definitions, including systems, components, subsystems, and so on, we never thought of--the process is the same, the difference is, we think about it, but just make it work, the definition is not clear. These are the kind of things that imaginative achievement here inexpressible, which leads to external companies often splitting a system that we "think" into multiple systems for charging ... Of course, this question is still clear and I have raised it, but we all think that it is not necessary to understand the problem. The CMDB classification is similar to the above, as is the classification of the CMDB. Let me give you an example: Someone asked why the server is not a network device ... I think this question is still not very good to answer. CMDB classification, it is best to be exhaustive but not cross, you can not let a CI belong to two categories at the same time. ----------interrupted, I ask another question, how to define CI, what is CI, what is not? ----------I need to review the categories that are now being collected. Environment:Building, computer roomPower Equipment: Distribution cabinets, header cabinets, UPS, PDU, cabinet air-conditioning equipment: air-conditioning Fire equipment: Now No, there will be some access control equipment: Now, there will be network: line: Internet lines, WAN lines, LAN line resources: IP, domain name, data interface network equipment: routers, network switches , wireless devices, security Equipment Network equipment accessories: Now No, there will be communications: communication equipment: Voice Device Virtualization: Virtual resource pool, virtual machine computer-Related: Computer machine: PC server, blade server, small machine, medium-sized machine, mainframe, industrial computer accessories: Now No, Future storage devices: disk array, centralized storage, tape library, fibre switch-specific devices: Blade chassis Other Devices: No, there will be software in the future:Business Group, system clusters, application clusters, database clusters, business system middleware: Tomcat, IIS, Apache, Jboss, Weblogic, WebSphere DB instance: DB2, Sybase, Oracle, MySQL, MSSQL The total sense of the physical resources of the building and the room should not be placed here, although it is really mutual entities, but the properties seem different, so first removed. ----------continue to----------CI is CI, the definition of business system, and the specific service-linked place in the service management part of the processing. For CI, there are only two states, normal and faulty, as the difference between numbers 0 and 1. Just thinking about the percentage effect on the transmission of the problem, this piece of content thrown into the service to deal with. CI is recorded in the static information, dynamic information from the monitoring, display when the interface can be called. Classification is linked to attributes, and certain classifications will have a specific set of attributes. Attribute definition--attribute set definition--properties and classification hooks after consideration, I think that the service model should be built from the basic service (that is, with a CI directly related to the minimum service), in service management should be able to introduce service-related concepts, which can simplify the function of the CMDB itself. The business model is the direct display of CI and services. The CMDB is a relatively dangling concept and cannot make it worse with overly complex features.
