<?xml version="1.0" encoding="UTF-8"?><rss version="0.92">
<channel>
	<title>BRAD HEDLUND .com</title>
	<link>http://bradhedlund.com</link>
	<description>Studies in Data Center Networking, Virtualization, Computing</description>
	<lastBuildDate>Thu, 26 Jan 2012 01:03:09 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	<!-- generator="WordPress/3.2.1" -->

	<item>
		<title>Construct a Leaf Spine design with 40G or 10G? An observation in scaling the fabric.</title>
		<description><![CDATA[Should you construct a Leaf/Spine fabric with 10G or 40G? In this post I’ll make the simple observation that using 10G interfaces in your leaf/spine fabric scales to more servers than using 40G interfaces, all with the same hardware, bandwidth, and oversubscription. Let’s suppose you’ve decided to build a Leaf/Spine fabric for your data center [...]]]></description>
		<link>http://bradhedlund.com/2012/01/25/construct-a-leaf-spine-design-with-40g-or-10g-an-observation-in-scaling-the-fabric/</link>
			</item>
	<item>
		<title>On optimizing traffic for network virtualization</title>
		<description><![CDATA[The era of network virtualization and software overlays is coming (read: VXLAN, OpenFlow, SDN, etc.) and with it the role of the physical network and what we define as &#8220;the network&#8221;, is all about to change.  How does this change the way application flows map to traffic on the network and servers? How does this change [...]]]></description>
		<link>http://bradhedlund.com/2011/12/22/on-optimizing-traffic-for-network-virtualization/</link>
			</item>
	<item>
		<title>First take on Embrane heleos</title>
		<description><![CDATA[Embrane came out of secrecy today and announced their solution that virtualizes the deployment of network based services.  In the context of how this affects network virtualization, here&#8217;s my initial thoughts on Embrane&#8217;s announcement.. My first take is that Embrane heleos is a positive thing for the network virtualization movement. (Read: good for Nicira, good [...]]]></description>
		<link>http://bradhedlund.com/2011/12/12/first-take-on-embrane-heleos/</link>
			</item>
	<item>
		<title>Hadoop network design challenge</title>
		<description><![CDATA[I had a bit of fun recently working on a hypothetical network design for a large scale Hadoop implementation.  A friend of mine mentioned he was responding to a challenging RFP, and when I asked him more about it out of curiosity he sent me these requirements: (4) Containers In each Container: (25) Racks (64) [...]]]></description>
		<link>http://bradhedlund.com/2011/11/05/hadoop-network-design-challenge/</link>
			</item>
	<item>
		<title>Network Virtualization is like a big virtual chassis</title>
		<description><![CDATA[This is something I&#8217;ve been chewing on for a while now and here&#8217;s my first rough attempt at writing it down: Network Virtualization is the new chassis switch, only much bigger. (and a lot less proprietary) The x86 server is the new Linecard The network switch is the new ASIC VXLAN (or NVGRE) is the new [...]]]></description>
		<link>http://bradhedlund.com/2011/10/12/network-virtualization-is-like-a-big-virtual-chassis/</link>
			</item>
	<item>
		<title>Starting a new journey with Dell Force10</title>
		<description><![CDATA[With mixed emotions, this week I submitted my resignation to Cisco, a fantastic company with great products and great people.  This was the result of an exhausting and drawn out thought process lasting several months.  The data center networking industry is changing fast and this was purely a forward-looking move to best position myself and [...]]]></description>
		<link>http://bradhedlund.com/2011/10/05/starting-a-new-journey-with-dell-force10/</link>
			</item>
	<item>
		<title>Understanding Hadoop Clusters and the Network</title>
		<description><![CDATA[This article is Part 1 in series that will take a closer look at the architecture and methods of a Hadoop cluster, and how it relates to the network and server infrastructure.  The content presented here is largely based on academic work and conversations I&#8217;ve had with customers running real production clusters.  If you run production [...]]]></description>
		<link>http://bradhedlund.com/2011/09/10/understanding-hadoop-clusters-and-the-network/</link>
			</item>
	<item>
		<title>Distributed systems trickle down into Enterprise IT</title>
		<description><![CDATA[In my new role at Cisco I&#8217;ve had the opportunity to observe and study something happening that is (in my opinion) truly significant and mind blowing.  The IT data center landscape as we know it is on the precipice of a major upheaval.  I&#8217;m not talking about virtualization, and cloud, and all that other stuff that&#8217;s been [...]]]></description>
		<link>http://bradhedlund.com/2011/08/19/distributed-systems-trickle-down-into-enterprise-it/</link>
			</item>
	<item>
		<title>On &#8220;Why TRILL wont work for the data center&#8221;</title>
		<description><![CDATA[Today I came across &#8220;Why TRILL won&#8217;t work for data center network architecture&#8221; by Anjan Venkatramani of Juniper. Anjan&#8217;s article makes a few myopic and flawed arguments in slamming TRILL, setting up a sale for QFabric.  The stated problems with TRILL include FCoE, L3 multi-pathing, VLAN scale, and large failure domains. The one and only Ivan Pepelnjak has already tackled the [...]]]></description>
		<link>http://bradhedlund.com/2011/06/15/on-why-trill-wont-work-in-the-data-center/</link>
			</item>
	<item>
		<title>&#8220;Jawbreaker&#8221;, merchant silicon, QFabric, and flat networks</title>
		<description><![CDATA[Brad, can you elaborate on Cisco’s Jawbreaker project? What exactly is it? Is it a response to Juniper’s Q-Fabric? Is it an attempt to rectify the inconsistencies in the differing purpose-built approaches of the N7K and N5K? Why create a new architecture? It seems like Cisco is really in trouble – creating a new architecture, [...]]]></description>
		<link>http://bradhedlund.com/2011/06/10/jawbreaker-merchant-silicon-qfabric-and-flat-networks/</link>
			</item>
</channel>
</rss>
