<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Clearspace Server Syndication Feed</title>
    <link>http://communities.vmware.com/blogs</link>
    <description>A syndication feed of all the blogs on this system</description>
    <pubDate>Wed, 25 Nov 2009 18:51:35 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-25T18:51:35Z</dc:date>
    <item>
      <title>How to Determine Bandwidth Usage</title>
      <link>http://communities.vmware.com/blogs/ManualAutomation/2009/11/25/how-to-determine-bandwidth-usage</link>
      <description>I gave a presentation at VMworld 2009 on my SRM implementation. Part of this presentation included a discussion on WAN requirements and, more specifically, how to determine the amount of bandwidth you're going to need to replicate virtual machines between sites.&lt;br /&gt;
&lt;br /&gt;
I have decided to wrap-up the main points of this discussion in this article for those that missed the session and for future reference in general.&lt;br /&gt;
&lt;br /&gt;
I've summarized the process in three steps:&lt;br /&gt;
Step 1: Determine the size of data that needs to be replicated&lt;br /&gt;
Step 2: Determine the change rate&lt;br /&gt;
Step 3: Crunch the numbers &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Determine the Size of Data that Needs to be Replicated&lt;/b&gt;&lt;br /&gt;
For SRM, you're going to group protected VMs on the same LUN or LUNs. View your datastores and add up all of the disk in use (i.e. utilized by VMDKs, VMXs, logs, etc). This will be the total size of data that needs to be replicated &lt;br /&gt;
&lt;br /&gt;
Note that the first replication is what I call the "seed" copy as it will replicate all of the data. Most modern replication technologies will replicate only the changes or deltas from that point forward. Because this can be quite a sizable amount of data sometimes adding up to a terabyte or more, I highly recommend replicating over a LAN connection first. I had the good fortune of having both of my SAN nodes in the same location for several weeks. This allowed me to setup replication between the two and perform that first seed copy while connected via high-speed LAN links. If you don't have this luxury, some SAN vendors provide a facility where by you can use alternate media such as tape to perform the first copy. Either way, please keep this in mind as it could dramatically impact the success of your efforts (i.e. replication could consume large amounts of bandwidth causing production applications to fail, it could run for a long time causing doubt that it will ever finish successfully, etc, etc). &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Determine the Change Rate&lt;/b&gt;&lt;br /&gt;
This will be the hardest part for some storage administrators. You'll typically want to determine both daily and peak change rates. There are several different ways of determining your change rate. Here are a few examples:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Obtain from incremental backups&lt;/li&gt;
&lt;li&gt;Utilize tools provided by your SAN vendor
&lt;ul&gt;
&lt;li&gt;If you haven't purchased your SAN yet, ask SAN vendors if they have tools that will help you manage and monitor bandwidth utilization&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Utilize third-party WAN (or LAN) bandwidth monitoring tools&lt;/li&gt;
&lt;li&gt;Perform several replications overs at least a full weeks time and measure the results&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
I used the last two methods to determine our daily and peak change rate. And after moving the second SAN unit to the remote site, we continued measuring the WAN bandwidth utilization over two weeks time.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Crunch the Numbers&lt;/b&gt;&lt;br /&gt;
Now that you're armed with some raw data, it's time to try to make sense of it all. The general formula we'll use to calculate the change rate is:&lt;br /&gt;
(GB change/day)/(GB total size) = % change rate&lt;br /&gt;
&lt;br /&gt;
So, for example, if we had 56GB of data change in one day out of 617GB total, the change rate would be 56/617 = 9% per day. You'll find that a 9% change rate is not that bad. From this you could surmise that you'll need a fractional DS3 (about 6 DS1s). &lt;br /&gt;
&lt;br /&gt;
Alternatively, you could use an "industry average" change rate of 20% and apply that to the total size of data you discovered in the first step. I have seen this figure used as a general guideline in documents from multiple SAN vendors over the years. Hopefully it's overkill for your needs but it's better than nothing. Using this rate on same same example:&lt;br /&gt;
20% * 617GB = 124GB/24hrs = 5.2GB/hr = about 12 DS1s &lt;br /&gt;
&lt;br /&gt;
As you can see, this will cause you to provision roughly double the amount bandwidth that you really need.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;Caveat Emptor&lt;/b&gt;&lt;br /&gt;
Please note that every environment is different. Consider these calculations to be estimates! These rates are never linear. For example, after all is said and done you may add several VMs to your replicated datastores dramatically increasing the total size. Consequently, I recommend revisiting your calculations on a regular basis and adjusting accordingly. Use a good network monitoring tool such as NetFlow Analyzer to help keep you on top of bandwidth utilization. &lt;br /&gt;
&lt;br /&gt;
One final note, my WAN utilization is made up of several consumers - SAN replication, Active Directory replication, corporate applications such as warehouse inventory tracking, etc. Make sure you account for these other bandwidth needs and provision WAN links that meet your total requirements. We also added 30% to our total bandwidth requirements to allow for growth and room for some additional utilization that we knew we would need within the next year. &lt;br /&gt;
&lt;br /&gt;
This certainly isn't the final word on the matter so please feel free to post your experiences on determining WAN bandwidth requirements.</description>
      <category domain="http://communities.vmware.com/blogs/tags">srm</category>
      <category domain="http://communities.vmware.com/blogs/tags">storage</category>
      <category domain="http://communities.vmware.com/blogs/tags">wan</category>
      <category domain="http://communities.vmware.com/blogs/tags">bandwidth</category>
      <pubDate>Wed, 25 Nov 2009 18:51:35 GMT</pubDate>
      <author>Virtual_JTW</author>
      <guid>http://communities.vmware.com/blogs/ManualAutomation/2009/11/25/how-to-determine-bandwidth-usage</guid>
      <dc:date>2009-11-25T18:51:35Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/ManualAutomation/comment/how-to-determine-bandwidth-usage</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ManualAutomation/feeds/comments?blogPostID=5252</wfw:commentRss>
    </item>
    <item>
      <title>Tip: EMC Celerra NS350 iSCSI and vSphere 4 SAN HCL</title>
      <link>http://communities.vmware.com/blogs/ManualAutomation/2009/11/23/tip-emc-celerra-ns350-iscsi-and-vsphere-4-san-hcl</link>
      <description>&lt;br /&gt;
