The OpenStack Blog

Category: Uncategorized

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 [email protected]

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 [email protected]  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.


Welcome new Gold Members Aptira, Hitachi, and Huawei!

The OpenStack Board of Directors approved Aptira, Hitachi and Huawei as Gold Members of the OpenStack Foundation. The companies are based in Australia/India, Japan and China respectively, and range from a startup to established, multinational corporations.

The timing couldn’t be better in my view, given that we are having our first ever Summit in Asia this week with attendees from 50 countries, including many from Australia, Japan, India, and China. As OpenStack adoption continues to accelerate around the globe, I am excited to welcome these new companies to the Gold Member ranks.

Some Background on the new members:

Aptira is a services business that focuses primarily on consulting, integration and training for OpenStack. Aptira has been instrumental in building the OpenStack community in Australia and India by organizing user groups, promotional activities and offering training courses. The company open sourced much of its training material and is collaborating across the community on broader education efforts.

Hitachi’s JP1 systems management solution supports OpenStack, and they’ve contributed support for their Hitachi Unified Storage platform for OpenStack Block Storage. The company also sponsors community building efforts in Japan, including an OpenStack event happening in Tokyo, February 2014.

Huawei is a top 20 OpenStack contributor that has contributed a Block Storage driver to support Huawei storage solutions, as well as made broader contributions to OpenStack documentation and testing systems. Huawei has supported community building efforts in China, including organizing meet ups and conferences, publishing whitepapers and blogs, and sponsoring and promoting the Summit this week.

Now let’s give each of the contributors from these companies a proper stacker welcome in Hong Kong this week!



OpenStack Launches Training Marketplace

Screen Shot 2013-09-16 at 10.37.09 AM

Today the OpenStack Foundation has launched a new Training Marketplace, making it easier to discover and participate in training courses offered by technology providers in the OpenStack ecosystem. Aptira, hastexo, The Linux Foundation, Mirantis, Morphlabs, Piston, Rackspace, Red Hat, SUSE and SwiftStack are the first companies to have courses available in the Marketplace, with the goal of growing the OpenStack talent pool and accelerating the availability of OpenStack training courses worldwide.

To find an OpenStack training course from the ecosystem of providers, visit
OpenStack expertise continues to pay off, with OpenStack jobs consistently paying higher wages and employers doubling the number of job postings over the past year.  The ecosystem has quickly responded to help developers and operators gain these valuable skills, with dozens of courses across 10 countries and 25 cities included in the Marketplace at launch. Future demand for OpenStack skills is only expected to grow, with the BSA Global Cloud Scorecard predicting that 14 million cloud jobs will be created by 2015.

OpenStack Jobs Pay

OpenStack Jobs Pay

“The goal of the Foundation is to eliminate barriers to OpenStack adoption, create more OpenStack experts and ensure that OpenStack has a positive impact on the careers of our community members,” said Jonathan Bryce, executive director of the OpenStack Foundation. “We want to grow the community, accelerate the availability of training programs worldwide and help close the OpenStack job gap.”

In order to offer courses in the Training Marketplace, companies must meet requirements set by the Foundation, with the primary purpose of the course being to contribute to, operate or build applications for an OpenStack cloud. The training curriculum should provide a strong understanding of the OpenStack core projects based on a current version of the software, as well as cover community governance and contribution processes.

In addition to paid and free training courses by companies in the OpenStack ecosystem, there are many community efforts to produce helpful documentation, how-to information and new Operations and Security guide books. There are also many educational sessions and hands-on workshops scheduled for the next OpenStack Summit, November 5-8, in Hong Kong. Workshops from previous Summits are available to view online.

Does your company offer training for OpenStack?  Contact us with details: [email protected]

Participate in the OpenStack User Survey by September 30!

We’re kicking off the second round of the OpenStack User Survey this month! You may remember before the April Summit we helped the User Committee run a survey to aggregate OpenStack deployments and share the results.

The first User Survey 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 Summit. Another huge benefit was the ability to uncover new users willing to talk about their OpenStack deployments, which can be found at

If you are an OpenStack user or have customers with OpenStack deployments, please take a few minutes to respond to our User Survey or 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 September 30, 2013 at 23:00 UTC. If you already completed the survey earlier in 2013, 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.

Take the Survey:

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.

Remember you can hear directly from users and see the aggregate survey findings by attending the next OpenStack Summit, November 5-8, in Hong Kong.

Thank you for your support!

Open Mic Spotlight: Flavio Percoco

Screen Shot 2013-09-12 at 8.40.46 AMThis 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. 

Flavio spends most of his time hacking on storage (Glance [core member], Cinder, Swift) and messaging (Marconi [core member]) modules. He has both Italian and Venezuelan roots, and is currently based in Italy where he works remotely for Red Hat. Flavio is also an actively open-source contributor and part of Mongodb Masters group.

