Archive

Author Archive

Putting CMDBs On a Pedestal: In the Cloud

September 21st, 2009

From research and my recent conversations with co-workers and analysts,

A Pedestal in the Clouds:  Accelerating Your Virtualization Journey

A Pedestal in the Clouds: Accelerating Your Virtualization Journey

it seems clear that there is an increasing awareness that the existing notion of a configuration management database (CMDB) — where it is the central repository for all information about the data center and the decisions are made for its management — is an unrealistic and problematic model. 

With the sheer amount of information that we expect it to hold - and our requirement that it always be up-to-date, accurate and complete - how can we expect it to seamlessly integrate all the discovery information?  And from our myriad of domain management tools that span applications, servers, network devices and storage — and within the context of how the physical environment is related to the virtual environment?

 

 

 

In today’s data center, the rate of change alone is too daunting a task for any one database management solution to effectively handle.

However, the CMDB remains a key piece of the puzzle because it offers a single place where we can go to make critical decisions about how to optimize operations, address configuration issues, and triage problems and service outages. 

We need the CMDB — especially as our data centers continue down the road of virtualization and make their way to the private cloud.  But we need to make sure that it has not only up-to-date and accurate information, but has the “right” information and that it provides federated access to real-time information about the resources that underpin the critical business services.  Without integration from the discovery to the CMDB - and without integration between the discovery sources - this simply is not possible.

So, rather than continuously building new connectors to link discovery to our CMDB and hope that it can reconcile all the configuration items (CIs), EMC offers a new approach…Perhaps it’s not new…It’s actually well aligned with the ITIL v3 concept of a configuration management system (CMS)where the CMDB is part (a critical part) of a more modular and federated approach to configuration visibility across the data center. 

EMC Ionix Data Center Insight offers a single integration point for best-of-breed discovery across applications, servers, network devices, and storage — inclusive of virtual environments.  On top of this, it deduplicates CI data so a customer can reconcile CIs.  It provides - through a Web services interface - virtualization of cross-domain dependency maps and the applied “best practices” based CIs to EMC’s (and third-party) CMDBs.

The result is a practical approach to populating and managing a CMDB with the “right” information, such that customers can easily understand the resources that underpin the business services.  And they can visualize the infrastructure dependencies so they can more effectively plan changes and avoid inadvertently disrupting business services.  With this, customers have all the foundational components needed to build an effective configuration management system — while making the most of their existing environments. 

In my opinion, this is a real game-changer and I look forward to the continued buzz (and philosophical debate) that the announcement has already generated.

Thoughts???

Jeff Abbott

Change and Configuration, Cloud, Configuration Management Database (CMDB) Population, Dependency Mapping , , ,

Is Anyone Solely Responsible for GRC?

May 18th, 2009

The more I learn about GRC (Governance, Risk, and Compliance), the more I

Is Anyone Responsible for GRC?

Is Anyone Responsible for GRC?

question whether “GRC” focused messaging resonates with anyone. Being in marketing, and representing products that play in this “market,” I’m continuously trying to tune my message and point it at the right person. But as governance, risk and compliance gets more traction as a category, I’m not sure anyone is out there thinking:  “Hey, that’s what I do!”

With so many categories of responsibility (legal compliance, IT compliance, financial compliance, etc.), and so many layers of applicability (IT layer, business operations layer, corporate compliance layer, etc.), it’s difficult to categorize whether technologies (read: products) are addressing governance, risk, or compliance.

… or security… or regulations… or standards… or frameworks. Keep Reading…

Change and Configuration, Data Center Automation and Compliance, Dependency Mapping , , , , , , , , ,