This is the 5th of a series of posts dealing with the concept of CMDB Federation. Application #3: CMDB Federation the Dynamic View of Existing Data The third definition of federation is much like the one we just addressed and struggles with many of the same challenges. However, in this application a central CI record is not actually created with a replication of chosen data from distributed sources. This model is based on the concept of creating a dynamic view of a CI by pulling from existing data sources each time a request is made.

This is the 3rd in a series of posts dealing with the concept of a Federated CMDB There are three traditional objections to this first application of the word federation:

 

1. • The database would be huge and performance would be an issue
   • The ITSM processes don't need all of that data so why would I mess up the CMDB with information these processes don't require.
   • The cost of this consolidation would outweigh the benefit

This is the 2nd in a series of posts dealing with the concept of a Federated CMDB Since I am obviously biased I will start with the application I believe to be the appropriate use of Federation.

The emerging capability of federating data sources is the biggest boon and the largest potential pitfall that has arisen for the discipline and process called Configuration Management! On the surface this may appear to be a completely contradictory statement. However, as is the case with all good intentions it all comes down to the application. First and foremost, database federation is an absolute must for a successfully Configuration Management Database (CMDB) implementation.

In keeping with the last post that challenges the artificial separation we have placed between IT and the business I would like to share a personal experience.

Many books and papers have been written on the subject of IT and business alignment. While not to downplay this important topic, one needs to ask why we are having this conversation. You don't see the equivalent concerns about HR and business alignment, Finance and business alignment or Engineering and business alignment. The very fact that these are relevant topics today tells us something about the current level of maturity of our industry.

It is the nature of ideas, structures and functions to mature and change over time as the needs placed upon these concepts evolve. This is true of the term IT Governance. The IT industry as a whole is undergoing a transformation from an industry largely shaped by the leadership and colorful personalities of individual IT executives and vendors, to one that is becoming more defined, homogeneous and regulated. Dare I say “Utility”?

Everyone needs a hobby!
Mine is deemed interesting by many and bizarre by others.

You see my family and I use multi billion dollar military satellites to find Tupperware containers hidden in the forest full of odd trinkets you may find at a dollar store.

Hello All This blog is dedicated to making sense out of the shifting landscape in which we in IT find ourselves. Just when we thought we had a good handle on managing technology, the job we thought we knew is being threatened by strange acronym's like CMMI, COBIT, ect.. Suddenly the rules have changed and we are not sure why. The goal of this blog is to offer an element of sanity and logic to what appears to be chaos. From the wisdom of the Hitch Hiker's Guide to the Galaxy never go anywhere without your towel and DON'T PANIC