Prior to Red Hat, Flavio worked on Big Data oriented applications, search engines and message systems. He was also an active member of Gnome’s a11y team where he contributed to Orca and created MouseTrap, a head-tracker application. Outside Red Hat, he likes to take pictures, swim, travel, hang around with family and friends and whatever seems interesting. You can follow him on Twitter at @flaper87.

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

Coffee and Gummy Bears. Here’s proof:

2. What behavior has helped you get the furthest as a developer? 

“Be humble about the things you know and fearless about the things you don’t know… And keep going.” I always remind myself this.

Computer Science is one of those careers where people never stop learning. It keeps evolving every second, there are always new things to learn, share or do.

I consider myself a very passioned developer and I’m always looking for new things to learn and share. Whenever I get the chance, I dig deeper on the things I like the most and I’m always looking forward to share everything I know with other people.

This way of thinking has taught me that knowledge is worthless if you don’t know how share it.

3. Why did you get into computer engineering?

I’m not one of those who started playing with computers since he was 3 years old. I spent my childhood playing outside my house rather than inside it. I started playing with computers – and I mean programming - when I was almost out of high school – or was I out already? mmh – and I completely fell in love with it. My first distro was RHEL and after it I jumped through a whole bunch of different distros.

My other options besides computer engineering were: Physics, Medicine or Psychology but I’m programmatically lazy so, here I am. I still want to study Physics, though.

4. What are your tips or tricks for surviving jet lag or long conferences?

Trust your clock, it’s always right (unless you forget to change it to the local time).

Don’t think about how tired or hungry you are because you’re not. If your clock says 12:00 then it is time for lunch, if it says 20:00 it’s time to have dinner and if it says 2:00 then you can be tired and go to bed.

I call that: “Biology by approximation”

5. Not counting the obvious (your colleagues or close former colleagues), who have you worked with closely, built a relationship with or learned the most from in the community? Why? 

Without any specific order:

Doug Hellman: No matter how or with regard to what, I always learn something new from him. Email threads, reviews or code, it doesn’t matter, he’s always teaching me something.

Devananda van der Veen: When we met at the last Europython, we not just talked about technology but also about Philosophy and Buddhism. I really enjoyed our conversations and learned at lot from them.

The whole Marconi team: Those guys rock. We’ve been working very closely since the project started. We’ve made calls, meetings and hung around on IRC. All this time, we’ve shared and learned from each other. Also, I’d dare to say that Marconi’s irc channel is the funniest throughout OpenStack.


Addressing the topic of ‘Core’ through Spider

The word “core” carries with it a wide range of meaning and implication for those involved within the OpenStack community. What we’ve discovered through ongoing discussions is that the goals of one audience simply aren’t necessarily the goals of the other audiences – in fact, in some cases, they’re opposed!

We first began the journey to refine the definition of core through a work effort called IncUp.  IncUp was a combined effort of TC and board members that resulted with improvements to the Incubation process. That effort also helped draw out the complex nature of defining core.  The complexity is due to the varied impact core has upon OpenStack users and contributors, as well as the ecosystem as a whole.

Addressing The Problem
On assignment from the Board, Rob Hirschfeld and I began meeting to further the progress of defining core. The first step in this process was to examine and define the goals of each audience, which Rob detailed in a series of blogs[1] outlining the thought processes we went through.

Shortly after we began this process, we quickly realized that the goals amongst these various audiences would either be aligned or in tension. Using different colors to map the goals and tensions on a whiteboard, we created a massive multi-colored “spider” graph, which became more of a mind map. Thus, we refer to the current effort as the “spider discussions” or simply spider.

Problem Statement/Goal
At the highest level, this spider effort is about advancing the OpenStack mission of producing the ubiquitous Open Source cloud computing platform. The key efforts within this process include defining the set of components, processes and criteria needed to protect the brand, provide users a good experience, and reinforce a collaborative community.OpenStack marks are the tools that the Foundation has to define and defend those keys.
In order for OpenStack implementers to use the OpenStack mark, the Board was chartered to provide specific and verifiable criteria. However, these do not currently exist in a usable form.  Thus, our “what is core” discussions and efforts seek to determine those criteria.
Statements of Position
Spider focuses on breaking down those criteria of core into referenceable position statements.  Those statements will form a basis to draw upon so that we may keep the decision making – and eventual implementation – on a progressive track.There are currently 10 evolving position statements:1.     Implementations that are core can utilize the OpenStack trademark (OpenStack™)
1.     This is the legal definition of core, as well as why it matters to  the community.

  1.  We want to make sure that the OpenStack™ mark means something.
  2. The OpenStack™ mark is not the same as the OpenStack brand; rather, the Board uses its control of the mark as a proxy to help manage the brand.

2.     Core is a subset of the whole project

  1. The OpenStack project is intended to be a broad and diverse community with new projects entering incubation, with new implementations frequently added. This innovation is vital to OpenStack but separate from the definition of core.
  2. There may be other marks that are managed separately by the foundation and available for the platform ecosystem at the Board’s discretion.
  3. The “OpenStack API Compatible” mark is not part of this discussion and should be not be assumed.
3.     Core definition can be applied equally to all usage models

  1.  There should not be multiple definitions of OpenStack, regardless of the operator (public, private, community, etc.).
  2. While expected that each deployment is identical, the differences must be quantifiable.

4.     Claiming OpenStack requires use of designated code frameworks

  1. Implementations claiming the OpenStack™ mark must use the approved API framework code.\
  2. Entities which only pass all the tests but do not use the API framework will not be considered or be approved as part of OpenStack.This prevents entities from using the API without joining the community, as well as surfaces bit-rot in alternate implementations to the larger community.
  3. By implementing this requirement,  interoperability is greatly improved, as there is more shared code between implementation

5.     Projects must have an open reference implementation

  1. OpenStack will require an open source reference base plug-in implementation for all projects (if not part of OpenStack, license model for reference plug-in must be compatible).
  2. We define a plug-in as alternate backend implementations with a common API framework that use common _code_ to implement the API.
  3. This establishes the expectation that projects (where technically feasible) will implement plug-in or extension architecture.
  4. This is already in place for several projects and addresses ecosystem support, further enabling innovation.
  5. Reference plug-ins are, by definition, the complete capability set. It is not acceptable to have core features that are not functional in the reference plug-in.
  6. This will enable alternate implementations to offer innovative or differentiated features without forcing changes to the reference plug-in implementation.
  7. This will also enable the reference to expand without forcing other alternate implementations to match all features and recertify.

6.     Vendors may substitute alternate implementations

  1. If a vendor plug-in passes all relevant tests then it can be considered a full substitute for the reference plug-in.
  2. If a vendor plug-in does not pass all relevant tests then the vendor is required to include the open source reference in the implementation.
  3. Alternate implementations may pass any tests that make sense and should add tests to validate new functionality.
  4. They are also required to have all the must-pass tests (see #10) to claim the OpenStack mark.

7.     OpenStack implementations are verified by open community tests

  1. OpenStack implementations by vendors must achieve 100% of must-have coverage.
  2. Implemented tests can be flagged as must-have required list.
  3. Certifiers will be required to disclose their testing gaps.
  4. This will put a lot of pressure on the Tempest project.
  5. Maintenance of the testing suite will become a core Foundation responsibility, which may require additional resources.
  6. Implementations and products are allowed to have variation based on publication of compatibility.
  7. Consumers must have a way to determine how the system is different from reference (posted, discovered, etc.).
  8. Testing must respond in an appropriate way in BOTH pass and fail (the wrong return rejects the entire suite).

8.     Tests can be remotely or self-administered

  1. Plug-in certification is driven by Tempest self-certification model.
  2. Self-certifiers are required to publish their results.
  3. Self-certifier are also required to publish enough information that a third party could build the reference implementation to pass the tests.
  4. Self-certifiers must include the operating systems that have been certified.
  5. It is preferred for self-certified implementations to refer back to an OpenStack reference architecture “flavor” instead of defining their own reference (a way to publish and agree on flavors is needed).
  6. The Foundation needs to define a mechanism of dispute resolution (i.e. a trust but verify model).
  7. All ecosystem partners need to make a “works against OpenStack” statement that is supportable.
  8. An API consumer can claim working against the OpenStack API if it works against any implementation passing all the “must have” tests.
  9. API consumers can state they are working against the OpenStack API with some “may have” items as requirements.
  10. API consumers are expected to write tests that validate their required behaviors (submitted as “may have” tests)

9.     A subset of tests are chosen by the Foundation as “must-pass”

  1. An OpenStack body will recommend which tests are elevated from “may-have” to “must-have.”
  2. The selection of “must-pass” tests should be based on quantifiable information when possible.
  3. Must-pass tests should be selected from the existing body of may-pass tests.  This encourages people to write tests for cases they want supported.
  4. We will have a process by which tests are elevated from “may” to “must” lists.
  5. Essentially, the hope is that the User Committee will nominate tests that elevate to the Board.

10.  OpenStack core means passing all “must-pass” tests

  1. The OpenStack Board owns the responsibility to define core (to approve ‘musts’).
  2. We are NOT defining which items are on the list in the Spider effort; rather, just making the position that this is how we will define core.
  3. May-have tests include items in the integrated release, but which are not core.
  4. Must-haves must comply with the core criteria defined from the IncUp committee results.
  5. Projects in Incubation or pre-Incubation are not to be included in the “may” list.

For a quick visual way to understand how these position statements interconnect Rob posted, in his blog series, an ‘OpenStack Core flowchart’. [2]

Help Us Finalize the 10

These position statements are an ongoing work in process. It is our goal to finalize them for the November Board meeting and Hong Kong Summit. Yet in order to meet that goal, we want your help and, as such, would love to hear from you. I encourage you all to strike up a conversation on IRC with Rob, myself or any board member, or simply post your feedback to the Foundation mailing list. We’re looking to you to help us reach the goal of the Foundation’s mission!

Alan Clark
OpenStack Board Chair


Back to top