<?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"
	>
<channel>
	<title>Comments on: Getting Giddy with the CMDB: REST, Cheap Spread, and Wet CIs</title>
	<atom:link href="http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/</link>
	<description>One foot in the muck, the other in utopia</description>
	<pubDate>Wed, 03 Dec 2008 21:11:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: People Over Process &#187; An Open Source CMDB</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-103154</link>
		<dc:creator>People Over Process &#187; An Open Source CMDB</dc:creator>
		<pubDate>Mon, 26 Nov 2007 23:38:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-103154</guid>
		<description>[...] (Related, see my short note and the resulting reader comments on the CMDB Federation standard effort.) [...]</description>
		<content:encoded><![CDATA[<p>[...] (Related, see my short note and the resulting reader comments on the CMDB Federation standard effort.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; BMC&#8217;s Developer Network and Open Source Announcement</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-50424</link>
		<dc:creator>People Over Process &#187; BMC&#8217;s Developer Network and Open Source Announcement</dc:creator>
		<pubDate>Wed, 25 Jul 2007 20:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-50424</guid>
		<description>[...] And I&#8217;ll throw a crazy one out there (crazy based on it&#8217;s revenue as I understand it): how about the CMDB? Could one come up with a plan where-in open sourcing it would actually be more profitable than keeping it closed source? It&#8217;d certainly be mud in the eye of the rest of the Big 4 and CMDB vendors. In BMC&#8217;s case, there&#8217;s the AR system, the runtime framework underpinning many of BMC&#8217;s highly successful products like Remedy and the CMDB. Less dramatic, I suspect the CMDB Federaton would benefit from an open source project or two. Here&#8217;s one idea. [...]</description>
		<content:encoded><![CDATA[<p>[...] And I&#8217;ll throw a crazy one out there (crazy based on it&#8217;s revenue as I understand it): how about the CMDB? Could one come up with a plan where-in open sourcing it would actually be more profitable than keeping it closed source? It&#8217;d certainly be mud in the eye of the rest of the Big 4 and CMDB vendors. In BMC&#8217;s case, there&#8217;s the AR system, the runtime framework underpinning many of BMC&#8217;s highly successful products like Remedy and the CMDB. Less dramatic, I suspect the CMDB Federaton would benefit from an open source project or two. Here&#8217;s one idea. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cote</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-10621</link>
		<dc:creator>cote</dc:creator>
		<pubDate>Fri, 02 Mar 2007 00:27:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-10621</guid>
		<description>Brendan: thanks for the commentary and pointers. I've been keen to see the open source CMDB(s?) pan out.

Mr. Twiggs: indeed. Too bad there isn't more slack time to try out new things ;)</description>
		<content:encoded><![CDATA[<p>Brendan: thanks for the commentary and pointers. I&#8217;ve been keen to see the open source CMDB(s?) pan out.</p>
<p>Mr. Twiggs: indeed. Too bad there isn&#8217;t more slack time to try out new things ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Glenn (aka Mr Twiggs)</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-10154</link>
		<dc:creator>Glenn (aka Mr Twiggs)</dc:creator>
		<pubDate>Tue, 27 Feb 2007 22:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-10154</guid>
		<description>Yes, I'm giddy!

If my upper management were as giddy as me, then shit would start happening. Alas, I don't think it will, but I'll continue to talk it up.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;m giddy!</p>
<p>If my upper management were as giddy as me, then shit would start happening. Alas, I don&#8217;t think it will, but I&#8217;ll continue to talk it up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Martin</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-10007</link>
		<dc:creator>Brendan Martin</dc:creator>
		<pubDate>Tue, 27 Feb 2007 03:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-10007</guid>
		<description>Cote, what do I say, its hard to mount an arguement to the contrary, but the vendor community will continue to build the hype and their proprietory interfaces just as long as the debate continues about standards and the maturity of ITIL. Its the utopian view of the world. Having an operations management background the information I require is a little different from the guys at the Ops Centre Flightdeck, and different again from the Change Managers. I need to know costs per device and service levels, etc. Take a quick look at &lt;a href="http://www.cmdb.info" rel="nofollow"&gt;CMDB.info&lt;/a&gt; for the details of an Open Source Framework for a CMDB. There are lots of functional tools in there, such as Nagios, Nmap, OCS Inventory, Oreon, etc. The only way there will be a set of standards emerge is to take the development of an industry standard within the Open Source Community. The REST and ATOM standards are an interesting debate, but under current capabilities I use Nmap, if something is on my network and its running an IP Stack, it can be found and further interogated in all sorts of ways. To progress on working towards standards, one requires a functional framework. Check out what is included in the stable build specs. BTY Great Blog. Cheers</description>
		<content:encoded><![CDATA[<p>Cote, what do I say, its hard to mount an arguement to the contrary, but the vendor community will continue to build the hype and their proprietory interfaces just as long as the debate continues about standards and the maturity of ITIL. Its the utopian view of the world. Having an operations management background the information I require is a little different from the guys at the Ops Centre Flightdeck, and different again from the Change Managers. I need to know costs per device and service levels, etc. Take a quick look at <a href="http://www.cmdb.info" rel="nofollow">CMDB.info</a> for the details of an Open Source Framework for a CMDB. There are lots of functional tools in there, such as Nagios, Nmap, OCS Inventory, Oreon, etc. The only way there will be a set of standards emerge is to take the development of an industry standard within the Open Source Community. The REST and ATOM standards are an interesting debate, but under current capabilities I use Nmap, if something is on my network and its running an IP Stack, it can be found and further interogated in all sorts of ways. To progress on working towards standards, one requires a functional framework. Check out what is included in the stable build specs. BTY Great Blog. Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cote</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9408</link>
		<dc:creator>cote</dc:creator>
		<pubDate>Fri, 23 Feb 2007 15:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9408</guid>
		<description>Dunno off the top of my head, Mark. But, obviously, it's something to start to paying attention to. Any findings yourself? I'm glad you've taken such interest in the topic here ;)</description>
		<content:encoded><![CDATA[<p>Dunno off the top of my head, Mark. But, obviously, it&#8217;s something to start to paying attention to. Any findings yourself? I&#8217;m glad you&#8217;ve taken such interest in the topic here ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Wahl</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9084</link>
		<dc:creator>Mark Wahl</dc:creator>
		<pubDate>Fri, 23 Feb 2007 00:18:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9084</guid>
		<description>Do you know if any of the open source CIMOM projects, e.g.
http://www.openpegasus.org/manual/CIMOperationsoverHTTP.html
http://wbemservices.sourceforge.net/
http://openwbem.sourceforge.net/
or SNIA, have or are adding a REST alternative to their WBEM?  There's a recent spec for assigning a URI to each element in the CIM repository, 
http://www.dmtf.org/standards/published_documents/DSP0207.pdf
If this were occuring, would be a possible starting point.</description>
		<content:encoded><![CDATA[<p>Do you know if any of the open source CIMOM projects, e.g.<br />
<a href="http://www.openpegasus.org/manual/CIMOperationsoverHTTP.html" rel="nofollow">http://www.openpegasus.org/manual/CIMOperationsoverHTTP.html</a><br />
<a href="http://wbemservices.sourceforge.net/" rel="nofollow">http://wbemservices.sourceforge.net/</a><br />
<a href="http://openwbem.sourceforge.net/" rel="nofollow">http://openwbem.sourceforge.net/</a><br />
or SNIA, have or are adding a REST alternative to their WBEM?  There&#8217;s a recent spec for assigning a URI to each element in the CIM repository,<br />
<a href="http://www.dmtf.org/standards/published_documents/DSP0207.pdf" rel="nofollow">http://www.dmtf.org/standards/published_documents/DSP0207.pdf</a><br />
If this were occuring, would be a possible starting point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cote</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9064</link>
		<dc:creator>cote</dc:creator>
		<pubDate>Thu, 22 Feb 2007 21:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9064</guid>
		<description>Those are all excellent points, as usual, Mark. There'd definitly be some transactional considerations. And, as you anticipated, the REST camp reply would be the re-orient the requirements to remove two phase commit. 

Also -- and to be fair to the Federation folks -- as I got to one of the other points, the major interest I have is in creating an open interface for CMDBs that (hopefully) could be used for federation as well. But, if the implementation of federation doesn't work with the less than transactionally perfect nature of REST (at the moment, hopefully), then other stuff would be needed. 

In that case, I'd hope the idea of having a REST interface on CMDB's could be moved to a more appropriate forum, or just CMDB's in general.

I don't know if anyone has looked to map WS-Man and WSDM to REST. I'm guess not. It'd certainly be a fun exercise and, speaking personally, a good excuse to read those specs ;)</description>
		<content:encoded><![CDATA[<p>Those are all excellent points, as usual, Mark. There&#8217;d definitly be some transactional considerations. And, as you anticipated, the REST camp reply would be the re-orient the requirements to remove two phase commit. </p>
<p>Also &#8212; and to be fair to the Federation folks &#8212; as I got to one of the other points, the major interest I have is in creating an open interface for CMDBs that (hopefully) could be used for federation as well. But, if the implementation of federation doesn&#8217;t work with the less than transactionally perfect nature of REST (at the moment, hopefully), then other stuff would be needed. </p>
<p>In that case, I&#8217;d hope the idea of having a REST interface on CMDB&#8217;s could be moved to a more appropriate forum, or just CMDB&#8217;s in general.</p>
<p>I don&#8217;t know if anyone has looked to map WS-Man and WSDM to REST. I&#8217;m guess not. It&#8217;d certainly be a fun exercise and, speaking personally, a good excuse to read those specs ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Wahl</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9052</link>
		<dc:creator>Mark Wahl</dc:creator>
		<pubDate>Thu, 22 Feb 2007 18:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9052</guid>
		<description>I'm afraid I see a gap - the CMDBF white paper doesn't spell out what kind of operations are going on between these components.  Without this, it's hard for me to evaluate whether a REST/ATOM model would be the best.

E.g., if the operations were limited to 
 get properties of a specified configuration object
 set properties of a specified configuration object
 get notified of a change of properties 

then a REST model seems viable, but then so does SNMP.  
SNMP is widely deployed, easy to implement in everything from a toaster to a data center, etc. 

But what if the operation is a two-phase-commit?  If foo is split across two CMDBs, and an application says "increment foo's counter bar", it might cause causes this federation component to have to negotiate managing separate transactions on the CMDBs.  Distributed Transaction Controller advocates would argue that existing protocols for 2PC should be leveraged for this operation; REST advocates might argue that the operations should be changed to avoid the need for 2PC.

&#62; Why come up with some horky WS-*/SOAP spec when you 
&#62; could just define the URL (ok, ok, “URI”…whatever) 
&#62; addressing of CI’s, how relationships are expressed, 
&#62; and then slap an ATOM interface on top of it?

I would have assumed that a WS-* spec from CMDBF would 
leverage the already-existing WS-Management and/or WSDM 
for some of the heavy lifting of data and protocol 
expression.

Has someone analyzed the abstract operations of 
WS-Management 
http://www.dmtf.org/standards/published_documents/DSP0226.pdf
or WSDM
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm
to look at the efficiency and ease of implementation of
a REST-encoded equivalent protocol for the same operations?</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid I see a gap - the CMDBF white paper doesn&#8217;t spell out what kind of operations are going on between these components.  Without this, it&#8217;s hard for me to evaluate whether a REST/ATOM model would be the best.</p>
<p>E.g., if the operations were limited to<br />
 get properties of a specified configuration object<br />
 set properties of a specified configuration object<br />
 get notified of a change of properties </p>
<p>then a REST model seems viable, but then so does SNMP.<br />
SNMP is widely deployed, easy to implement in everything from a toaster to a data center, etc. </p>
<p>But what if the operation is a two-phase-commit?  If foo is split across two CMDBs, and an application says &#8220;increment foo&#8217;s counter bar&#8221;, it might cause causes this federation component to have to negotiate managing separate transactions on the CMDBs.  Distributed Transaction Controller advocates would argue that existing protocols for 2PC should be leveraged for this operation; REST advocates might argue that the operations should be changed to avoid the need for 2PC.</p>
<p>&gt; Why come up with some horky WS-*/SOAP spec when you<br />
&gt; could just define the URL (ok, ok, “URI”…whatever)<br />
&gt; addressing of CI’s, how relationships are expressed,<br />
&gt; and then slap an ATOM interface on top of it?</p>
<p>I would have assumed that a WS-* spec from CMDBF would<br />
leverage the already-existing WS-Management and/or WSDM<br />
for some of the heavy lifting of data and protocol<br />
expression.</p>
<p>Has someone analyzed the abstract operations of<br />
WS-Management<br />
<a href="http://www.dmtf.org/standards/published_documents/DSP0226.pdf" rel="nofollow">http://www.dmtf.org/standards/published_documents/DSP0226.pdf</a><br />
or WSDM<br />
<a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm" rel="nofollow">http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm</a><br />
to look at the efficiency and ease of implementation of<br />
a REST-encoded equivalent protocol for the same operations?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Tilkov</title>
		<link>http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9051</link>
		<dc:creator>Stefan Tilkov</dc:creator>
		<pubDate>Thu, 22 Feb 2007 17:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2007/02/22/getting-giddy-with-the-cmdb-rest-cheap-spread-and-wet-cis/#comment-9051</guid>
		<description>You are absolutely correct, but I agree with James - fat chance any big vendor is going to jump on this ...

In any case any of them do, count me in as a REST geek available for hire.</description>
		<content:encoded><![CDATA[<p>You are absolutely correct, but I agree with James - fat chance any big vendor is going to jump on this &#8230;</p>
<p>In any case any of them do, count me in as a REST geek available for hire.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
