The OpenStack Blog

Category: Uncategorized

Participate in the OpenStack User Survey by April 11!

We’re kicking off the third round of the OpenStack User Survey this month! You may remember before last November’s Summit in Hong Kong, we helped the User Committee run a survey to aggregate OpenStack deployments and share the results.

Hong Kong Survey Results

The survey received nearly twice as many answers as the previous round (822 compared to 414) and 387 deployments compared to 187.

The first User Survey in Spring 2013 provided great insight to the types of deployments and technology decisions made by the OpenStack community. We were able to catalogue 230 unique deployments – you can see the results presented by the User Committee at the last Spring Summit. Another huge benefit was the ability to uncover new users willing to talk about their OpenStack deployments, which can be found here:

If you are an OpenStack user or have customers with OpenStack deployments, please take a few minutes to respond to our User Survey and pass it along to your network. The goals of the survey are to better define the OpenStack user community and requirements, facilitate engagement and communication among the user community, and uncover new use cases or OpenStack users who might be willing to tell their stories publicly.

Below you’ll find a link and instructions to complete the User Survey by April 11, 2014 at 23:00 UTC. If you already completed the survey last year, there’s no need to start from scratch. You simply need to log back in to update your Deployment Profile, as well as take the opportunity to provide any additional input.

All the information provided is confidential and will only be presented in aggregate unless the user consents to making it public. Aggregate responses will be shared with the OpenStack Board, Technical Committee and community at large to help shape the roadmap and share useful information regarding operational decisions.

You can also help us by promoting the survey so we can secure as much participation as possible, for example by retweeting the OpenStack handle: @OpenStack

Remember, you can hear directly from users and see the aggregate survey findings by attending the next OpenStack Summit, May 12-16, in Atlanta.

Thank you for your support!


OpenStack Summit May 2014 Schedule & Registration Deadlines


The official Summit agenda is now live:

Adjustments, edits, additions to the schedule may be made between now and the Summit.  Continue to visit the site for updates.

Upcoming deadline reminders:

March 28* is the last day to save 50% off the full price and register for the Summit at the discounted Early Bird rate. Don’t miss out – prices will increase on March 29.

Register here:

March 31* is the deadline to sign contracts to sponsor the Summit. We still have a few Event and Startup sponsorship levels available. Contact if you are interested.

April 14* is the deadline to redeem all sponsor and speaker registration codes. If you are a sponsor or a confirmed speaker – please check your email inbox or junk folder for the code. When registering on Eventbrite you will need to enter your code before you select the ticket.

* The time for each deadline listed above is 11:55pm CST.

Please contact with any Summit related questions.

OpenStack Atlanta Summit Presentation Voting

Wednesday evening we launched the online tool that allows you to rate the presentation proposals summited for the OpenStack Summit coming up May 12-16 in Atlanta.

This is our second year with online voting for summit presentations, and we wanted to let you know about a bug we’ve just corrected that you might have experienced during the first two days of voting. Alert community members discovered that in some cases, older presentations from our prior summit could be displayed once a vote was cast. (The system randomly selects the next presentation to display, and in this particular case it was not limiting the results to only the upcoming summit.) That’s now been corrected and we apologize for the bug that caused it.

Ultimately, the chairs for each track make the final presentation selections, using the ratings gathered from the community as input. To allow a bit more time for you to cast your votes, we’ve extended the voting deadline until midnight central, March 3rd.

If you are a presenter or voter with any questions or feedback, please let us know:

New Foundation Gold Members & Sponsors

The OpenStack Foundation is thrilled to have new additions to our ecosystem. Three new Gold Members and 18 Corporate Sponsors have recently joined the incredible list of companies who are supporting the Foundation and driving innovation on the platform.  AptiraHuawei and Hitachi won the OpenStack Board’s approval at the November board meeting and joined the Foundation as Gold members, which requires a strong, strategic commitment to the technology and community.

We’ve also seen amazing support in Corporate Sponsorship and we want to share the impressive list of recent additions.

The diversity in technologies and geographic location of these new additions to the ecosystem reflects the growth of OpenStack and its footprint worldwide.  We are looking forward to enjoying each these companies’ unique contributions going forward!

