<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://omarsultan.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Omar Sultan</title>
 <link>http://omarsultan.sys-con.com/</link>
 <description>Latest News from Omar Sultan</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 08:51:29 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Services in a Cloud Computing Environment</title>
 <link>http://omarsultan.sys-con.com/node/770228</link>
 <description>Once we cut through the cloud-hype and start looking at the practicalities of implementing things like workload portability, I think the lessons of the past will re-assert themselves, this time with things like security and L4-7 services.&lt;p&gt;&lt;a href=&quot;http://omarsultan.sys-con.com/node/770228&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 07 Dec 2008 15:50:00 EST</pubDate>
 <guid isPermaLink="true">http://omarsultan.sys-con.com/node/770228</guid>
 <comments>http://omarsultan.sys-con.com/node/770228#feedback</comments>
</item>
<item>
 <title>Cloud Computing and the &quot;Cloud Dining&quot; Analogy</title>
 <link>http://omarsultan.sys-con.com/node/592855</link>
 <description>I was chatting with a customer the other day who was struggling with some of the implications of cloud computing. The analogy that finally made sense to them is what I will call &#039;cloud dining.&#039; I am the cook in the house and I am tasked with feeding the family. If my 10-year old is lobbying for Italian, I can cook at home or order out. The decision may also vary from day to day. For instance, I might not have all the ingredients and have to order out, or, like this weekend, it may be 103 outside and cooking at home is not all that appealing. Now, the same can be said for supporting a given application in a cloud computing environment.&lt;p&gt;&lt;a href=&quot;http://omarsultan.sys-con.com/node/592855&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 03 Nov 2008 22:00:00 EST</pubDate>
 <guid isPermaLink="true">http://omarsultan.sys-con.com/node/592855</guid>
 <comments>http://omarsultan.sys-con.com/node/592855#feedback</comments>
</item>
<item>
 <title>Deconstructing Data Center 3.0 </title>
 <link>http://omarsultan.sys-con.com/node/668562</link>
 <description>You may be wondering if there is anything to this “Data Center 3.0” thing beyond some clever marketing folks earning their paychecks. Well, clever marketing folks aside, the name was very explicitly chosen, so lets deconstruct it a bit. First of all, this is not LAN 3.0 or SAN 3.0, but &lt;em&gt;Data Center&lt;/em&gt; 3.0.&lt;p&gt;&lt;a href=&quot;http://omarsultan.sys-con.com/node/668562&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 09 Sep 2008 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://omarsultan.sys-con.com/node/668562</guid>
 <comments>http://omarsultan.sys-con.com/node/668562#feedback</comments>
</item>
<item>
 <title>Virtualization: Data Centers &amp; The Joy of Lego</title>
 <link>http://omarsultan.sys-con.com/node/534132</link>
 <description>During customer briefings, I&#039;ll often use the concept of the Lego data center when talking about the vision behind Data Center 3.0. The joy of Lego (for me at least) is the ability to build something then, (sometimes violently) break it apart and build something else. This is the operational model we look to bring to the data center - sans most of the violence - with Data Center 3.0.&lt;p&gt;&lt;a href=&quot;http://omarsultan.sys-con.com/node/534132&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 27 Apr 2008 09:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://omarsultan.sys-con.com/node/534132</guid>
 <comments>http://omarsultan.sys-con.com/node/534132#feedback</comments>
</item>
</channel>
</rss>
