The CMDBf Cone of Silence is Lifted

I guess I need to explain why I have been silent for so long.  Partly because I've been very busy taking on new responsibilities around here.  Partly because I wanted to say something about the CMDB Federation standard, but couldn't.

Well, now I can.  Albeit I think the bylaws of this committee are still pretty restrictive, but I think I can at least comment on what we agreed to publish yesterday.

It's really pretty good.  Well, what do you expect from a blog?  Details?  Just a few - now I can make lots of entries (when I have time) and say things in smaller increments.

The specification is maybe 95% complete.  Maybe that's why it's version 0.95.  We plan to add some more details, incorporating feedback from interested parties if possible.  We also have some unfinished business (part of which is left in little TBD boxes in the draft.)

Here's the spec in a nutshell: "...the main purpose of the specification is to support systems that minimize or eliminate transferring and storing data from MDRs in federators."  MDRs are Management Data Repositories - that's basically anything that has data about configuration items.  Federators are (oops no definition in the spec) actually Federating CMDBs.  That would be CMDBs that can consume data from MDRs using the specified interfaces, and present "an aggregate view of an item or relationship, potentially using data from multiple MDRs."

So, when can you use it?  First things first.  The draft spec is on http://cmdbf.org.  Check it out.  Also, William Vambenepe has a blog about it today: http://stage.vambenepe.com.

Send me comments if you wish.  We still have to get that other 5% complete and then there's all those other opinions out there that need to be considered.  Then we will submit the spec to a standards body that you all know and some love.  Then who knows?