Original link: https://wiki.eryajf.net/pages/4bcf72/
Our operation and maintenance team has brought together a group of outstanding young people full of ideas. In every weekly meeting, after we finished our daily work communication, we would always jump out of the present moment and brainstorm nonsense. In these seemingly idle communications, we conducted a lot of discussions on operation and maintenance specifications and best practices, and the more discussions we conducted, the more we were able to discover a problem, whether it was for a whole process (referring to a project) The implementation of the specification constraints on the naming of the entire life cycle), or the maintenance of the host list in the application dimension of the publishing platform, cannot avoid a CMDB platform that can truly solve the pain points of operation and maintenance. Note that an attributive is added in front of the term CMDB to really solve the pain points of operation and maintenance. In fact, before this, we have not done the construction of CMDB platform, but due to our lack of understanding of this concept in the past, we completely handed it over to the operation and maintenance development students, and the CMDB developed according to some of his experience ideas, but It is always difficult to actually implement it in actual operation and maintenance production. In short, the CMDB platform has been done, but it has failed.
This article is transferred from: https://wiki.eryajf.net/pages/4bcf72/
This site is only for collection, and the copyright belongs to the original author.