<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: An Open Source CMDB</title>
	<atom:link href="http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/</link>
	<description>One foot in the muck, the other in utopia</description>
	<lastBuildDate>Tue, 22 May 2012 15:13:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: dlog</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-340661</link>
		<dc:creator>dlog</dc:creator>
		<pubDate>Thu, 29 Oct 2009 09:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-340661</guid>
		<description>You should add i-doit.org to the existing ones as it is currently the best open source CMDB </description>
		<content:encoded><![CDATA[<p>You should add i-doit.org to the existing ones as it is currently the best open source CMDB </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rg</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-196064</link>
		<dc:creator>rg</dc:creator>
		<pubDate>Thu, 03 Jul 2008 05:42:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-196064</guid>
		<description> &lt;a href=&quot;http://www.i-doit.org&quot; rel=&quot;nofollow&quot;&gt;http://www.i-doit.org&lt;/a&gt;  
Big CMDB-Tool written in PHP </description>
		<content:encoded><![CDATA[<p> <a href="http://www.i-doit.org" rel="nofollow">http://www.i-doit.org</a><br />
Big CMDB-Tool written in PHP </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jinxfei</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-111746</link>
		<dc:creator>jinxfei</dc:creator>
		<pubDate>Sun, 09 Dec 2007 03:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-111746</guid>
		<description>htt://www.onecmdb.org
This is a simple cmdb writen in java.</description>
		<content:encoded><![CDATA[<p>htt://www.onecmdb.org<br />
This is a simple cmdb writen in java.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cote</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-110690</link>
		<dc:creator>cote</dc:creator>
		<pubDate>Fri, 07 Dec 2007 15:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-110690</guid>
		<description>Thanks for the re-reply, Marv. Ideally, what I&#039;d like to see in an open source ref. impl. is a project that coincided with the development of the spec as much as possible. Why during? Because I&#039;d rather see coders encounter errors in coding to the spec and feed that back into the spec as much as possible. Also, it&#039;d be good to have the whole process of developing the code in the open for others to look at when doing their own implementation - as you nicely reference back to the SNMP impl of yore.

Ideally, the ref. impl. would be production ready - if not in the fine print, then in the code at least. Also, it&#039;d be key for it to be very permissively licensed, under the BSD, Apache, or like so that people could yank the code to use on their own or start for their own projects, open or closed source.

That&#039;s just a quick, off the top of my head response. I&#039;m of course happy to think out-loud more ;)

Additionally, you might consider coming down to &lt;a href=&quot;http://barcamp.org/BarCampESM&quot; rel=&quot;nofollow&quot;&gt;barcampESM &lt;/a&gt; this Jan in Austin, TX to talk with &lt;a href=&quot;http://barcamp.org/BarCampESMAttendees&quot; rel=&quot;nofollow&quot;&gt;a wider audience&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Thanks for the re-reply, Marv. Ideally, what I&#8217;d like to see in an open source ref. impl. is a project that coincided with the development of the spec as much as possible. Why during? Because I&#8217;d rather see coders encounter errors in coding to the spec and feed that back into the spec as much as possible. Also, it&#8217;d be good to have the whole process of developing the code in the open for others to look at when doing their own implementation &#8211; as you nicely reference back to the SNMP impl of yore.</p>
<p>Ideally, the ref. impl. would be production ready &#8211; if not in the fine print, then in the code at least. Also, it&#8217;d be key for it to be very permissively licensed, under the BSD, Apache, or like so that people could yank the code to use on their own or start for their own projects, open or closed source.</p>
<p>That&#8217;s just a quick, off the top of my head response. I&#8217;m of course happy to think out-loud more ;)</p>
<p>Additionally, you might consider coming down to <a href="http://barcamp.org/BarCampESM" rel="nofollow">barcampESM </a> this Jan in Austin, TX to talk with <a href="http://barcamp.org/BarCampESMAttendees" rel="nofollow">a wider audience</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zenoss Blog &#187; Zenoss Newsletter - November 2007</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-108724</link>
		<dc:creator>Zenoss Blog &#187; Zenoss Newsletter - November 2007</dc:creator>
		<pubDate>Tue, 04 Dec 2007 18:54:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-108724</guid>
		<description>[...] People over Process: An Open Source CMDB [...]</description>
		<content:encoded><![CDATA[<p>[...] People over Process: An Open Source CMDB [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marv Waschke</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-105798</link>
		<dc:creator>Marv Waschke</dc:creator>
		<pubDate>Thu, 29 Nov 2007 19:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-105798</guid>
		<description>It is too early to give you a solid answer to your question, but let me point out that for a vendor like CA, working on a standard is an investment and we will do what we can to get a return on that investment. If we don&#039;t adopt it ourselves, our ROI is gone. If the CMDBf specification is not widely adopted, our ROI is gone. 

Would an open source reference implementation help? Thinking back on my own experience as a developer, without the open source reference implementation of the SNMP trap code, (was it someone from Stanford who wrote that?) I am sure I would not have been nearly as eager to put automatically generated incidents into the service desk product I was working on at the time, and I don&#039;t think SNMP would have become the ubiquitous standard it is today. 

So, would I like to see an open source reference implementation of the CMDBf spec? You are darn tootin&#039; I would. I can&#039;t go beyond my own opinion, but you know for yourself that no one likes to lose ROI... 

Along those lines, tell us more about what you would like to see in a reference implementation. What form would you like it to take? How would you like to see it published? Never can tell who might pay attention.
Marv 
http://community.ca.com/blogs/itservice</description>
		<content:encoded><![CDATA[<p>It is too early to give you a solid answer to your question, but let me point out that for a vendor like CA, working on a standard is an investment and we will do what we can to get a return on that investment. If we don&#8217;t adopt it ourselves, our ROI is gone. If the CMDBf specification is not widely adopted, our ROI is gone. </p>
<p>Would an open source reference implementation help? Thinking back on my own experience as a developer, without the open source reference implementation of the SNMP trap code, (was it someone from Stanford who wrote that?) I am sure I would not have been nearly as eager to put automatically generated incidents into the service desk product I was working on at the time, and I don&#8217;t think SNMP would have become the ubiquitous standard it is today. </p>
<p>So, would I like to see an open source reference implementation of the CMDBf spec? You are darn tootin&#8217; I would. I can&#8217;t go beyond my own opinion, but you know for yourself that no one likes to lose ROI&#8230; </p>
<p>Along those lines, tell us more about what you would like to see in a reference implementation. What form would you like it to take? How would you like to see it published? Never can tell who might pay attention.<br />
Marv<br />
<a href="http://community.ca.com/blogs/itservice" rel="nofollow">http://community.ca.com/blogs/itservice</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cote'</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-105190</link>
		<dc:creator>Cote'</dc:creator>
		<pubDate>Thu, 29 Nov 2007 00:24:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-105190</guid>
		<description>Thanks for the comment and link (you can bet I&#039;ll subscribe), Marv. I agree with you: the standards are the key. My thinking is that having shipping code with the standard - rather than just having the standard itself - is vital for adoption, esp. in the IT management area. That said, I don&#039;t know what the CMDBf&#039;s plans for the reference implementations or other &quot;running code&quot; along those lines. Out of curiosity: are there some?</description>
		<content:encoded><![CDATA[<p>Thanks for the comment and link (you can bet I&#8217;ll subscribe), Marv. I agree with you: the standards are the key. My thinking is that having shipping code with the standard &#8211; rather than just having the standard itself &#8211; is vital for adoption, esp. in the IT management area. That said, I don&#8217;t know what the CMDBf&#8217;s plans for the reference implementations or other &#8220;running code&#8221; along those lines. Out of curiosity: are there some?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marv Waschke</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-104990</link>
		<dc:creator>Marv Waschke</dc:creator>
		<pubDate>Wed, 28 Nov 2007 11:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-104990</guid>
		<description>I am a partisan in this discussion, being from CA and a member of the CMDB Federation Working Group technical committee (we do have a name!), but I want to point out that the CMDBf spec and work on language standards like SML pave the way toward a level of standardization that will make an open source CMDB make sense. Believe it or not, I think an open source CMDB is a great idea, but you point out many problems that hold back an open source source implementation as much as closed source. Without widely accepted models of interfaces, CIs, and transactions, an open source CMDB is no easier to integrate or federate than any proprietary product. So right now, those of us from the vendors who are slogging it out in the trenches, building the standards that will make CMDBs easier to implement are doing a service to open source as well as proprietary products. You can see some of my perspective on this in my blog, &lt;a href=&quot;http://community.ca.com/blogs/itservice&quot; rel=&quot;nofollow&quot;&gt;http://community.ca.com/blogs/itservice&lt;/a&gt;. Marv Waschke </description>
		<content:encoded><![CDATA[<p>I am a partisan in this discussion, being from CA and a member of the CMDB Federation Working Group technical committee (we do have a name!), but I want to point out that the CMDBf spec and work on language standards like SML pave the way toward a level of standardization that will make an open source CMDB make sense. Believe it or not, I think an open source CMDB is a great idea, but you point out many problems that hold back an open source source implementation as much as closed source. Without widely accepted models of interfaces, CIs, and transactions, an open source CMDB is no easier to integrate or federate than any proprietary product. So right now, those of us from the vendors who are slogging it out in the trenches, building the standards that will make CMDBs easier to implement are doing a service to open source as well as proprietary products. You can see some of my perspective on this in my blog, <a href="http://community.ca.com/blogs/itservice" rel="nofollow">http://community.ca.com/blogs/itservice</a>. Marv Waschke </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An Open Source CMDB at John M Willis</title>
		<link>http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/comment-page-1/#comment-104188</link>
		<dc:creator>An Open Source CMDB at John M Willis</dc:creator>
		<pubDate>Tue, 27 Nov 2007 21:49:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/11/26/an-open-source-cmdb/#comment-104188</guid>
		<description>[...] An Open Source CMDB [...]</description>
		<content:encoded><![CDATA[<p>[...] An Open Source CMDB [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

