<?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: Amazon fails to address interoperability concerns; Flexiscale plans cloud platform</title>
	<atom:link href="http://www.itwriting.com/blog/971-amazon-fails-to-address-interoperability-concerns-flexiscale-plans-cloud-platform.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.itwriting.com/blog/971-amazon-fails-to-address-interoperability-concerns-flexiscale-plans-cloud-platform.html</link>
	<description>Tech writing blog</description>
	<lastBuildDate>Tue, 16 Mar 2010 23:26:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tony Lucas</title>
		<link>http://www.itwriting.com/blog/971-amazon-fails-to-address-interoperability-concerns-flexiscale-plans-cloud-platform.html/comment-page-1#comment-109833</link>
		<dc:creator>Tony Lucas</dc:creator>
		<pubDate>Sat, 11 Oct 2008 17:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/971-amazon-fails-to-address-interoperability-concerns-flexiscale-plans-cloud-platform.html#comment-109833</guid>
		<description>Tim,

Sorry we didn&#039;t catch up properly at the event, we were originally meant to be discussing the pro&#039;s and con&#039;s of interoperability, rather than announcing something.  Unfortunately when you only have one side willing to even discuss it, (I&#039;ll let you guess who!), it wasn&#039;t possible.

Happy to give you an update on the work we are doing to make these things easier though.  We are certainly keen to enable the automated transfer of AMI&#039;s to ourselves for starters.

Regards,

Tony.</description>
		<content:encoded><![CDATA[<p>Tim,</p>
<p>Sorry we didn&#8217;t catch up properly at the event, we were originally meant to be discussing the pro&#8217;s and con&#8217;s of interoperability, rather than announcing something.  Unfortunately when you only have one side willing to even discuss it, (I&#8217;ll let you guess who!), it wasn&#8217;t possible.</p>
<p>Happy to give you an update on the work we are doing to make these things easier though.  We are certainly keen to enable the automated transfer of AMI&#8217;s to ourselves for starters.</p>
<p>Regards,</p>
<p>Tony.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bert Armijo</title>
		<link>http://www.itwriting.com/blog/971-amazon-fails-to-address-interoperability-concerns-flexiscale-plans-cloud-platform.html/comment-page-1#comment-109810</link>
		<dc:creator>Bert Armijo</dc:creator>
		<pubDate>Sat, 11 Oct 2008 06:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.itwriting.com/blog/971-amazon-fails-to-address-interoperability-concerns-flexiscale-plans-cloud-platform.html#comment-109810</guid>
		<description>Tim,

Interoperability certainly is a major concern for users of cloud computing. However, it&#039;s important that we get the functionality in place first to provide sufficient value for users.

We looked at OVF when the first draft was released, but came to the conclusion it isn&#039;t well designed for cloud computing. It seemed more of a descriptive wrapper targeted at traditional data center operations.

Bert</description>
		<content:encoded><![CDATA[<p>Tim,</p>
<p>Interoperability certainly is a major concern for users of cloud computing. However, it&#8217;s important that we get the functionality in place first to provide sufficient value for users.</p>
<p>We looked at OVF when the first draft was released, but came to the conclusion it isn&#8217;t well designed for cloud computing. It seemed more of a descriptive wrapper targeted at traditional data center operations.</p>
<p>Bert</p>
]]></content:encoded>
	</item>
</channel>
</rss>