As part of my vSphere 4.0 upgrade planning, I checked VMware's HCL for all of my hardware. I noticed that VMware's SAN HCL for vSphere 4 includes the Celerra NS350 for NAS but there's no listing for iSCSI unlike many other Celerra models that explicitly state "iSCSI" and "NAS". &lt;br /&gt;
&lt;br /&gt;
Good News: I opened and SR with EMC support who verified that the Celerra NS350 is indeed supported as an iSCSI target for vSphere 4 just as it is for VI 3.5. &lt;br /&gt;
&lt;p /&gt;
For future reference, one can verify this by using the e-Lab Navigator tool found on EMC PowerLink. &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">vmware</category>
      <category domain="http://communities.vmware.com/blogs/tags">support</category>
      <category domain="http://communities.vmware.com/blogs/tags">vsphere</category>
      <category domain="http://communities.vmware.com/blogs/tags">storage</category>
      <category domain="http://communities.vmware.com/blogs/tags">hcl</category>
      <pubDate>Mon, 23 Nov 2009 21:50:18 GMT</pubDate>
      <author>Virtual_JTW</author>
      <guid>http://communities.vmware.com/blogs/ManualAutomation/2009/11/23/tip-emc-celerra-ns350-iscsi-and-vsphere-4-san-hcl</guid>
      <dc:date>2009-11-23T21:50:18Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/ManualAutomation/comment/tip-emc-celerra-ns350-iscsi-and-vsphere-4-san-hcl</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/ManualAutomation/feeds/comments?blogPostID=5250</wfw:commentRss>
    </item>
    <item>
      <title>VMware TAM Weekly Newsletter Edition 1.13 - vSphere 4 Update 1.0, View 4.0 Available for download and loads more</title>
      <link>http://communities.vmware.com/blogs/vmwaretam/2009/11/23/vmware-tam-weekly-newsletter-edition-113-vsphere-4-update-10-view-40-available-for-download-and-loads-more</link>
      <description>Lots of news, reviews and more in this weeks newsletter, please enjoy.&lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;

