Open source software has done a lot to transform the IT industry, but perhaps more than anything else it has reminded those who architect complex systems that all elements of a datacenter have to be equally open and programmable for them to make the customizations that are necessary to run specific workloads efficiently and therefore cost effectively.
Servers have been smashed wide open in large enterprises, HPC centers, hyperscalers, and cloud builders (excepting Microsoft Azure, of course) by the double whammy of the ubiquity of the X86 server and the open source Linux operating system, and storage has followed suit …
The Walls Come Down On The Last Bastion Of Proprietary was written by Timothy Prickett Morgan at The Next Platform.
The post Worth Reading: The end of the hypervisor appeared first on 'net work.
Building high performance systems at the bleeding edge hardware-wise without considering the way data actually moves through such a system is too common—and woefully so, given the fact that understanding and articulating an application’s requirements can lead to dramatic I/O improvements.
A range of “Frequently Unanswered Questions” are at the root of inefficient storage design due to a lack of specified workflows, and this problem is widespread, especially in verticals where data isn’t the sole business driver.
One could make the argument that data is at the heart of any large-scale computing endeavor, but as workflows change, the habit of …
Framing Questions for Optimized I/O Subsystems was written by Nicole Hemsoth at The Next Platform.
Flow-based load balancing is used mostly in layer 2 networks, although in Layer 3 routing, packets can be load balanced per packets or per flow, flow-based load balancing is commonly used with the Local area network, datacenter and datacenter interconnect technologies. There are two important load balancing mechanisms in layer 2. Vlan-based load balancing and […]
The post What is flow-based load balancing ? appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
As a keen observer of the network engineering world for the last twenty… okay, maybe longer, but I don’t want to sound like an old man telling stories quite yet… years, there’s one thing I’ve always found kind-of strange. We have a strong tendency towards hero worship.
I don’t really know why this might be, but I’ve seen it in Cisco TAC—the almost hushed tones around a senior engineer who “is brilliant.” I’ve seen it while sitting in a meeting in the middle of an argument over some technical point in a particular RFC. Someone says, “we should just ask the author…” Which is almost always followed by something like: “Really? You know them?”
To some degree, this is understandable—network engineering is difficult, and we should truly honor those in our world who have made a huge impact. In many other ways, it’s unhelpful, and even unhealthy. Why?
First, it tends to create an “us versus them,” atmosphere in our world. There are engineers who work on “normal” networks, and then there are those who work on, well, you know, special ones. Not everyone needs those “special skills,” so we end up creating a vast pool of people Continue reading
Also: Why networking should follow the example of graphics chips
What does PE-CE mean in the context of MPLS ? What is CE , P and PE device in MPLS and MPLS VPN ? These are foundational terms and definition in MPLS. MPLS is one of the most commonly used encapsulation mechanism in Service Provider networks and before studying more advanced mechanisms, this article is […]
The post What does PE-CE mean in MPLS ? appeared first on Cisco Network Design and Architecture | CCDE Bootcamp | orhanergun.net.
The Docker open source project is among the most successful in recent history by every possible metric: number of contributors, GitHub stars, commit frequency, … Managing an open source project at that scale and preserving a healthy community doesn’t come without challenges.
This post is the last of a 3-part series on how we deal with those challenges on the Docker Engine project. Part 1 was all about the people behind the project, and part 2 focused on the processes. In Part 3, we will cover tooling and automation.
There are many areas for automation in a project such as Docker. We wanted to present and share some of our tooling with you: the CI, the utility bots, and the project dashboards.
IT Security Engineering. At Gusto we are on a mission to create a world where work empowers a better life. As Gusto's IT Security Engineer you'll shape the future of IT security and compliance. We're looking for a strong IT technical lead to manage security audits and write and implement controls. You'll also focus on our employee, network, and endpoint posture. As Gusto's first IT Security Engineer, you will be able to build the security organization with direct impact to protecting PII and ePHI. Read more and apply here.
Awake Networks is an early stage network security and analytics startup that processes, analyzes, and stores billions of events at network speed. We help security teams respond to intrusions with super-human efficiency and provide macroscopic and microscopic insight into the networks they defend. We're looking for folks that are excited about applying modern bleeding edge techniques to build systems that handle scale in a constrained environment. We have many open-ended problems to solve around stream-processing, distributed systems, machine learning, query processing, data modeling, and much more! Please check out our jobs page to learn more.
Site Reliability Engineer Manager. We at Spotify are looking for an engineering leader (Chapter Continue reading
The 10GbE network interface card is rarely the bottleneck on the average enterprise host. So who needs 25GbE? The answer is about what you will need tomorrow versus what you do need today.
The post The Case for the 25GbE Access Layer appeared first on Packet Pushers.
An edge router is a very pricey box indeed, often costing anywhere from $100,000 to $200,000 per 100 Gb/sec port, depending on features in the router and not including optical cables that are also terribly expensive. Moreover, these routers might only be able to cram 80 ports into a half rack or full rack of space. The 7500R universal spine and 7280R universal leaf switches cost on the order of $3,000 per 100 Gb/sec port, and they are considerably denser and less expensive. - Leaving Fixed Function Switches Behind For Universal LeafsBroadcom Jericho ASICs are currently available in Arista 7500R/7280R routers and in Cisco NCS 5000 series routers. Expect further disruption Continue reading