The networking industry is changing rapidly with demand for more dynamic control of big data, and scale-out cloud applications. The inevitable shift to software-defined workloads and workflows is crystal clear. This calls for more “disaggregation” of software models for the network stack.
Should networking move to a more open standards-based approach or continue with legacy stacks? The answer is defined by considering the following three options for networking software stacks, and the actual choice depends on the factors as shown below in Figure 1.
1. Classic OS: The established network vendors tend to develop multi-million lines of complex software code with enterprise or service provider class features for LAN or WAN. This closed monolithic “Blob-OS” model can be based on modified and proprietary versions of a BSD or Linux Kernel. Traditional enterprise support is the hallmark of this model, but innovation is rarely evident. Claims of programmability usually include band-aid APIs, or guest virtual machine access. The classic OS addresses mature markets akin to a mainframe usually for customers with siloed IT stacks that support legacy applications.
2. Cloud OS: At Arista, our software engineers build based on an open Linux Kernel, providing programmable capabilities that legacy switch-based Blob-OSs do Continue reading
The networking startup, spun out of DreamHost, gets some OpenStack clout.
Startup has raised nearly $100M in the name of networking-as-a-service and the software-defined WAN.
mkdir usbflash:/MY_ROOT_CA
crypto key generate rsa label MY_ROOT_CA modulus 2048 exportable storage nvram:
Two years later it's time for an update.