OpenStack Commitment to Interoperability

OpenStack began with the mission to produce a ubiquitous open source cloud computing platform. A key component of that mission is building not only software, but a large OpenStack ecosystem that would support its growth and add value to the core technology platform. In carrying out that mission, the Foundation has been taking key steps to define the core technology platform and advance OpenStack interoperability.

The TL;DR summary:  Now that we have tons of users, we need to make sure all (downstream) products labeled “OpenStack” have a certain set of core capabilities, and we need to verify those with automated tests just like we do upstream.  End-users should be our focus, and ensuring they get what they want and expect out of the platform once it’s running as a service is paramount.  The goal is to define the first set of tests in time for the May 2014 Summit in Atlanta. If this matters to you, get involved!

Read on to learn more about the rationale, history, future plans, and how you can get involved.

Why does interoperability matter for OpenStack?

We’ve heard from many users and operators that interoperability between OpenStack clouds and hybrid cloud scenarios are an important part of the value they are seeking. OpenStack is most useful when it provides a common platform to consistently deploy workloads between clouds without making resource intensive changes to operations tools and processes. Value is unlocked when development tools and applications have a common target across public and private OpenStack clouds.

The full potential of OpenStack will not be realized if users don’t know what they’re going to get from public cloud services or off-the-shelf distributions and appliances. Ambiguity or mistrust about the capabilities of OpenStack isn’t good for the business ecosystem or end users. It’s important that public clouds and private cloud products branded with OpenStack have a clear meaning in the market.

What is the Foundation doing?

One of the most important responsibilities we have as a Foundation is to ensure the long-term value of the OpenStack brand in the market. This has been an ongoing priority since our founding and has involved the collective effort of a great number of community members.

When we began, we implemented an OpenStack trademark policy, which allows broad use of the OpenStack logo and name for non-commercial community building efforts like user group meetups, while also creating special guidelines, technical requirements, and licenses for use by commercial products. As the community, the software, and the ecosystem have grown, so too has the need to refine these technical requirements for commercial products, by defining a core set of capabilities included in all products and services marketed as “OpenStack.”

It is indeed a large task, one that stems from the diversity of our community, the breadth of our ecosystem, and the broad application of our software. But it is one that will ensure the longevity, vitality and utility of OpenStack far into the future.

Therefore, in order to agree on a set of well-defined criteria for the core we must take special care to have a transparent and objective process. The Board of Directors and the Technical Committee have initiated a number of programs to tackle the issue.

IncUp (Early 2013)

The first step was forming the Incubation/Future of the Core (IncUp) committee, a joint effort between the OpenStack Board of Directors and Technical Committee, aimed at tackling the process for expanding the scope of OpenStack through new project incubation and promotion.

At the April 2013 board meeting, the Board of Directors approved the IncUp committee’s recommendations, including 1) The technical committee continues to manage the incubation process for new projects applying to be part of the coordinated, integrated release 2) Projects that are part of the coordinated release should be referred to as “Integrated” (but not necessarily “Core”), and 3) “Core” is a label the Board can attach to a project that is part of the regular integrated release.

The Technical Committee is following on these efforts by creating a clear set of guidelines for projects that wish to be officially incubated, as well as the attributes an incubated project should have before being approved for graduation to the integrated release. The purpose of the guidelines are to maintain a high standard of quality and cross-project integration for OpenStack.

The important outcome of the IncUp committee places the responsibility to manage the technical scope of the OpenStack project with the Technical Committee, while the Board ultimately sets the criteria for which technical capabilities should be present in (downstream) commercial products or services marketed as OpenStack. This led to the next phase in the process: considering how to define those criteria in a standard and broadly applicable manner.

Enter the “Spider” (2013)

The Board of Directors formed a new work group to tackle the task of determining how to define Core in a consistent manner that would apply to the varied set of use cases OpenStack addresses and the broad set of technology developed within the community. Early in this effort, the team, including Alan Clark and Rob Hirschfeld, drew a map on a whiteboard of dependencies and relationships that came into play when trying to define which projects were “Core OpenStack.” The drawing, which revealed some of the complexities of the task, resembled a spider mind map and inspired the nickname for the group.

