Hype and Bubble Burst for the CMDB Finally - Fall of the Dreaded 4 Letter Word!
They fall as fast as they rise. What is the "value" of static data from the past in a database? Outside of tracking how many, cost and depreciation value, I cannot think of a single thing. Although as I watch the Nats play the Mets, baseball is all about metrics and stats from the past without relative value for the novice watcher. Number of homeruns in relationship to how many others have hit or the most ever hit brings a whole new perspective. It's the relationship and relativivity of the metric that brings "value" by creating "information".
The topic of CMDB can bring holy war, lengthy debate, but tonight I am going to be short and sweet with luck and slightly controversial.
Rise of the CMS
Within the Novell BSM solution we speak in terms of the Configuration Management System (CMS) accessing data at it's source as data in memory (or federated in real-time) because the value is joining the data metrics in a model providing the relationships that illustrate "value" through the creation of "information". Now the metrics are put in relative terms creating "information" by which to take action upon in real-time, rather than a static repository to report against after the fact. These metrics can now be "weighted" in relationship to one another and overall priority of real-time events/status is determined as an overall picture of information determining the true business impacting priority and thus reaction.
Duplicate data is often a question and the CMS reconciles the sources of data illustrating mismatched data and/or using data from the "trusted source" that manages the specific metrics accurately. The CMS does this at the time of integration automating the building of the initial models providing the opportunity clean-up data or merely use the data from the trusted source.
Governance to Standards is managed with a "static" snapshot of the model that is automatically compared against the real-time, operational model of what is "live" in the environment illustrating differences between last approved and operational. This leads to one of two things: unapproved change and the need to back out or a change that was not completed with the update to the approved model governing adherence to approved changes. This same automatic synchronization is also often performed in developing standard configurations.
In the end, the database of static historical data has no "value". It is the CMS that creates real-time "value" with "relationships" turning "data" into "information" from your myriad of data sources, automating the models and the management of the models and environment.
Dawn of a New Day and the CMS for Real-Time Value and Actionability! Thoughts?
Control Your Infrastructure from Physical to Virtual to the Cloud!
Shameless plug for my very dear friend and Forrester Analyst Glenn O'Donnell who wrote the book on the subject:
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.