CMDB Model Design 2
Http://blog.vsharing.com/xqscool/A1275233.html
It is estimated that all two of the broken children are a bit dizzy, and I'm a little dizzy. Two comparisons. 1th, the Properties section has added dynamic content. That's the question I've been thinking about-after all, we've been monitoring for years, and monitoring data has been kept in the CMDB for a long time. Because the CMDB uses more of the current state, if you want to record performance data, you need to record the historical situation, so that the CMDB is packaged with monitoring. I'm still just providing an interface, and the CMDB can call it. Furthermore, the CMDB has these properties and must have a data source. Therefore, the introduction of the interface to ensure that there is dynamic Data monitoring, no monitoring and no dynamic data. In addition, although the history of the data of the CMDB should be recorded, but this and dynamic data is two different, do not make a mistake. 2nd, the CMDB model replaces "action" with "business". It's a tree-shaped structure, so it's not a big difference. In fact, the basic properties of the CMDB can only contain the other three blocks, that is, attributes, classifications and relationships. Regardless of the "action" or "business" these two, although said also must not be less, but from a certain point of view is not necessary, of course, the key to see you from what perspective, from the perspective of business must have "business", from the perspective of operations must have "action". 3rd, after the introduction of the business, the process of implementing the CMDB is top-down, not before the bottom up. From business initiation, to it, then to relationships, and finally to attributes. and through the presentation of this business architecture, the company will be able to confidently implement the CMDB from top to bottom. 4th, after the introduction of the business, the impact of the CMDB's failure directly can be seen in the specific impact on the business. 5th, service-related content, service levels are replaced with service catalogs, and their content is migrated from the CMDB section. But in fact I think the two are essential: service levels define what services are provided, and the service catalog defines the specific service items that are provided (the project is further divided into action sequences). 6th place, so that when the real homework, we can understand the impact of CI at the service level. looked at the second model design, the personal feeling of CI model design, CI can have more dimensions, but how to balance the design and use of complex problems? The most red effect is very good, but it will bring early development and implementation of the difficulty level.