Rather than jump straight into choosing specific projects that would qualify for the “Core” label, the committee focused on defining principles that would apply equally to any commonly required and deployed component of OpenStack deployments. These principles were drafted and reviewed through the summer and fall of 2013 at a series of open community meetings held online and in various locations. After several revisions, the Board of Directors approved the final principles at their November 2013 meeting.

DefCore (Ongoing)

After approving the guiding principles at the Hong Kong Summit in November 2013, the OpenStack Board of Directors created the DefCore committee, chaired by Rob Hirschfeld and Josh McKenty, to define a “core” set of capabilities which are expected to be present in all commercial products marketed as “OpenStack”, along with a set of tests to validate those capabilities.

The creation of DefCore marks a new focus on including a test-driven component to the definition of core. This route is more objective, and test-based standards better addresses our commitment to interoperability. The committee is working to determine which capabilities a commercial offering should include to make use of the OpenStack marks and is currently in the process of standardizing the tests that must be passed. The goal is to repurpose the same testing that we’ve been doing on the upstream code to apply to the products and services downstream, ensuring that they retain the fundamental building blocks of Openstack.

One of the realizations coming out of the early work of the committee was that users think in terms of “capabilities” more than “projects.”  Projects are how we organize as a development community, but in the end the capabilities delivered by an openstack-powered cloud are what really matter, and in practice many capabilities rely on multiple underlying “projects”.  This is a subtle but important distinction which is reflected in the way we think about writing tests to validate those capabilities in the downstream products licensing the OpenStack brand.

The DefCore committee is working against an aggressive timeline with a plan to the pilot must-pass tests for Havana before the OpenStack Summit in Atlanta in May. Icehouse will follow shortly thereafter, and Juno’s test will be ready to go by the Paris summit.

Being able to expose OpenStack cloud test results and provide a defined target for end users is an incredibly important effort and high priority for the Foundation this year. It is our hope that by outlining the steps we’re taking, the community will involve themselves in these efforts and track the progress of this vital endeavor. To get involved in the DefCore process, sign up for the mailing list and follow the wiki for updates.

Instant Poll:

Create your free online surveys with SurveyMonkey , the world’s leading questionnaire tool.

Atlanta Summit – Call for Speakers Open + Sponsor & Registration Info

The OpenStack Summit will be held in Atlanta, Georgia May 12-16, 2014. Continue to check for the latest announcements. If you have any questions regarding the Summit please contact

The Summit is a five-day conference for OpenStack contributors, enterprise users, service providers, application developers and ecosystem members.  Attendees can expect visionary keynote speakers, 200+ breakout sessions, hands-on workshops, collaborative design sessions and lots of networking. Keynote sessions will take place Monday and Tuesday, the main conference will run Monday – Thursday. The Design Summit, a special track for active technical contributors to plan the next software release, will run Tuesday – Friday. See below image for reference.

The call for speakers is now open

Hurry, the deadline for submissions is February 14!  All speaking proposals will be posted for public vote in late February, and speakers will be notified in March. If your session is selected you will be provided with a free code to register for the Summit.  If you plan to co-present a topic or panel, be sure to input all planned speakers into the system. Proposed speaking tracks: Operations, Getting Started, Hands-On Workshops (90 minutes), Related OSS Projects, Apps on OpenStack, Cloud Strategy & Business Value, Public & Hybrid Clouds, Ecosystem, Products & Services, Compute, Storage, Networking, Security, and Community Building.

Sponsoring the OpenStack Summit is a great way to gain exposure and support the open source community. If you are interested in supporting the Summit and would like to have a presence in our expo hall – the executable Atlanta Summit sponsorship agreement will become available on January 21 at 17:00 UTC at this link -  If your company did not previously sponsor either the Portland or Hong Kong OpenStack Summits then you will first need to sign the Master Event Sponsorship Agreement.  Please fully read the Sponsorship Prospectus and process to become a sponsor before signing the sponsorship agreement. All sponsorship levels are limited and sold on a first-come, first-serve basis determined by the timestamp on your signed Echosign agreement. After signing the agreement please check your email to confirm submission via Echosign – the contract is not complete until you confirm by clicking the link emailed to you via Echosign.

