OpenFlow @ Google - Urs Hoelzle, Google
Why Hacker News recommends it
Cited as a primary source for Google building its own switches and running OpenFlow in production.
What it is
Urs Hoelzle, Google's SVP of infrastructure, gives the 2012 Open Networking Summit keynote on how Google adopted OpenFlow and software-defined networking in its own networks. The slides are linked in the description.
Recommended by 1 HN commenters across 1 different months, 2013 to 2015.
What Hacker News said
Recommends jzelinskie · 2013-05 · on “Return of the Borg: How Twitter Rebuilt Google’s Secret Weapon”
Honestly, everyday I'm continually impressed by posts describing the internal technology powering Google. Having an abstraction layer like this for global deployment couldn't be more convenient. With the news about Facebook the other day, I watched a talk on OpenFlow ( [this video] ) and the fact that they have a test suite they can plug into continuous integration in order to see if your commit breaks your application in any network situation is incredible. I'd love to sign an NDA and just talk to the teams working on these projects for hours. Truly impressive work.
Cites Ironlink · 2013-05 · on “ Facebook aims to knock Cisco down a peg with open network hardware”
For those interested, Google has been using OpenFlow for some time now. This presentation by Urs Hölzle is about a year old: [this video] Slides: [LINK]
Cites dmayle · 2013-12 · on “Why Google isn't our Bell Labs”
I may be a bit biased, because I'm a Googler... but looking through this thread and seeing all the people downplaying Google's contributions to Go, Android and Dart. As if they were minor... But what about all of the papers that have changed the way the world does computing? Some choice links below: MapReduce [LINK] BigTable [LINK] Dremel Paper [LINK] Chubby Paper [LINK] Urs Holzle on OpenFlow: [this video] Megastore Paper [LINK] Spanner Paper [LINK] Granted, some of these will take awhile before having implementations outside of Google... but you can't deny the impact of this work...
Cites thomseddon · 2015-01 · on “How We Failed at OpenStack”
>> >> You see, physical switch operating systems leave a lot to be desired in terms of supporting modern automation and API interaction (Juniper’s forthcoming 14.2 JUNOS updates offer some refreshing REST API’s!). >> This. Network hardware vendors have no incentive to make their devices more easily automated, and in fact face disincentive not to. There is actually a relatively established roadmap for the solution to this in "bare metal" / "white box" switches that essentially just talk OpenFlow to a controller. Google moved their entire international internal backbone (more traffic than public facing) to this model[1]. The issue at the moment is that there isn't lots of OS options and subseq