How the Board’s DefCore Committee is Crowdsoucing Core
Redefining OpenStack Core
with Community, Tests & Code
DefCore = Commercial Use
Uses of the OpenStack mark:
1. Community (non-commercial use)
2. Code (integrated release)
3. Commerce (products and services)
DefCore covers #3 only!
OpenStack™ should mean something to users
What matters to users?
● OpenStack as a reliable platform (brand)
● Common Validation (testing)
● Common Implementation (code)
● And, don’t impede grown and innovation!
DefCore = Interoperability
What is DefCore?
DefCore is a process that sets base requirements for all
OpenStack products by defining:
1) must-pass tests of capabilities, and
2) designated sections of code
These definitions use community resources and
involvement to drive interoperability by creating the
minimum standards for products labeled “OpenStack”.
Capabilities AND then Code
Validated by Tests
Integrated Projects Only
Which code gets Designated?
● code provides the project external REST API, or
● code is shared and provides common functionality for
all options, or
● code implements logic that is critical for cross-
● code interfaces to vendor-specific functions, or
● project design explicitly intended this section to be
● code extends the project external REST API in a new
or different way, or
● code is being deprecated
Overview: How do we do this?
One Committee, with
- 10 Principles
- 12 Criteria
- 75+ Capabilities
- 1 Scoring Matrix