*New* Headline sponsorship process - Headline contracts will be confirmed on a first-come, first-serve basis if there are 4 or less contracts submitted within the first hour of the executable agreement becoming available. In order to create a fair and level playing field, if more than four (4) companies submit signed contracts within the first hour (between 17:00 – 18:00 UTC) for a Headline sponrship level, the Foundation staff will conduct a lottery to draw the four (4) Headline sponsors. A link to watch a livestream of the lottery drawing will be posted on at approximately 18:00 UTC.  The remaining companies that do not secure the Headline sponsorship lottery will be given the opportunity to re-sign contracts and obtain Premier level sponsorship slots in the order they submitted Headline agreements. The lottery is only applicable to the Headline sponsorship level.  If you have any questions please contact  We appreciate your support!

Note – If your company has any past due balances owed to OpenStack Foundation, these invoices will need to be be paid in full in order to be eligible to sponsor the Summit.

Early Bird Registration will open on January 28 and run through March 21. Act quickly to register, as prices will increase starting March 22, 2014. The link to registration will be posted at

We will again offer TWO types of passes. In addition to the “Full Access” pass, there will be a “Keynote + Expo” level pass to help introduce even more people to OpenStack. Restrictions apply to the lower priced pass, so please review the details before selecting a ticket.

Screen Shot 2014-01-14 at 10.49.50 AM

Screen Shot 2013-12-18 at 11.56.34 AM

Atlanta Summit Schedule


It’s Summer Internship Time in the Southern Hemisphere!

After a brisk walk in Austin Texas in mid-30 degree Fahrenheit weather, I welcome the idea that it’s summertime somewhere. Since it’s summertime in the southern hemisphere, we can now announce our next round of Outreach Program for Women internships!

I’m excited that we have four interns and four mentors this time around. Many thanks to HP, the OpenStack Foundation, and Rackspace for funding our four. HP also stepped in this round and made it possible for more of the nine participating organizations to select interns, including OpenStack. Plus, RedHat developers are mentoring our interns. I asked each intern, what do you see when you look above your screen?

Annapoornima Koppad is known as akoppad on IRC. She lives in Bangalore, Karnataka, India. She’ll be working on surfacing the instance actions in the OpenStack dashboard through the Horizon project with our second-time mentor, Julie Pichon. Anna says, “It’s a wintry December in Bangalore, India. There is a gloomy, cold, and yet pleasant atmosphere. There is a small window in front of me, and I think it’s most likely to rain after sometime. I see my neighbours are scurrying up to renovate their house. I sip up my warm tea, and I have some books on my right shelf.”

Sayali Lunkad will be working on adding sparklines to the Dashboard, mentored by Ladislav Smola. Sayali goes by sayalilunkad on IRC and is located in Pune, Maharashtra, India. Sayali says, “I read this mail just as I woke up. I am in my room from where I see the sun up in the sky and parrots and crows in my terrace garden which is connected to my room. It is a pleasant morning, hope everyone has a good day!”

In Dallas Texas we find Cindy Pallares-Quezada (cpallares on IRC) She’ll be working on the Queues API Spec for the Marconi project with Flavio Percoco. Cindy says, “As for what’s above my screen, I see my window. Outside my window there’s lots of leafless branches that belong to a big tree (I’m on the second floor of a two story building). The branches are all covered in melting ice. Past the trees there’s a street and a lawn that’s full of lots of fallen trees and is covered in yellow, orange, and green leaves.”

Miranda Zhang (MirandaZhang on IRC) is in Canberra, Australia and will work with Diane Fleming to enhance the API Complete Reference pages and create a comprehensive OpenStack API Guide. She was kind enough to send pictures of her workstation. Miranda says, “Unfortunately, I’m in a room with no window (otherwise I may be able to tell you about the cuddly rabbits running around the campus, it’s hot sunny summer in Australia now), and above the computer screen I’m looking at, there are just walls, so I look around my workstation, they say a picture is worth a thousand words:”

While the interns are super important, I have to emphasize how much we should appreciate the mentoring and project identification work that goes into this program. Our mentors are extremely valuable to OpenStack as are the ideas for 3-month projects. Thanks to everyone who worked together to get these ideas ready and thanks in advance to the mentors and interns who make this project so worthwhile.

