Monthly Archives: July 2010

Rackspace and OpenStack

Rackspace is open-sourcing its cloud software — Cloud Files and Cloud Servers — and merging its codebase and roadmap with NASA’s Nebula project (not to be confused with OpenNebula), in order to form a broader community project called OpenStack. This will be hypervisor-neutral, and initially supports Xen (which Rackspace uses) and KVM (which NASA uses), and there’s a fairly broad set of vendors who have committed to contributing to the stack or integrating with it.

While my colleagues and I intend to write a full-fledged research note on this, I feel like shooting from the hip on my blog, since the research note will take a while to get done.

I’ve said before that hosters have traditionally been integrators, not developers of technology, yet the cloud, with its strong emphasis on automation, and its status as an emerging technology without true turnkey solutions at this stage, has forced hosters into becoming developers.

I think the decision to open-source its cloud stack reinforces Rackspace’s market positioning as a services company, and not a software company — whereas many of its cloud competitors have defined themselves as software companies (Amazon, GoGrid, and Joyent, notably).

At the same time, open sourcing is not necessarily a way to software success. Rackspace has a whole host of new challenges that it will have to meet. First, it must ensure that the roadmap of the new project aligns sufficiently with its own needs, since it has decided that it will use the project’s public codebase for its own service. Second, it now has to manage and just as importantly, lead, an open-source community, getting useful commits from outside contributors and managing the commit process. (Rackspace and NASA have formed a board for governance of the project, on which they have multiple seats but are in the minority.) Third, as with all such things, there are potential code-quality issues, the impact of which become significantly magnified when running operations at massive scale.

In general, though, this move is indicative of the struggle that the hosting industry is going through right now. VMware’s price point is too high, it’ll become even higher for those who want to adopt “Redwood” (vCloud), and the initial vCloud release is not a true turnkey service provider solution. This is forcing everyone into looking at alternatives, which will potentially threaten VMware’s ability to dominate the future of cloud IaaS. The compelling value proposition of single pane of glass management for hybrid clouds is the key argument for having VMware both in the enterprise and in outsourced clouds; if the service providers don’t enthusiastically embrace this technology (something which is increasingly threatening), the single pane of glass management will go to a vendor other than VMware, probably someone hypervisor-neutral. Citrix, with its recent moves to be much more service provider friendly, is in a good position to benefit from this. So are hypervisor-neutral cloud management software vendors, like

Bookmark and Share

HostingCon (and Booth Babes)

I’m on my way home from HostingCon. I wish I had decided to stay an extra day. I originally expected I’d give my Monday keynote and be free to roam and have various conversations with random people, have plenty of time to wander the show floor, and so on. Instead, my schedule filled up rapidly with clients and friends-of-clients (for instance, folks with relationships with our investment banking clients who tugged some strings), plus other folks who grabbed me on email beforehand.

Great things have happened with the show since iNet Interactive took over running it — the audience has become much more diverse in terms of the types of attendees, and in general, it’s a smoothly-run, very professional show, quite a change from the past. I enjoyed having the chance to deliver the opening keynote, as well as my formal and informal conversations with people.

I wish I’d had more time than the 30 minutes I had to spend on the show floor. But there’s been a very interesting backchannel discussion happening on Twitter #HostingCon) that I want to highlight, and that’s the subject of booth babes.

Much to my surprise, there were several exhibitors who brought booth babes — you know the classic sort, in super-skimpy outfits, arrayed in front of their booths. A number of female attendees have called this out on Twitter, but just as interesting are the retweets and supporting objections that come from male attendees. This was particularly stark because of the near total absence of women from the conference; the attendance is overwhelmingly male, and so there was little female representation in either attendees or exhibitors. This was true to even a far greater extent than I’m accustomed to seeing at IT conferences.

So, vendors, here’s a set of reasons why you should not bring booth babes. (And especially not to something like HostingCon, where much of the audience is C-level executives, and it’s all about the business and networking.)

1. You imply your audience is immature and/or unprofessional. Booth babes imply that you think that your audience’s primary interest is in staring at boobs, as opposed to getting serious business done. Moreover, there’s no way to look professional while ogling, and even those people who would like to ogle don’t want to do so in front of people that they’re doing business with. Unless you’re E3 and your audience is adolescents and overgrown adolescents, this is a bad tactic. (And you can argue that booth babes ended up significantly contributing to the death of E3 as a serious trade show.)

2. You imply that your company’s offerings are less interesting than the flesh on display. Yes, everyone needs to do something to draw in traffic, but booth babes smack of desperation. But you do this by having a compelling display that makes people want to come have conversations, not by having booth babes shoving trinkets at people. People grab the trinkets and then don’t have the conversations.

3. You actually make it harder for people to get to the booth itself. This is especially true on crowded show floors, where the booth babes basically form a wall in front of your booth. This makes it hard to see your display, your collateral, and the nametags of the people you have staffing your booth (important for any attendee who is trying to do some networking). Chances are that a lot of people simply don’t make it through the obstacle, especially if they’re casually perusing the floor, rather than looking for you specifically.

I chose not to talk to any exhibitor with booth babes. It wasn’t really a principle thing; I’m not actually offended, just bemused. It was simply a practical matter.

I don’t think conference organizations necessarily need to have rules against booth babes, per se. I simply think that companies should exercise good sense when thinking about where they’re exhibiting and who they’re exhibiting to.

Bookmark and Share

%d bloggers like this: