Your SlideShare is downloading. ×
0
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Cracking the CMDB Enigma
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Cracking the CMDB Enigma

898

Published on

View the full webcast recording at http://forms.axiossystems.com/LP=227

View the full webcast recording at http://forms.axiossystems.com/LP=227

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
898
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
70
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Glenn O’Donnell Senior Analyst Forrester Research February 19, 2009 Cracking The CMDB Enigma Hint: There is no “CMDB”
  • 2. CMDB
  • 3. CMS
  • 4. Questions to be Answered <ul><li>What is the difference between CMDB and CMS? </li></ul><ul><li>What’s feasible; what’s not? </li></ul><ul><li>What is federation? </li></ul><ul><li>What good is the CMDB? </li></ul><ul><li>How will the CMS evolve? </li></ul>
  • 5. What IS this thing we call a CMDB? <ul><li>The source of information for IT decisions </li></ul><ul><li>“CMDB” is a misnomer </li></ul><ul><li>A critical element of operational discipline </li></ul><ul><li>Popularized by ITIL </li></ul><ul><li>Migrate to the ITILv3 configuration management system (CMS) </li></ul>Change Configuration Release Incident Problem Availability Service Level Capacity Financial Continuity Use Service Delivery Service Support Discovery Changes Use Use Use Use Use Use Use CMDB CMDB
  • 6. The Configuration Management System <ul><li>The CMS contains MANY “CMDBs” </li></ul><ul><ul><li>Management Data Repositories (MDRs) </li></ul></ul><ul><ul><li>Linked by federation </li></ul></ul><ul><li>Accuracy is ensured by discovery & change mgmt </li></ul><ul><li>Heavy use of metadata </li></ul><ul><li>Captures all data about IT services and infrastructure </li></ul>HR DB Servers Network Service Catalog Storage Virtual Servers CMS Known Errors Incidents Apps Data Whse
  • 7. CMDB: What’s possible and what’s not? <ul><li>Federation is coming </li></ul><ul><li>Infrastructure discovery </li></ul><ul><li>Application discovery </li></ul><ul><li>Attack small bites </li></ul><ul><li>Multi-vendor CMDB </li></ul><ul><li>CMS (but it’ll take time) </li></ul><ul><li>Federation is coming </li></ul><ul><li>Accuracy in “old world” </li></ul><ul><li>Accuracy in “new world” </li></ul><ul><li>Single-Vendor CMDB </li></ul><ul><li>“ One” CMDB </li></ul><ul><li>“ Big Bang” CMDB </li></ul>Possible Difficult / Impossible Isolated pockets of the truth are better than unified ambiguity!
  • 8. A simple federated CMDB example local data Service Catalog service A service B service C Service MDR customer service owner application A Customer MDR organization ID contact person IT_customer_rep HR DB employee ID name organization ID Application MDR client network server Server MDR manufacturer model storage Client MDR manufacturer model user Network MDR manufacturer model num_ports Storage MDR manufacturer model capacity 100% metadata mix of metadata and local data
  • 9. The CMDB “Butterfly Effect” <ul><li>All decisions are based on configuration information! </li></ul><ul><li>Good information = good decisions </li></ul><ul><li>Bad information = bad decisions </li></ul><ul><li>Decisions compound </li></ul><ul><li>Delays will prove devastating </li></ul>Punitive Outsourcing Operational Excellence Process Refinement Status Quo CMS “ Nudge” Disadvantage Delayed Start Collapse The very future of the organization rides on trustworthy information!
  • 10. Discovery Yields the Truth <ul><li>CMDB population is a big problem </li></ul><ul><ul><li>Solution: discovery and change mgmt </li></ul></ul><ul><li>Complexity is beyond comprehension … and getting MUCH worse </li></ul><ul><ul><li>Verify documented systems; trust no current data </li></ul></ul><ul><li>Automated technologies discover the truth </li></ul><ul><ul><li>e.g., network, server, storage, apps, … </li></ul></ul><ul><li>Beware of blind faith, but tools discover complex environments (the truth) better than humans can </li></ul>Difference
  • 11. CMDB process maturity 1 2 3 4 5 <ul><li>Knowledge of IT is almost entirely in human minds </li></ul><ul><li>Verifying configuration is heavily manual </li></ul><ul><li>Simple CMDB is assembled, but data is stale </li></ul><ul><li>Limited discovery is in use </li></ul><ul><li>Heavy use of discovery, but data unification is weak </li></ul><ul><li>Most discovery data is unified into a federated model </li></ul><ul><li>Early process integration is happening </li></ul><ul><li>Most discovery data is unified into a federated model </li></ul><ul><li>Broad process integration is accelerating execution </li></ul>
  • 12. CMDB becomes the CMS <ul><li>Federation will grow through 2011 </li></ul><ul><li>Process integration becomes the focus by late 2009 </li></ul><ul><li>CMS technologies become infused in mgmt tools </li></ul><ul><ul><li>Vendors will focus on CMS use, not the CMS itself </li></ul></ul><ul><li>Service design, visualization and reporting will emerge as important tools/functions based on CMS </li></ul><ul><li>CMS elements will be decoupled from other tools </li></ul><ul><ul><li>Modular MDR integration will be the feed </li></ul></ul><ul><li>Active adaptation will derive intelligence from the CMS and will update CMS immediately (mandatory!) </li></ul>
  • 13. Prepare for the new CMDB (the CMS) <ul><li>Beware CMDB misinformation </li></ul><ul><li>The “new CMDB” follows a federated model </li></ul><ul><li>Understand how tools will evolve and which foundation tools are available today </li></ul><ul><li>Much of the CMDB will change </li></ul><ul><li>Determine HOW the CMDB will be used </li></ul><ul><li>Ensure a thriving future with trustworthy information </li></ul>Information is not just data, it is useful data with intelligence! 1 0 1 1 1 1 1 1 1 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 1 1 1 1 1 0 0 0 0 1 0 1 0 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 1 0 0 1 1 1 0 0 1 1 1 0 0 1 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 1 0 0 0 0 0 1 1 1 0 0 0 0 1 1 0 1 0 1 0 1 0
  • 14. How to do CMDB right! <ul><li>Start now </li></ul><ul><li>Appoint and empower a strong CMDB leader </li></ul><ul><li>Leverage discovery and incumbent tools </li></ul><ul><li>Expect to do some integration yourself </li></ul><ul><li>Unify service-level definitions with metadata models </li></ul><ul><li>Migrate thinking to align more with ITILv3 </li></ul>Avoid the monolith! There can be no single CMDB!
  • 15. Thank you <ul><li>Glenn O’Donnell </li></ul><ul><li>+1 617.613.8826 </li></ul><ul><li>[email_address] </li></ul><ul><li>www.forrester.com </li></ul>

×