Comments on: Lippis Report 121: A New Approach to Network Design When You’re In The Cloud http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/ Resources for Network / IT Business Decision Makers Tue, 22 May 2012 00:38:58 +0000 hourly 1 http://wordpress.org/?v=3.0 By: thsridhar http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-168666 thsridhar Fri, 10 Apr 2009 16:34:59 +0000 http://lippisreport.com/?p=1443#comment-168666 Nick, Your point above: _______ It’s not until fixed phones are replaced with virtualized soft UC phones and the majority of end-point connections are wireless that the access layer may be subsumed into a WLAN infrastructure. PoE support in the end will keep the access layer viable for years to come. ________ PoE might still be used to power the APs in a WLAN infrastructure but there will, of course, be far fewer APs than desktop IP phones needing PoE support. Sridhar Nick,

Your point above:

_______
It’s not until fixed phones are replaced with virtualized soft UC phones and the majority of end-point connections are wireless that the access layer may be subsumed into a WLAN infrastructure. PoE support in the end will keep the access layer viable for years to come.
________

PoE might still be used to power the APs in a WLAN infrastructure but there will, of course, be far fewer APs than desktop IP phones needing PoE support.

Sridhar

]]> By: thsridhar http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-168665 thsridhar Fri, 10 Apr 2009 16:30:23 +0000 http://lippisreport.com/?p=1443#comment-168665 PG Your point is valid - the challenge would be tie in the management of these tiers to a unified view, thus reducing some of the configuration complexity. Nick's outline above of the Cisco approach is relevant here: _____ The Nexus 2000 and 5000 may be two separate physical devices but they are logically one, making up the Cloud Access tier. In this scenario the Nexus 2000 is a line extender.... _____ Sridhar PG

Your point is valid – the challenge would be tie in the management of these tiers to a unified view, thus reducing some of the configuration complexity. Nick’s outline above of the Cisco approach is relevant here:
_____
The Nexus 2000 and 5000 may be two separate physical devices but they are logically one, making up the Cloud Access tier. In this scenario the Nexus 2000 is a line extender….
_____

Sridhar

]]> By: ppgandhi http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-155804 ppgandhi Thu, 26 Mar 2009 05:11:54 +0000 http://lippisreport.com/?p=1443#comment-155804 If one continues to assume that hypervisor switch is the new access (tiers don't need to be physical boxes), then isn't there a possibility of 4 tiers in a data center / cloud with a blade server deployment? Tier-1 (edge): hypervisor switch Tier-2: blade switch (with 10G uplinks) Tier-3: 10g aggregation (L2/L3) Tier-4: Core (L3) PG. If one continues to assume that hypervisor switch is the new access (tiers don’t need to be physical boxes), then isn’t there a possibility of 4 tiers in a data center / cloud with a blade server deployment?

Tier-1 (edge): hypervisor switch
Tier-2: blade switch (with 10G uplinks)
Tier-3: 10g aggregation (L2/L3)
Tier-4: Core (L3)

PG.

]]> By: mjmorris http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-193709 mjmorris Wed, 11 Mar 2009 18:53:33 +0000 http://lippisreport.com/?p=1443#comment-193709 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">very good article on DC network design in cloud/virtualized world...worth the 5 minute read.... http://is.gd/mVoR</span></span> very good article on DC network design in cloud/virtualized world…worth the 5 minute read…. http://is.gd/mVoR

]]> By: Nick Lippis http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-143942 Nick Lippis Mon, 09 Mar 2009 19:56:11 +0000 http://lippisreport.com/?p=1443#comment-143942 T Sridhar: Spanning Tree in cloud or other high end data centers and even in enterprise campus networks is fading as most seek to utilize trunk ports for moving traffic versus redundancy. KIshore Seshadri: I agree with your assessment. The bottom line is that there are conditions for 3 and 2 tier networking models. For now 2 tier in the cloud and potentially for private cloud implementations and 3 tier in traditional enterprise and data center implementations. T Sridhar: Spanning Tree in cloud or other high end data centers and even in enterprise campus networks is fading as most seek to utilize trunk ports for moving traffic versus redundancy.