Open Mic Spotlight: Sean Chen

sean_openmicThis post is part of the OpenStack Open Mic series to spotlight the people who have helped make OpenStack successful. Each week, a new contributor will step up to the mic and answer five questions about OpenStack, cloud, careers and what they do for fun. 

Sean worked at VMware, where his last project was hybrid cloud service. He is currently working on a converged storage project at a small startup. He lives near Stanford, California. You can follow him on Twitter @opencomp

1. Where is your happy place? Favorite place to visit, vacation, decompress?

I visited Banff National Park with my kids and family this past summer. Emerald Lake, Lake Louise and Moraine Lake were breathtakingly beautiful.

2. What is your go-to beverage or snack while coding?

Chocolate, intense dark. Mochi green tea ice cream. Pearl (Boba) milk tea.

3.  Have you organized an OpenStack meet-up/event or spoken about OpenStack at an event? What did you learn? What was the best part?

I talked about how to manage VMware ESX and Virtual Center with OpenStack at the 2012 Summit. The best part was that it made OpenStackers aware of VMware’s plans with OpenStack and the software defined data center, as well as VMware’s efforts around expanding Nicira’s contributions to Quantum and Open vSwitch.

4. Why did you decide to go into computer engineering?

Apple IIe, which made me immensely happy, and got me interested in computing.

5. How did you first get involved in OpenStack?

I was doing research on open source cloud initiatives and decided to improve VMware Compute Driver in OpenStack and bring many key features to the community.

OpenStack User Survey Statistics November 2013

Prepared by Tim Bell, Ryan Lane and JC Martin, your User Committee. See also: Infographic.


In preparation for the OpenStack summit in Hong Kong in November 2013, members of the OpenStack foundation were asked to provide their feedback via a user survey. The goals were

  • Profile the user community across geographies and industries
  • Understand the current deployments of OpenStack
  • Receive input on priorities for the technical and management boards

The format was

  • Information about the person concerned
  • Feedback on priorities and improvements
  • For those with OpenStack deployments, questions on deployment sizes, technologies used in multiple choice format


The survey is open for any one to input their ideas and deployments at but a specific campaign was run during September/October to get the latest details.