&lt;ul class="jive-dash"&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
Kind Regards&lt;br /&gt;
&lt;br /&gt;
Neil Isserow | VCP3 | Technical Account Manager - Queensland | &lt;br /&gt;
VMware Australia |</description>
      <category domain="http://communities.vmware.com/blogs/tags">4.0</category>
      <category domain="http://communities.vmware.com/blogs/tags">anz</category>
      <category domain="http://communities.vmware.com/blogs/tags">archive</category>
      <category domain="http://communities.vmware.com/blogs/tags">brisbane</category>
      <category domain="http://communities.vmware.com/blogs/tags">certification</category>
      <category domain="http://communities.vmware.com/blogs/tags">course</category>
      <category domain="http://communities.vmware.com/blogs/tags">discount</category>
      <category domain="http://communities.vmware.com/blogs/tags">esx</category>
      <category domain="http://communities.vmware.com/blogs/tags">esxi</category>
      <category domain="http://communities.vmware.com/blogs/tags">neil</category>
      <category domain="http://communities.vmware.com/blogs/tags">news</category>
      <category domain="http://communities.vmware.com/blogs/tags">newsletter</category>
      <category domain="http://communities.vmware.com/blogs/tags">region</category>
      <category domain="http://communities.vmware.com/blogs/tags">tam</category>
      <category domain="http://communities.vmware.com/blogs/tags">technical</category>
      <category domain="http://communities.vmware.com/blogs/tags">technical_account_manager</category>
      <category domain="http://communities.vmware.com/blogs/tags">twitter</category>
      <category domain="http://communities.vmware.com/blogs/tags">vforum</category>
      <category domain="http://communities.vmware.com/blogs/tags">vi4</category>
      <category domain="http://communities.vmware.com/blogs/tags">virtualization</category>
      <category domain="http://communities.vmware.com/blogs/tags">vmworld</category>
      <category domain="http://communities.vmware.com/blogs/tags">vsphere</category>
      <category domain="http://communities.vmware.com/blogs/tags">vss</category>
      <category domain="http://communities.vmware.com/blogs/tags">weekly</category>
      <category domain="http://communities.vmware.com/blogs/tags">view_4.0</category>
      <category domain="http://communities.vmware.com/blogs/tags">update_1</category>
      <pubDate>Mon, 23 Nov 2009 08:47:40 GMT</pubDate>
      <author>nisserow</author>
      <guid>http://communities.vmware.com/blogs/vmwaretam/2009/11/23/vmware-tam-weekly-newsletter-edition-113-vsphere-4-update-10-view-40-available-for-download-and-loads-more</guid>
      <dc:date>2009-11-23T08:47:40Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/vmwaretam/comment/vmware-tam-weekly-newsletter-edition-113-vsphere-4-update-10-view-40-available-for-download-and-loads-more</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/vmwaretam/feeds/comments?blogPostID=5247</wfw:commentRss>
    </item>
    <item>
      <title>vSphere PowerCLI 4.0 Update1 リリース</title>
      <link>http://communities.vmware.com/blogs/kkomatsu/2009/11/22/vsphere-powercli-40-update1-</link>
      <description>vSphere 4.0 Update1 にあわせて、vSphere PowerCLI 4.0 Update1 もリリースされた。大幅な機能拡張がなされている。&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/windowstoolkit/"&gt;http://www.vmware.com/support/developer/windowstoolkit/&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
