Tenant Networking in Public Clouds: Do We Still Need Networking Engineers?
Ivan Pepelnjak
Listening to so-called « thought leaders » one might believe that the move to public infrastructure cloud solves all the problems of this world. All of a sudden, the developers are empowered to deploy any application they wish, the networking and security engineers are obsolete, and everything works like a charm.
There’s a bit of a gap between this rosy picture and the reality. Tenant networking in public clouds is different from what we’re used to in the IP/Ethernet world, and it can get ridiculously complex once you start adding network services, inter-tenant connectivity, and direct connectivity to on-premises locations. Not only that, many of the concepts you master while working with one of the big public cloud providers does not apply to any other public cloud provider — they are all unique.
The presentation will focus on three main topics described above:
* How is public cloud networking different (and why)
* What are the major differences between big public cloud providers
* How complex can it get (and how slow it is to provision)
We’ll wrap up with a few recommendations one could follow when trying to survive this new onslaught of networking madness.
Ivan Pepelnjak: Ivan Pepelnjak has been designing and implementing large-scale service provider and enterprise networks as well as teaching and writing books about advanced technologies since 1990. He’s author of several Cisco Press books, prolific blogger and writer, occasional consultant, and author of a series of highly successful webinars and online courses. His current focus includes large-scale data centers and cloud deployments, network automation, and software defined networking (SDN) and data centers (SDDC).
Views : 1883
network engineer
