ONUG Spring 2015 & the Cancer of Vendor Sponsorship

Based on feedback from attendees of earlier ONUG events, I was looking forward to this conference. Right now, most of my customer conversations are at the “1a” level (“What is SDN? What does my company mean when we say SDN?”). There are certainly some that are more sophisticated (we have paying customers for our controller, after all), but I was looking forward to a concentrated gathering of users to hear what’s on their minds.

Here are my observations from Day 1:

Speaking of vendors–most of the vendor attendees were small startups, many in the SD-WAN space. Of the established players, Juniper was notably absent. And despite the clear interest in white-box with this group, Cumulus opted not to invest in this event.

There were some bright spots, notably Adrian Cockcroft’s talk about how to DevOps. You can view his slides here. Ted Turner from Intuit (Ananda Rajagopal’s guest) later in the day talked about how Intuit is taking 15-year-old apps and breaking them into microservices, and then leveraging AWS for the non-core portions of the app workflow. The reliance on AWS for a significant portion of one’s IT operations was actually a fairly common theme in both speaker and offline comments.

Unfortunately, the rest of Day 1 was given over to “Working Group test results presentations”, aka the aforementioned vendor panels. Or as Andre Kindness of Forrester put it:

Today the morning sessions were closed to us vendors–fair enough, I suppose…on the one hand, I can appreciate users’ desire for frank discussions without getting aggressive phone calls to their management from certain suppliers. On the other hand, hearing what users are really struggling with (which isn’t always the same thing as engineering’s neat ideas) is always instructive for those of us who might be in a position to help provide solutions. I’d be good with seats in the peanut gallery and a strict behind-the-red-velvet-rope, listen-only policy for vendors for these sessions–especially since there was no bar on media attendees.

The first open session of today featured Najam Ahmad of Facebook. Facebook is doing some very interesting things with their infrastructure, and although it’s certainly not, in its entirety, a blueprint for most other companies, there are always interesting nuggets in their presentations that can be applied in other contexts. For example, when an audience member asked about getting the right skillsets in the networking organization, here’s what he said (slightly paraphrasing):

“We have a free-hacking month once a year. Anyone can go work on any team they’re interested in, and at the end of the month, if they want, they can stay with that team, or go back to their old team. For a while we weren’t getting any of the software engineers. Networking just seemed boring and weird to them. Then we started framing it as a big distributed systems project, and that started drawing them in. Then you have the problem of developers not knowing much about networking and vice versa, so we paired networking people with software devs and had them work together on projects, with the expectation that each would learn from the other. Now everyone on our team codes, to some extent. Some more, some less, but they all have an appreciation for each others’ knowledge and skills.”

There were some luncheon sessions that I couldn’t stay focused on because they mostly had the same problem as Day 1’s panels. This was followed by an investor panel, which mostly focused on two questions:

  1. Will SDN/NFV/whitebox hurt Cisco?
  2. What are the prospects for startups in these areas?

On #1, the view was that if Cisco and other established networking vendors lay down strong strategies now, once we start seeing active deployments a year or so from now, it shouldn’t make a significant difference for them. The hype around SDN of a year or so ago, which appeared to be hurting Cisco’s stock price, has died down as the reality of the length of this transition (10 years, one speaker posited, which seems very likely) has set in, and there’s plenty of time to get the go-to-market execution in place. Interestingly, the institutional investor commented that he didn’t see VMware NSX breaking out beyond the security segmentation use case it’s currently positioning. NSX’s architecture as a vertically integrated software stack anchored to a specific hypervisor probably does limit its use cases more than other, more general-purpose controllers, but given the very long runway the same speaker gave other vendors in the space to work out their strategies, I was left wondering what other knowledge and commentary was behind the comment.

On #2, no one expected any significant moves to IPOs or strong exits in the next year, owing to the expected leadtime on real SDN deployments. One speaker also commented that the bar would likely be higher for IPOs than in past cycles, with an expectation that the company actually be making money before entering into the public markets. That would be refreshing, wouldn’t it?

The final session today was a discussion on DevOps, which was covered very adequately by other bloggers. In fact, here are links to several other live blogs posted by my Networking Field Day friends:

ONUG Spring 2015 Live Blog – Day 1 (Ethan Banks)

ONUG Spring 2015 Live Blog – Day 2 (Ethan Banks)

Tom Hollingsworth/John Herbert – Day 1

Liveblog from ONUG Day 2 (John Herbert)

Now, about the “cancer” comment in the title of this post: I had gone all the way over to the other side of the world (Paris, not horrible) in March to the MPLS/SDN/NFV World Congress, having heard good things about it from past attendees. I heard from the same people (vendors) I’ve heard from many times at conferences in the US. I already know my colleagues’ and competitors’ schticks. I don’t need to hear it again. ONUG turned out to be much the same. I said this to an analyst friend at Gartner Data Center a couple of years ago. I’m dreading ONS at this point. I get that events are revenue opportunities (and for Mr. Lippis of ONUG, a primary one), and also that when vendors pony up large chunks of money to help cover the costs of the events, the marketing departments expect something (visibility, since the value of leads is honestly very negligible) in return. But–YUCK. I know I’m not the only one who’s tired of hearing the same thing at every event. There have to be other, better ways to do this.

Update: Some ideas to get the ball rolling here.

Advertisements

First, Let’s Define the Problem

So, Women in Tech. It’s become a hot topic in the last year. That’s a good thing in many ways. It also means, as happens with most hot topics, that lots of ideas and statistics get thrown around, increasingly willy-nilly and context-free. This is less good, because it tends to make the conversation more heated without producing anything useful as a result, and because it means that while more people can recite depressing stats and thereby convince themselves they’re enlightened, there isn’t actually any deeper understanding of the problem for most.