新しく提供されたコマンドレットによって例えば下記のようなことが自動化できる&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;ESX自体のパワーオン・オフ、パッチの適用が可能に&lt;/li&gt;
&lt;li&gt;仮想マシンクローン時等のカスタマイゼーションでIPアドレス等の指定が可能に&lt;/li&gt;
&lt;li&gt;ゲストOSのネットワーク設定の制御可能に&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
また、既存のコマンドレットの拡張によって、下記のようなことにも対応できる&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;仮想マシンをThinディスクで作成可能に&lt;/li&gt;
&lt;li&gt;仮想マシンのライブクローン(パワーオン状態の仮想マシンのクローン)が可能に&lt;/li&gt;
&lt;li&gt;仮想ディスクのオンライン拡張が可能に&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
一方、vNetwork Distributed Switch の構成・管理への対応は見送られているようだ。VMworld の Break out セッションでは、VMotion や FT、NFC トラフィック を Parse する Wireshark プラグインと並んでデモもされていただけに残念。これら、PowerCLI で対応していない機能については、先日も紹介した Get-View を使って、vSphere SDK for .Net のレベルで記述することになる。&lt;br /&gt;
&lt;br /&gt;
なお、同じタイミングでPowerCLI コマンドレットのオンラインリファレンスがついに提供された&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/windowstoolkit/wintk40u1/html/index.html"&gt;http://www.vmware.com/support/developer/windowstoolkit/wintk40u1/html/index.html&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">api</category>
      <category domain="http://communities.vmware.com/blogs/tags">automation</category>
      <category domain="http://communities.vmware.com/blogs/tags">powershell</category>
      <category domain="http://communities.vmware.com/blogs/tags">sdk</category>
      <pubDate>Sun, 22 Nov 2009 23:27:55 GMT</pubDate>
      <author>kkomatsu</author>
      <guid>http://communities.vmware.com/blogs/kkomatsu/2009/11/22/vsphere-powercli-40-update1-</guid>
      <dc:date>2009-11-22T23:27:55Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/kkomatsu/comment/vsphere-powercli-40-update1-</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/kkomatsu/feeds/comments?blogPostID=5245</wfw:commentRss>
    </item>
    <item>
      <title>MAP-1.1 Mathematica Platform</title>
      <link>http://communities.vmware.com/blogs/3bx/2009/11/21/map11-mathematica-platform</link>
      <description>Notations: A-Action, R-Result, Q-Question, C-Cognition/Commentary, X-Exploration research&lt;br /&gt;
&lt;br /&gt;
A MAP-1.1.1 Completed the Mathematica installation.&lt;br /&gt;
&lt;br /&gt;
R MAP-1.1.2 Mathematica installation completed successfully.  As far as I can tell at this point Mathematica 7 for Students runs well on an Ubuntu Server 9.10 virtual machine in the ESX Server 3i 3.5 Build 153875 environment.&lt;br /&gt;
&lt;p /&gt;
 &lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/38-5244-7729/Mathematica+on+MAP1.jpg" alt="Mathematica on MAP1.jpg" width="620" class="jive-image-thumbnail jive-image" onclick="myJiveImage.start(this, 'http://communities.vmware.com/servlet/JiveServlet/downloadImage/38-5244-7729/Mathematica+on+MAP1.jpg');return false;"/&gt;</description>
      <category domain="http://communities.vmware.com/blogs/tags">mathematica</category>
      <pubDate>Sat, 21 Nov 2009 20:04:29 GMT</pubDate>
      <author>focaccio</author>
      <guid>http://communities.vmware.com/blogs/3bx/2009/11/21/map11-mathematica-platform</guid>
      <dc:date>2009-11-21T20:04:29Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/3bx/comment/map11-mathematica-platform</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/3bx/feeds/comments?blogPostID=5244</wfw:commentRss>
    </item>
    <item>
      <title>virtualization.info Vanguards on LinkedIn</title>
      <link>http://communities.vmware.com/blogs/vmwareconnected/2009/11/19/virtualizationinfo-vanguards-on-linkedin</link>
      <description>We last saw our intrepid Web 2.0 adventurer about to delve back into the depths of &lt;a class="jive-link-external" href="http://www.linkedin.com/"&gt;LinkedIn&lt;/a&gt;. LinkedIn is old school, one of the oldest business social networks, and it's not about virtual martinis or superwalls or how many movies you have in common -- it's all about the networking.&lt;br /&gt;
