The cloud giant's Network Intelligence Center packs four tools aimed at helping customers monitor,...
Today we start the next chapter in the Docker story, one that’s focused on developers. That we have the opportunity to write this next chapter is thanks to you, our community, for without you we wouldn’t be here. And while our focus on developers builds on recent history, it’s a focus also grounded in Docker’s beginning.
When Solomon Hykes, Docker’s founder, unveiled the Docker project in 2013, he succinctly stated the problem Docker aimed to solve as, “for a developer, shipping code to the server is hard.” To address, Docker abstracted out OS kernels’ complex container primitives, provided a developer-friendly, CLI-based workflow and defined an immutable, portable image format. The result transformed how developers work, making it much easier to build, ship and run their apps on any server. So while container primitives had existed for decades, Docker democratized them and made them as easy to use as
docker run hello-worldThe rest is history. Over the last six years, Docker containerization catalyzed the growth of microservices-based applications, enabled development teams to ship apps many times faster and accelerated the migration of apps from the data center to the cloud. Far from a Docker-only effort, a Continue reading
Companies including Inspur and Dell Technologies sell Liqid’s switch and software inside their...
Do you need an LSP for MPLS ?
In this post, I will go through below topics. This is one of the points which network engineers struggle to understand as I have seen.
Network mergers and acquisitions are the processes which can be seen in any type of businesses. As a network designers, our job to identify the business requirements of both existing networks and the merged network and finding best possible technical solutions for the business.
Quality of service (QoS) is the overall performance of a telephony or computer network, particularly the performance seen by the users of the network.
What is tier in the first place ? If you are dealing with Service Provider networks, you hear this term a lot. But how we define Tier 1,Tier 2 and Tier 3 Service Providers ?
What is reliability in networking ? Why reliability is an important design tool ? I will provide the answers of these questions with the examples in this post.
Is fate sharing bad thing in network design? Someone asked this question recently on my youtube channel and I want to share a post for the website followers as well.
First of all, what is fate sharing ? Below is the Wikipedia definition of fate sharing.
Do we still lose packet with fast reroute? One of my students asked me this question. And I would like to share the answer with everyone.
Couple days ago I discussed some IP Mobility solutions, including LISP (Locator Identity Separation Protocol) with the CCDE students.
Don’t expect technical topic in this post. Instead I wanted to show how was my situation before and after the CCDE – Cisco Certified Design Expert !. Enjoy 
Fast Convergence and the Fast Reroute Network reliability is an important design aspect for deployability of time and loss sensitive applications. When a link, node or SRLG failure occurs in a routed network, there is inevitably a period of disruption to the delivery of traffic until the network reconverges on the new topology.
Technology prototypes tested and validated by the group are now commercially available and being...
One of my readers sent me a question along these lines…
VXLAN Network Identifier is 24 bit long, giving 16 us million separate segments. However, we have to map VNI into VLANs on most switches. How can we scale up to 16 million segments when we have run out of VLAN IDs? Can we create a separate VTEP on the same switch?
VXLAN is just an encapsulation format and does not imply any particular switch architecture. What really matters in this particular case is the implementation of the MAC forwarding table in switching ASIC.
Read more ...Scaling symbolic evaluation for automated verification of systems code with Serval Nelson et al., SOSP’19
Serval is a framework for developing automated verifiers of systems software. It makes an interesting juxtaposition to the approach Google took with Snap that we looked at last time out. I’m sure that Google engineers do indeed take extreme care when building the low level networking code that powers Google’s datacenters, but their fundamental design point was to enable frequent releases for fast iteration, feedback on their designs, and yes, early detection of problems.
Formal verification is at the other end of the spectrum. In theory it enables you to eliminate whole classes of problems and vulnerabilities entirely (in practice perfection is still hard to come by), and so it can be especially valuable in security sensitive situations. But it comes with a very high price tag:
Writing proofs requires a time investment that is usually measured in person-years, and the size of the proofs can be several times or even more that an order of magnitude larger than that of implementation code.
That’s both very expensive and an incredibly long wait for feedback. To invest in formally modelling something, you really Continue reading