Which brings me to my next point: which problem, exactly? The real answer of course, is that there are many, and often they’re linked to one another, but far too many articles on the Women in Tech topic recite a litany of statistics (most of which are from studies about women workers in all industries, or write-ups of polls of college students) that relate to a bunch of different problems and then conclude “Tech Hates Women!”

I take issue with this. Continue reading

Books I Read in 2014

Often when you read interviews with business leaders, they get asked about their favorite book, or what they’re currently reading. Invariably the answer is some business tome, which led me to make this observation one day:

Continue reading

Deploying Out of Context: Behavioral Findings

I conducted a practical anthropology experiment recently: I wore an 18th century dress with a long train out to a masquerade-themed event, and then to a private party. Some of the things I learned about how unfamiliar things affect behavior were unexpected, and applicable outside the realm of retro fashion. I detail my findings below.

Introduction

You get dressed every day. You’ve been doing it for years. You might give some thought in the morning to the design of how you will be presenting yourself that day, but probably almost none to the mechanics of getting dressed and moving about in your clothes.

You can do that because the clothes you own are designed for the social context AND the physical environment in which you operate. But change any of those things and you quickly find you have to adapt to all of them. Continue reading

If content is created, does it have to make a sound?

Amy Lewis just published a post I like a lot, “Consume and Be Thankful“. The executive summary is “Shut up and listen”. In other words, publishing content should not be the sole focus of being a community member, much less a leader. This is exactly the opposite approach advocated lately by Om Malik, Greg Ferro and others, challenging themselves and others to publish 30 blogs in 30 days. Continue reading

Reflections on Armistice Day

I’m just off the plane from France, where I combined the OpenStack Summit with a family vacation. As we landed, the American flight attendant explained to the plane that it was Veteran’s Day in the U.S., which means that we thank our veterans for their service. I was bitterly amused.

Why?

In Europe November 11th is Armistice Day. It celebrates the day peace was made at the end of the “War To End All Wars”–WWI. When I lived in the Pas de Calais, where most of it was fought, it was still living memory for old folks, a somber day of wearing black and visiting graves, and remembering the horrors of that time, and being thankful for peace. I found it horribly ironic that this woman, who clearly had no notion of the history of this particular date, felt she was positioned to teach half the plane about it. Continue reading

A Simple Definition of “Open”

I wrote this into an internal FAQ today:

Q: What does “open” really mean?

A: “Open” is used in a variety of ways. An “open” API is an interface that uses standard protocols, tools and models and that can be written to by customers and third-party developers. An API is not, by itself, “open source”. Open source describes a development model in which anyone at all is free to download, improve upon and, with the agreement of the developer community, contribute code to a particular project. It is common to use open source components, often from many different projects, as building blocks of a proprietary piece of commercial software. Increasingly, there are open source projects, including OpenStack and OpenDaylight, which seek to deliver a complete and wholly open solution.

I like it, but given how freighted the whole topic is, it seems rather daringly simple and straightforward. So, dear readers, what nuances, caveats and gotchas am I missing?

An Educational SDN Use Case

I was going to blog about Tom’s comments on the VMunderground Networking panel–which were the highlight of the panel, to me–during the week of VMworld. But I wanted to include the video, which only got posted recently. Fortunately for all, Tom has further elaborated his thoughts AND included the video on his own blog, which I’ve shared below.

The Networking Nerd

During the VMUnderground Networking Panel, we had a great discussion about software defined networking (SDN) among other topics. Seems that SDN is a big unknown for many out there. One of the reasons for this is the lack of specific applications of the technology. OSPF and SQL are things that solve problems. Can the same be said of SDN? One specific question regarded how to use SDN in small-to-medium enterprise shops. I fired off an answer from my own experience:

Since then, I’ve had a few people using my example with regards to a great use case for SDN. I decided that I needed to develop it a bit more now that I’ve had time to think about it.

Schools are a great example of the kinds of “do more with less” organizations that are becoming more common. They have enterprise-class networks and needs and live off budgets that…

View original post 611 more words

On Success and Happiness

Robin Williams died today. Normally I don’t give much thought to celebrity deaths—what about all the other people who died today? is my usual unvoiced response to the expressions of sadness that promptly pour out on social media. But this one struck me for a few different reasons.

Much of my generation of Americans grew up with Williams in his most goofy and manic role, Mork from Ork. His later roles, even the relatively serious ones, continued to be driven by the manic motormouth compulsion that first brought him fame. They were leavened by an increasing humanity, but it was clear that giving free rein to his frenetic free association was what really energized him. I had the opportunity to see him live twice—he lived in Marin and would occasionally test out new material at a smallish club in San Francisco—and his barely contained energy, which would grow over the evening as he got going, was practically a force of a nature that swept everyone in the room along with him. It’s hard to imagine Williams surviving, yet alone thriving, in any other profession. Watching him live, I became convinced that Mork the alien was the real Williams, and that he spent much of his later years trying to figure out how to be human. His more touching moments on screen typically had to do with realizing and articulating a failure to be what other characters needed his to be. Continue reading

Response: Open Networking: The Whale That Swallowed SDN

Art Fewell, whose views I greatly respect, has written a very good post on Network World entitled “Open Networking: The Whale That Swallowed SDN“. It’s a great historical summary of SDN 2011-present, with some noteworthy areas of concern. I agree with the general thrust of Art’s thesis, yet at many points I found myself thinking “Yeah, but…” I started to write a few comments on the Network World page, but the comments turned into a page, so here we are.

Here’s what I really liked in Art’s piece: Continue reading