&lt;br /&gt;
I will admit it's been a while since I've been there -- probably since the last time I was looking for a job, which seems to be one of the major use cases for LinkedIn. The principle activity of LinkedIn, aside from the meta-activity of increasing the size of your personal network, is the Introduction -- asking your network to hand your referral from person to person until you reach the object of your affections -- Bill Clinton, a hiring manager, a prospect. I've never sent or received one of these invitations, but I do know folks that have gotten plenty of job inquiries from the site. My profile on LinkedIn is &lt;a class="jive-link-external" href="http://www.linkedin.com/in/johntroyer"&gt;here&lt;/a&gt;, and no, I'm not looking for a job. &lt;br /&gt;
&lt;br /&gt;
Spurred on by the current social networking frenzy, they are adding features like a Q&amp;#38;A section and beefier profiles.  Here's Bernard Lunn of Read/Write Web on &lt;a class="jive-link-external" href="http://www.readwriteweb.com/archives/linkedin_and_the_future_of_business_social_networks.php"&gt;how he recently used LinkedIn&lt;/a&gt; and his perception of its business value vs Facebook's. &lt;br /&gt;
&lt;br /&gt;
&lt;div style="float: right; margin: 0 0 5px 5px;"&gt;&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/38-1227-1400/Vanguards-761533.png" alt="Vanguards-761533.png" class="jive-image"  /&gt; &lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/38-1227-1401/linkedin-720690.gif" alt="linkedin-720690.gif" class="jive-image"  /&gt;&lt;/div&gt;
After logging in and taking care of some pending connection requests, I joined Alessandro Perilli's &lt;a class="jive-link-external" href="http://www.virtualization.info/community/"&gt;virtualization.info Vanguards Group&lt;/a&gt; (not to be confused with &lt;a class="jive-link-external" href="http://www.vmware.com/customers/vanguard.html"&gt;VMware's Virtual Vanguard Awards&lt;/a&gt;). &lt;br /&gt;
&lt;br /&gt;
After only a month and with a single announcement, Alessandro has assembled 383 virtualization professionals from across the globe. Not bad! So why do you want to be there, even if you're not looking for a job?&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;A wide cross-section of the virtualization industry.&lt;/b&gt; There are vendors (from VMware and Microsoft on out), consultants of all stripes, very experienced sysadmins and IT experts, and quite a few names you may recognize from communities.vmware.com.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;You can see and contact everybody in the Group.&lt;/b&gt; The contact piece is configurable on a per-group and per-person basis, but Vanguards is set up by default so that we can all contact each other. Interested in finding a virtualization consultant in Norway? Looking for a contact at a vendor -- either the executive or the engineering kind? Want to compare notes with someone else in your industry? You can probably make that happen here with a quick search.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;You won't be spammed.&lt;/b&gt; Now, since this is a business network, many people have something to pitch, so LinkedIn groups are not built for spam. In a LinkedIn Group you can contact individuals, but nobody in the Group can globally spam everybody in the group with a pitch for their latest virtualization management appliance.&lt;br /&gt;
&lt;br /&gt;
LinkedIn is still very much a business-to-business network, and so what a Group can do there is still very buttoned-down and oriented at making business contacts -- LinkedIn doesn't actually offer much more to do with Groups yet. I suspect that we'll see other functionality soon: for instance, you can ask a Question to your network and the LinkedIn community at large, but I'd love to see questions just from the virtualization.info Vanguards Group. Although the Groups feature on LinkedIn is at least two years old, they've only recently &lt;a class="jive-link-external" href="http://blog.linkedin.com/blog/2007/09/linkedin-groups.html"&gt;opened up and become easier to create&lt;/a&gt;.   &lt;br /&gt;
&lt;br /&gt;
So you can't go wrong adding the &lt;a class="jive-link-external" href="http://www.virtualization.info/community/"&gt;virtualization.info Vanguards Group&lt;/a&gt; on LinkedIn to your professional online presence. I think since we have such a vibrant community here, I'm not going to start up a LinkedIn group specifically for VMware, but let me know if you have other good ideas.</description>
      <category domain="http://communities.vmware.com/blogs/tags">linkedin</category>
      <pubDate>Fri, 16 Nov 2007 03:17:38 GMT</pubDate>
      <author>JohnTroyer</author>
      <guid>http://communities.vmware.com/blogs/vmwareconnected/2009/11/19/virtualizationinfo-vanguards-on-linkedin</guid>
      <dc:date>2007-11-16T03:17:38Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/vmwareconnected/comment/virtualizationinfo-vanguards-on-linkedin</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/vmwareconnected/feeds/comments?blogPostID=1227</wfw:commentRss>
    </item>
    <item>
      <title>Virtualization reddit: come on in!</title>
      <link>http://communities.vmware.com/blogs/vmwareconnected/2009/11/19/virtualization-reddit-come-on-in</link>
      <description>There are many social media sites out there. Most of them can be interesting if you have something in common with the crowd that hangs out there. &lt;a class="jive-link-external" href="http://digg.com"&gt;Digg&lt;/a&gt; often gets most of the press, but I've always been more partial to &lt;a class="jive-link-external" href="http://reddit.com"&gt;reddit&lt;/a&gt;. &lt;br /&gt;
