[irq]: techie interrupted




“ The end result is that compute-centric teams can create logical groupings that are not dependent on the configuration of the underlying network. Need a new logical grouping for some new line-of-business application? No problem, create it and start turning up workloads. Meanwhile, the networking-centric teams are free to design the network for optimal performance, resiliency, and cost-effectiveness without having to take the compute-centric team’s logical groups into consideration. Need to use a routed L3 architecture between pods/racks/ToR switches using VLANs? No problem—build it the way it needs to be built, and the network virtualization solution will handle creating the compute-centric logical grouping. „

Thinking Out Loud: The Future of VLANs - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers



“ If, however, someone tries to sell you software that’s supposed to control your physical switches, and does not support the usual set of protocols you need to integrate the OpenFlow-controlled switches with the rest of your network (example: STP, LACP, LLDP on L2 and some routing protocol on L3), think twice. If you use the OpenFlow-controlled part of the network in an isolated fabric or small-scale environment, you probably don’t care whether the new toy supports STP or OSPF; if you want to integrate it with the rest of your existing data center network, be very careful. „

Implementing Control-Plane Protocols with OpenFlow « ipSpace.net by @ioshints


“ The detail about the network that is unspoken when the idea of building cheaper network switches is discussed, is the ability to dynamically control and redistribute capacity. Capacity in the network is and has been constrained from the beginning. Capacity is constrained by the physical wires and the protocols that we run over the wires to allow for interoperability, fault detection and restoration. The idea of building overlay networks for virtualized machines is an attempt to solve the challenge of static capacity with programming. If all the compute resources are virtualized, it is possible to build an overlay network that can then move VMs around to pools of capacity in the network. „

Fluidity of Network Capacity, Commoditization, DIY Openness and the Demise of the Network Engineer | SIWDT


“ The reason is that it’s a new messaging protocol, where you don’t specify the recipients. New protocols are rare. Or more precisely, new protocols that take off are. There are only a handful of commonly used ones: TCP/IP (the Internet), SMTP (email), HTTP (the web), and so on. So any new protocol is a big deal. But Twitter is a protocol owned by a private company. That’s even rarer. „

Why Twitter is a Big Deal


“ The [Facebook] statistic was for every external 1kb HTTP request, they have a 930x increase in internal traffic. „

Self Similar Nature of Ethernet Traffic | SIWDT

“ The 2008 market crash left IT leaders with far too much IT infrastructure that was misplaced and misallocated to the needs of their customers. See the attached charts of CAPEX. Five years on from 2008 we are in a period of recomposition for the IT industry — especially the network. I suspect that 2014 through 2020 are going to big years in which nearly all the networks on global basis are going to be rebuilt. 2013 is the year in which IT leaders are working through the process of figuring out what the pieces of the new network will look like. Once those technology choices are made, we will be off and running. „

The Bigger Picture – Beyond Incrementalism | SIWDT

blog comments powered by Disqus
« previous | page 2 of 89 | next »
Tumblr » powered Sid05 » templated Disquss » commented