Dear Dr. Cloud,
My company was leading edge a few years back in adopting a CMDB – and in truth, it really did help. It makes sense to keep configurations and inventories in one place. If we were a manufacturer, having this core inventory system would be critical to our business, and for IT, it’s no different. But now, the new cloud team is building out a new service environment – and I worry about the centrality of our beloved CMDB. Thoughts?
--Central in Chicago
This is a very valid concern. How central is something that is separated into chunks? Sure, you can build a virtualized environment CMDB, but how does that facilitate the central source of truth? Then, maybe add a cloud services CMDB, and an external cloud services CMDB, and soon enough you’ll have to check in 10 places for a patch or config change.
So, the best practice is to maintain that central source of truth in a central CMDB. So, that way, the same service can move from physical to virtual to private cloud and public cloud – and remain consistently tracked. There really are 2 ways of doing this… either opt for a solution with an integrated CMDB, or federate the CMDBs centrally to ensure you can treat them as a centralized CMDB. Either way, cloud services and the cloud service catalog should be included.
This is one of many wonderful examples of not tossing out the baby with the bathwater. We learned a lot about IT management in the past 20 years… Let’s ensure the best of it makes it to the cloud.
Dr. Cloud answers cloudy questions on Tuesdays (or when he's late, Wednesdays). To reach the good doctor, email firstname.lastname@example.org