Comments on: CMDB in the Cloud: not your father’s CMDB http://stage.vambenepe.com/archives/1527 William Vambenepe's stage Tue, 07 Feb 2012 23:33:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Mark Mszanski http://stage.vambenepe.com/archives/1527#comment-927 Mark Mszanski Tue, 15 Feb 2011 20:38:39 +0000 http://stage.vambenepe.com/?p=1527#comment-927 William, I am just reading this information and agree completely with your analysis. Evolven Software provides the ability to react to dynamic, virtualized changes as the Automated COnfiguration Control Solution - About time we had a next generation solution of CMDB. The CMDB was a good start but rigid and not designed to handle the next generation of IT - IF your interested we can show you what we mean and would love your input. Sincerely, Mark Mszanski EVP US Operations Evolven Software Inc. MarkM@Evolven.com www.evolven.com 908.500.4087 William,

I am just reading this information and agree completely with your analysis. Evolven Software provides the ability to react to dynamic, virtualized changes as the Automated COnfiguration Control Solution – About time we had a next generation solution of CMDB. The CMDB was a good start but rigid and not designed to handle the next generation of IT – IF your interested we can show you what we mean and would love your input.

Sincerely,

Mark Mszanski
EVP US Operations
Evolven Software Inc.
MarkM@Evolven.com
http://www.evolven.com
908.500.4087

]]> By: Coté's People Over Process » Pouring new wine on old problems – IT Management & Cloud Podcast #75 http://stage.vambenepe.com/archives/1527#comment-926 Coté's People Over Process » Pouring new wine on old problems – IT Management & Cloud Podcast #75 Fri, 02 Jul 2010 17:53:05 +0000 http://stage.vambenepe.com/?p=1527#comment-926 [...] to be or not to be – William V. has a nice round-up of the sentiment. What’s going on with CMDBs, asset databases, discovery, topology mappings, [...] [...] to be or not to be – William V. has a nice round-up of the sentiment. What’s going on with CMDBs, asset databases, discovery, topology mappings, [...]

]]> By: Coté's People Over Process » Pouring new wine on old problems – IT Management & Cloud Podcast #75 http://stage.vambenepe.com/archives/1527#comment-1069 Coté's People Over Process » Pouring new wine on old problems – IT Management & Cloud Podcast #75 Fri, 02 Jul 2010 17:53:05 +0000 http://stage.vambenepe.com/?p=1527#comment-1069 [...] to be or not to be – William V. has a nice round-up of the sentiment. What’s going on with CMDBs, asset databases, discovery, topology mappings, [...] [...] to be or not to be – William V. has a nice round-up of the sentiment. What’s going on with CMDBs, asset databases, discovery, topology mappings, [...]

]]> By: Donald F. Ferguson http://stage.vambenepe.com/archives/1527#comment-925 Donald F. Ferguson Wed, 16 Jun 2010 18:54:57 +0000 http://stage.vambenepe.com/?p=1527#comment-925 Reasons (1) and (2) do not seem to render CMDBs irrelevant in a cloud/virtual environment. CMDB data models will always need to evolve, support configuration/customization/extension/modernization/etc. Reasons (3) and (4) is also not compelling. First, ETL is only one of many ways that CMDBs can discover and update information. Most modern CMDBs support other more dynamic, event based models. Second, your comments about the existence of APIs and direct access to information replacing discovery/guessing is also correct. I think a major issue is the inherent assumption that CMDBs "know everything." I think *MDBs in the cloud world are going to have to have capabilities to only discover things/configs/etc for which there is a need to obtain the information. This approach is more analogous to a federated database, in which the information gathering occurs when a query arrives. The federated DB does not aggressively try and get information. I did not follow your analysis of (5). I do agree, probably because of my background, that application centric management is the way to go, although I have an odd view. WRT to configuration versus monitoring, I do not see any intrinsic issue. Configuration, Definition, Monitoring, Operations, ... are different facets in managing information for IT things. CMDBs would have had to and were already expanding to encompass more facets than configuration. Reasons (1) and (2) do not seem to render CMDBs irrelevant in a cloud/virtual environment. CMDB data models will always need to evolve, support configuration/customization/extension/modernization/etc.

Reasons (3) and (4) is also not compelling. First, ETL is only one of many ways that CMDBs can discover and update information. Most modern CMDBs support other more dynamic, event based models. Second, your comments about the existence of APIs and direct access to information replacing discovery/guessing is also correct.

I think a major issue is the inherent assumption that CMDBs “know everything.” I think *MDBs in the cloud world are going to have to have capabilities to only discover things/configs/etc for which there is a need to obtain the information. This approach is more analogous to a federated database, in which the information gathering occurs when a query arrives. The federated DB does not aggressively try and get information.

I did not follow your analysis of (5).

I do agree, probably because of my background, that application centric management is the way to go, although I have an odd view.

WRT to configuration versus monitoring, I do not see any intrinsic issue. Configuration, Definition, Monitoring, Operations, … are different facets in managing information for IT things. CMDBs would have had to and were already expanding to encompass more facets than configuration.

]]>