&lt;br /&gt;
Reddit works in a similar way to Digg -- people submit items, and everybody votes them up or down. In theory, the most interesting items bubble to the top. Also in theory, as you rate items up or down, the system learns about your interest and starts to show you recommended items. &lt;br /&gt;
&lt;br /&gt;
The reddit crowd has always been a little geekier and a little more interesting -- a bit of lisp, a bit of web culture, and sometimes a funny picture. A quick dip into the &lt;a class="jive-link-external" href="http://reddit.com/r/programming"&gt;programming reddit&lt;/a&gt; now and then will help you carry on the conversation at your next party when Erlang or closures come up. (Hmm, I may be going to the wrong parties.)&lt;br /&gt;
&lt;br /&gt;
Reddit just opened up a beta feature to create new topic-specific reddits and I'm very pleased to announce:&lt;br /&gt;
&lt;h2&gt;&lt;a class="jive-link-external" href="http://reddit.com/r/virtualization/"&gt;virtualization reddit&lt;/a&gt;&lt;/h2&gt;
&lt;a class="jive-link-external" href="http://reddit.com/r/virtualization/"&gt;&lt;img src="http://communities.vmware.com/servlet/JiveServlet/downloadImage/38-1431-1757/reddit.PNG" alt="reddit.PNG" class="jive-image"  /&gt;&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Virtualization reddit is the place to read news and commentary about virtualization, all chosen by the virtualization community. VMware, Microsoft, Virtuozzo, Xen, whatever. Go ahead, create an account, submit your favorite news article or blog post on virtualization, and rate the others.&lt;br /&gt;
&lt;br /&gt;
I've submitted a few articles, but one man does not a social media site make. Come on in, add your two cents, vote up the most interesting articles, and have fun. Then check back every day to discover today's must-read articles about virtualization technology and the virtualization industry.</description>
      <category domain="http://communities.vmware.com/blogs/tags">reddit</category>
      <category domain="http://communities.vmware.com/blogs/tags">social_media</category>
      <pubDate>Fri, 25 Jan 2008 05:50:34 GMT</pubDate>
      <author>JohnTroyer</author>
      <guid>http://communities.vmware.com/blogs/vmwareconnected/2009/11/19/virtualization-reddit-come-on-in</guid>
      <dc:date>2008-01-25T05:50:34Z</dc:date>
      <wfw:comment>http://communities.vmware.com/blogs/vmwareconnected/comment/virtualization-reddit-come-on-in</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/vmwareconnected/feeds/comments?blogPostID=1431</wfw:commentRss>
    </item>
  </channel>
</rss>

