Blog Post

Examining the latest OpenStack spat

So what’s the real deal with OpenStack driver compatibility efforts?

Last week, Mirantis stepped forward, pushing what it called a multi-vendor open-source driver certification effort for drivers that work with OpenStack. The goal is a no-brainer — making sure software and hardware from many companies can easily work in the OpenStack cloud ecosystem.

Mirantis co-founder Boris Renski told me that VMware(s vmw), Netapp(s ntap), Dreamhost and other companies were aboard. Interestingly, driver certification — indeed certification of all kinds — is a point of pride for Red Hat(s rhat), another OpenStack player, and the one that, arguably, has become the most influential in the OpenStack cosmos. Red Hat’s name was conspicuously absent from the Mirantis list and about an hour before Mirantis announced this effort, Red Hat(s rhat) posted a blog of its own, touting the value of its certification efforts.

Why can’t we all just get along?

A Rackspace(s rax) spokeswoman said that company is “actively reviewing the Mirantis program” but other OpenStack players said there already is a community process in place that will accomplish the same goal. Dreamhost CEO Simon Anderson referred me to the OpenStack DefCore committee and noted that Mirantis “overreached” in claiming Dreamhost as an adherent to its program.

The CEO of another OpenStack-focused vendor said that the DefCore committee, established in November at the last OpenStack Summit in Hong Kong, will take care of driver issues “but that’s not a Mirantis story.”

Renski explained to eWeek how what Mirantis proposes differs from the DefCore’s RefStack effort. While Refstack will define API-level tests for specific OpenStack implementations and distributions to pass so that they can use the OpenStack label. But, Renski said:

“What we are doing is about exposing objective information with regard to drivers and plug-ins that third-party vendors write (like NetApp, VMware, Ceth [sic], etc.) about compatibility with particular versions of OpenStack.”

Look, we all get that OpenStack is being pushed by a variety of competing interests — I mean both IBM and HP tout OpenStack as key to their respective cloud strategies — but to the outside world all this vendor drama is a distraction and probably not a positive thing for overall OpenStack adoption

Dueling cloud conferences

March is going to be a busy month for public cloud aficionados. On February 4, Amazon Web Services sent out save the date notices for the AWS Summit in San Francisco March 26. featuring SVP Andy Jassy and a full day of events and talks. On February 12, Google cloud chief Urs Hölzle announced Google Cloud Platform Live in San Francisco on March 27. Talk about vs. aws

This week’s Structure show

New Rackspace prez lays out his plan of action

Download This Episode

Subscribe in iTunes

The Structure Show RSS Feed

More cloud news from around the web

Microsoft said to cut Windows price 70 percent to counter rivals

Assessing Windows Azure at its four-year mark

Rackspace seals new UK data center in frosty air-cooled TOMB

Cloud Cruiser for Rackspace private cloud goes live

4 Responses to “Examining the latest OpenStack spat”

  1. Eduardo Mendez

    OpenStack looks like too many many people sleeping on the same bed and pulling the blanket. It looks like all of them will end with cold feet…

  2. Aryeh Friedman

    Being on the sidelines and watching it is sure is fun ;-)… sounds like an other case of OpenStack is to complex for it’s own good (until it effects the user’s and developer’s then it is no fun)

    On the whole issues of drivers this is not even OpenStacks problem per se (see details). Namely they should be left to the virtualization and cloud foundation layers. All that OpenStack should be presented is a single unified abstraction it can pull from. Once this is done it can focus on what does best is building (public and private) application/end-user clouds.

  3. This is Rob Hirschfeld. OpenStack board member and co-chair of the DefCore committee. Mirantis’ activities in this area are being coordinated with the DefCore activity and align with the direction of the board. While DefCore focuses on selecting tests to define OpenStack core, there is a substantial need for community activity to expand coverage and run tests.

    This effort fills a gap and aligns with DefCore.