Mavericks Invent Future Internet Where Cisco Is Meaningless
wired.com
wired.com
This specific product really only works in environments that are using linux based hypervisors (Xen/KVM/Openstack) in a datacenter environment. It doesn't address the typical campus network, or the more common ESX/ESXi/HyperV virtualization environments. The major block for most vswitches is VMware's lack of flexibility for other hypervisor network switches. The only option is the Nexus 1000V, and it's comparable to the dVs. The problem with both is that it requires Enterprise plus licensing which is roughly twice the cost of Standard.
In short, the difference between Nicira and the 1000V using VXLAN is not large. They both have hypervisors independent of switching fabric that allow large scale L2 flexibility. The only difference is hypervisor availability. It may be a while until we see VMware loosen up on their hypervisor, and equally time until things like the 1000V make it to Xen/Openstack.
Here's a better breakdown of what's actually happening for the networking/virtualization curious: http://blog.ioshints.info/2012/02/nicira-open-vswitch-inside... http://blog.ioshints.info/2012/02/nicira-uncloaked.html
Given the above and that most networking hardware is still configured by hardware engineers, this sector does seem ripe for disruption.
The challenging portion of configuring networks is keeping track of all the stacks and protocols. MAC, IP, virtual L2 features, virtual L3 features, virtual L2 with L3 features, routing virtualization, L2 loop detection/prevention, L3 loop detection/prevention, maximizing bandwidth without adding complexity or cost, multicast delivery strategy, broadcast/multicast control, best practices, and integration the application/TCP layer as well. I would say nearly all of those problems exist with or without something like OpenFlow, and it's already software. I love this part about networking, as every layer in the stack is modular and can be virtualized, so you're continually keeping track of protocols on top of protocols, and it all evolves so quickly. To say network engineers are no longer necessary after you virtualize networking is analogous to trying to cut 90% of server support staff once you're 90% virtualized. The added complexity may just compensate for the lack of hardware.
The other option is once the virtualization density is so high that virtual routers become feasible, and virtualized switches have more value, that you start to see 'hardware' go away. There are some very large cloud providers that are at this scale and can benefit, but the everyday enterprise isn't quite there yet. That's why these technologies are still a few years from mainstream, but they will definitely catch on.
Outside the datacenter, and even for the data center core, I think we'll continue to see customized silicon as opposed to commodity computing processors pushing the network traffic. Even the 'software' Google switches are on something like the Broadcom chip set, specific to network forwarding. Cisco's one of the few companies that develop their own chip set, which is one of the points of contention in the article, but they continue to find reasons to justify the cost.
Martin Casado is hellasmart. Nicira is the VMware of networking.
Check out Open vSwitch http://openvswitch.org/they all are like that. It's basically TED in print. With expensive watch ads.
This is, I think, the long term answer to both network neutrality and the IPv4 address crunch; IP could be relegated to a similar long-term role as Ethernet.
http://video.google.com/videoplay?docid=-6972678839686672840
I'm skeptical.
PC/Server virtualization didn't make IT go away, instead it made the job more complex. Now you need someone to run the VMware cluster and understand the nuances of virtualization. You still have a bunch of servers to patch and backup. And you still need the help desk to fix the same problems we've always had (printer doesn't work, my internet is down).
However, you gain a lot of flexibility and agility (which is the point of the article).
I've just not seen new technology reduce _technology_ jobs. In fact its usually the opposite. We need to coin some kind of catchy "law meme" like Greenspun's tenth rule, Conway's, Sturgeon's etc.
Meaning we get rid of the line workers making $25K/yr and replace them with expensive administrators making $60k/yr.
(Slightly tongue in cheek).
Highly skilled people may not be working with networking hardware per say, but they will certainly be doing networking.
With VMWare (and others) you had a fixed set of OS'es that mostly assumed a homogenous x86 platform to run on.
But this seems to be the opposite. You have a (very) heterogeneous physical layer and with a homogeneous software layer.
Anyone have any details on this?
I work at a telco with very heterogeneous network, we have to run a lot of separate and expensive (b/c of oracle/solaris licensing) management software to make this all work. So this is obviously interesting to me.
I could imagine some custom FPGA based modules that you could reprogram on the fly when you needed to regonfigure your networking hardware I am not sure what that buys you networking quipment doesnt have the scale that say a standard pc does apart from maybe acess level switches.
At this moment this seems to be more of a point and drool interface for those that cant hack IOS or pass the CCIE exam.
Turn your statement around: The easier networking gear can implement features, the easier to offer high speed, transparent encryption.
Incidentally, this year's summit starts today.