It’s that time of the year again - a new OpenStack Summit is around the corner! And this time it’s being hosted at Austin, Texas.
We are excited to be at the summit to share what we have been doing with Contrail in the networking space. There is a lot of work that has happened over the last few months, especially Contrail and its relevance in the Container ecosystem.
Telecommunication service providers have evolved over the decades, but fundamentally they are still operating the original business model: Build infrastructure and sell services over it.
There are many industries that have been disrupted by new entrants, taking adavntages of digital transformation: Uber has dirsupted the taxi, AirBnB disrupts the hospitality market, Kodak was disrupted by digital photography...
Will you be the Service Provider disrupting the telco space, or will you be the Service Provider disrupted by others?
This blog describes the story of a customer whose data center network is growing very fast, to the point that their traditional access-aggregation-core layer 2 architecture starts crumbling. It explains how EVPN-VXLAN solves the scaling issues by introducing a layer 3 IP fabric without having to give up layer 2 services for the applications (thus avoiding a rewrite of the application).
Here is a great blog by my intern Animesh Kumar. He worked for my over the summer and created a great tool Ptolemy: The Network Cartographer. For me it was an amazing experience and I am so happy to have had Animesh working for me this summer.
By Animesh Kumar:
During my initial years of work in IT industry I used to work on Automation of test suites for the tools I had developed or the APIs I had written. My notion about Automation at that time was to make everything in a program or tool run automatically without any manual effort. One click of a button and it should run all the scenarios by itself, covering all the possible test cases and corner cases. For doing this, I used to think of all the possible test cases, negative or positive and automate the testing for it. But every time a new bug came in and my test suite failed catching it, used to frustrate me a lot that even after putting in so much effort, I was unable to automate the testing.
I often get asked, “Where does the automation come from?” This makes me think of a great safari trip where only the keenest hunters could go and find the automation. It could be in a tree or perhaps over behind that rock. Sometimes people even ask me for automation that makes the automation for you. Then my mind shifts to a hospital and walking past the nursery filled with all sorts of newborn automations with the proud automation parents. While both would be great automation fan fiction the truth is much more mundane, automation comes from the need to solve a workflow in an automated methodology or process.