KIshore Seshadri: I agree with your assessment. The bottom line is that there are conditions for 3 and 2 tier networking models. For now 2 tier in the cloud and potentially for private cloud implementations and 3 tier in traditional enterprise and data center implementations.

]]> By: KIshore Seshadri http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-143737 KIshore Seshadri Fri, 06 Mar 2009 19:01:54 +0000 http://lippisreport.com/?p=1443#comment-143737 Nick Won't the answer be different for different groups and different functions in a classic enterprise? I can see some apps that migrate to external clouds needing a fat pipe to an external cloud service provider but not needing the classic 3 tier architecture internally? You're likely to see similar shifts for collaborative apps that migrate to SaaS models. Internal apps will likely continue to be built around the 3 tier model. I can however see networks inside cloud service providers migrating to a 2 tier model since server-to-data relationships and locations will not be known a priori. This will likely drive the need for full mesh topologies where any server may need to communicate with any other server and/or data storage. The topologies described by Arista and others for cloud networking would make sense inside such networks. If internal clouds do take off and get to large scale, I can see such islands of 2 tiering inside enterprises as well. Nick
Won’t the answer be different for different groups and different functions in a classic enterprise? I can see some apps that migrate to external clouds needing a fat pipe to an external cloud service provider but not needing the classic 3 tier architecture internally? You’re likely to see similar shifts for collaborative apps that migrate to SaaS models. Internal apps will likely continue to be built around the 3 tier model. I can however see networks inside cloud service providers migrating to a 2 tier model since server-to-data relationships and locations will not be known a priori. This will likely drive the need for full mesh topologies where any server may need to communicate with any other server and/or data storage. The topologies described by Arista and others for cloud networking would make sense inside such networks. If internal clouds do take off and get to large scale, I can see such islands of 2 tiering inside enterprises as well.

]]> By: T Sridhar http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-143727 T Sridhar Fri, 06 Mar 2009 16:26:36 +0000 http://lippisreport.com/?p=1443#comment-143727 Enhancements/upgrades/alternatives to protocols like Spanning Tree Protocol (STP) are another data center networking trend. For example, the IEEE is working on Shortest Path Bridging (802.1AQ0 and the IETF is working on something similar called TRILL using Rbridges. Your thoughts? Enhancements/upgrades/alternatives to protocols like Spanning Tree Protocol (STP) are another data center networking trend. For example, the IEEE is working on Shortest Path Bridging (802.1AQ0 and the IETF is working on something similar called TRILL using Rbridges. Your thoughts?

]]> By: Nick Lippis http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-143501 Nick Lippis Tue, 03 Mar 2009 19:00:09 +0000 http://lippisreport.com/?p=1443#comment-143501 We are so early in the adoption cycle of cloud computing that there are many area that require research. The economic model, scale, management at scale, how virtualization fits into cloud, what is the unified fabric, one, two or three tiers of networking, network access to cloud, inter-connecting private and public clouds, etc etc etc We are so early in the adoption cycle of cloud computing that there are many area that require research. The economic model, scale, management at scale, how virtualization fits into cloud, what is the unified fabric, one, two or three tiers of networking, network access to cloud, inter-connecting private and public clouds, etc etc etc

]]> By: Cynthia http://lippisreport.com/2009/03/a-new-approach-to-network-design-in-the-cloud/comment-page-1/#comment-143271 Cynthia Fri, 27 Feb 2009 21:33:46 +0000 http://lippisreport.com/?p=1443#comment-143271 What would you consider to be a "problem" or "issue" that still requires some level of research to help advance Cloud Computing adoption? What would you consider to be a “problem” or “issue” that still requires some level of research to help advance Cloud Computing adoption?

]]>