What a load of .... Computerworld: How Much Is 'Just Enough' for a CMDB?
This article has been podcast in slightly modified form.
Antonio gave us an interesting link in a recent comment. Excuse me folks, but what a load of crap it is.
"A just-enough CMDB should provide a full picture of the following:
All technology components related to the specific service.
The relationships and interdependencies among those components, including relationships between logical and physical components.
Context from a service perspective -- role-based views of the technology that consider the requirements of the audience.
State, in terms of availability, business performance and technology performance.
Governance -- automated management of what is currently running versus what should be running and was last approved.
Management of service through defined, monitored and automatically managed service levels.
It is important to note that a just-enough CMDB must include definitions of services and information on state and automated governance/management, all frequently updated."
Dear God, what isn't in there? How does "just-enough" differ from "everything"? This is "top-down" alright: "top-right-down-to-the-bottom".
This is the kind of platitudinous claptrap peddled by vendors and their analyst sycophants to lull people into adopting their lunatic ideas (and buying their products and consulting). Make it sound easy, obvious and do-able.
"less is more ", "top down", "just enough", "relationship-discovery tools", "design and implementation can be made much easier", "critical services".... Crap.
If you drill down far enough to find everything listed here for just one service, the complexities and inter-dependencies of a modern IT environment mean you will have found a fair proportion of your entire environment. And wasted plenty of time and money doing it... if you ever get there.