Doubling-down on OpenFlow

I’m incredibly happy to announce that I’ve joined to help lead our efforts around open source, including Floodlight, the world’s only apache-licensed SDN controller, and Indigo, an OpenFlow agent for physical switches.

First, a little bit about me:

In 2006 I co-founded and ran engineering and operations for GoGrid ( , one of the world’s first cloud computing service providers. After growing GoGrid to span two continents and service over 10,000 enterprise users using only open-source tools (and what was at the time the second largest Xen deployment next to Amazon EC2) I decided to refocus my efforts on where I saw most of the adoption of cloud would be happening:  private deployments inside of enterprises providing automated self-service to internal development and IT groups.  I ended up helping Piston Cloud ( – who was building a distribution of OpenStack – bring their product to market, until my friend Kyle Forster @ Big Switch told me that he was looking for someone to help grow out their open source efforts that include Floodlight and Indigo.

Now, I had been keeping my eye on OpenFlow and SDN since 2007 when Martin Casado pitched us his idea to connect virtual hosts via dynamically provisioned (what were then GRE) tunnels when we were trying to figure out how to scale the GoGrid network (we decided the technology was too immature). So my first reaction to Kyle was “why does Big Switch need an open source strategy?”. After all it’s no secret that it’s very difficult to make money selling open source technology. Not saying it’s impossible – obviously companies like Redhat have found the secret – but unless your market is gigantic and product is extremely easy to deploy and support, it becomes very difficult to turn a profit. And as a startup in the incredibly competitive enterprise infrastructure market and competing with a giant like Cisco, you could say I was “cautiously intrigued” by the idea.

I wanted to be sure that Big Switch was serious about doing what it takes to truly create a vibrant open source community – the most important attribute of which is a diverse set of contributors who are not dominated by one company or influenced by commercial interests.

After spending a few weeks with the team, a few things became obvious:

— Big Switch’s commercial products have an incredibly compelling value proposition (hint: it’s all about the Apps)
— Floodlight represents the “core” of the commercial product (that is still in Beta), and
— with Floodlight, we have the opportunity to define the de facto standard for controller APIs
— we have assembled the best engineering team for SDN in the world

I look forward to diving into this in much more detail as we become more public about our plans, but I can say that I’m incredibly excited about the opportunity that we have in front of us, and what this means for developers and users of SDN technologies as we disrupt the world of network infrastructure.

You can reach me anytime at or email to the floodlight-developer group.

Comments are closed.