The previous survey was performed in April 2013 and presented at the summit (see

As with all surveys, there are risks of errors in that those who report to an anonymous survey do not necessarily reflect the installed user base. For an open source project, this is especially difficult as there is no tracking of deployments.

This report covers the statistics gathered from the survey based on the presentation prepared by J.C. Martin from the user committee with input from Ryan Lane, Tim Bell and Tom Fifield. Further analysis is ongoing for the comments and feedback which will be published later.

Changes since the last survey

The September survey added several new questions and modified some of the originals, with the aim of clarifying some of the responses from the previous survey and gaining deeper insights into the community’s methodologies for OpenStack deployment. To gather the best possible data after the changes, a communications campaign was enacted to encourage previous contributors to update their responses.

A summary of changes is as follows:

  • Industry list updated based on “Other” responses from previous survey
  • Information sources – removed forums, added ask, planet, ‘other’
  • Added “Community Cloud” to cloud types to be in line with NIST definition
  • Replaced references to Quantum, and added Orchestration and Metering projects
  • Attempted to clarify “User Group” participation, based on poor previous responses
  • Better recognition of Continuous Deployments
  • Fixed lists of Hypervisors, Block Storage and Network drivers based on current support
  • Changed “Number of Users” question from free-form to a pick-list
  • Changed “Workloads” question to a select list, based on collating options from previous free-text response
  • Added a new question “What do you like most about OpenStack?”
  • Added a new question “If you are using nova-network and not OpenStack Networking (Neutron), what would allow you to migrate?”
  • Added a new question “What is the main Operating System you are using to run your OpenStack cloud?”
  • Added a new question “What tools are you using to deploy/configure your cluster?”
  • Added a new question “What are your business drivers for using OpenStack? ”


User Profiles

822 people from 539 different companies responded to the survey, 216 of these were already members of OpenStack user groups which is an encouraging sign of involvement in the community.

Geographically, the community is widely spread with the US responses now being the minority. Given have that this summit is based for the first time outside of America, it demonstrates the global reach of the OpenStack community and the importance to continue with a global approach.

The survey received nearly twice as many answers as the previous round (822 compared to 414) and 387 deployments compared to 187. The national distributions have adjusted a little with the US response share dropping to 38% from 42% with corresponding increases elsewhere.

The industries are clearly dominated by IT companies along with Academic and Telecoms with 80% of deployments. Government, Film/Media and Manufacturing are more limited but there is a trend towards diversification as the previous survey had 85% of deployments in IT/Academic/Telecoms.

Organisation sizes are similar to the previous survey with well spread mixture of small companies to large.

Business drivers were similar across deployments with the emphasis on agility. Nearly half the organisations felt that implementing OpenStack was an effective way to attract talent.

For information sources about OpenStack, there is now a rise in the formal documentation usage such as and the operations guide. This reflects well on the efforts that have been placed in this area as it was one of the items highlighted in the previous survey as an area to improve. was also started recently and is now rising up the information sources reflecting the benefits of developing standard Q&A high quality answers.

With Grizzly coming out, there has been a clear migration from Folsom and Essex to Grizzly. Installations on Havana have now started and the sites on trunk have continued to follow that approach.

Private cloud deployments are the majority as in the past survey.

For features, with ceilometer and heat becoming standard components and maturing rapidly, their adoption is accelerating. Bare metal and database-as-a-service deployments are starting to appear.

Over 165 deployments are now in production. This is around double the number in the previous survey (84). Equally, the Dev/QA and Proof of Concept deployments have doubled in the past six months.

Most features follow similar ratios to the previous survey (but deployments are around twice). OCCI was asked for the first time but the usage currently is not widespread compared to EC2 which is enabled over 30% of the OpenStack installations.

For the implementation choices, OpenStack provides many alternatives.

In the storage area, LVM is the largest single deployment technology which probably reflects on the ease of installation. Ceph, however, is available in nearly 20% of deployments. The huge list of storage options illustrates the different configuration choices that sites are making while deploying cinder, especially if there is a deployment for other purposes at the site. Since multiple options could be selected, this could also indicate that sites are trying several different backend storage solutions.

For deployment tools, Puppet comes out on top. However, it is encouraging to see that all but one site considered a deployment tool to simplify the installation and configuration of OpenStack.

Within the different deployments, there is a variety of scale. Many of the proof of concept instances have a small number of virtual machine instances but there are now over 30 clouds with over 1,000 instances, 15 with over 5,000 cores and 11 with more than 1,000 hypervisors. Storage, networking and objects follow similar curves with the smaller instances providing many small configurations and several at large scale.

OpenStack is used for both public and private cloud deployments. The number of responses on these points is significantly less than the total deployments, illustrating that these questions may also be considered sensitive by the deployers.

The following statistics were all gathered by dropping the proof-of-concept reports and focus on the production and dev/qa instances.

The deployment tool space has a number of common solutions. devstack is used on many of the smaller instances, presumably as part of the deployment of test clusters. However, as the number of nodes increases, tools such as Puppet and Chef takeover.

KVM continues to be the most popular hypervisor for production deployments but the variety continues to expand, even including container technologies such as lxc and OpenVZ.

Ubuntu remains the most popular O/S for OpenStack deployments, especially for the smaller configurations.

For network drivers, there are a variety of drivers with the open source vSwitch leading the pack.


Additional References

OpenStack User Survey: October 2013

The OpenStack User Committee and Foundation staff conducted a survey of OpenStack cloud operators and end users, and are sharing the results with the community this week during the OpenStack Summit Hong Kong. The goal of the survey is to give users a strong voice in the community to share their technical requirements, feedback and best practices with the developers building OpenStack, as well as other cloud operators.

The survey generated 822 responses and catalogued 387 OpenStack cloud deployments across 56 countries.  A few key highlights:
  • More than half of the clouds were already running Grizzly or Havana 
  • The top five countries with deployments were U.S., India, China, France, and Canada
  • The top 3 business drivers were Cost Savings, Operational Efficiency, Open Platform
You can find more detail in the full report by the User Committee.


Back to top