openstack defcore review 2014
TRANSCRIPT
How the Board’s DefCore Committee is Crowdsoucing Core
Redefining OpenStack Core
with Community, Tests & Code
DefCore Co-ChairRob Hirschfeld
December 2014
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 usersWhat 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
Capabilities (API)Designated Section
Integrated Release
OpenStack Project
Integrated ReleaseCapabilitiesProject APIs
Validated by Tests
Designated SectionsIntegrated Projects Only
Required Upstream
Which code gets Designated?
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-
platform operation
Not Designated:● code interfaces to vendor-specific functions, or● project design explicitly intended this section to be
replaceable, or● 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
(per release)
DefCore Principles
Platform & Component Levels
In Oct 2014, The Board and Foundation added the concept of “levels” to core.
Vendors can to comply with DefCore but use a subset of the whole project.
Core = Tests+Designated Code
12 Criteria
Capabilities
Capabilities = Groups of API Tests, e.g.:"block-snapshots" :test_snapshot_create_get_list_update_delete,test_volume_from_snapshot
Capabilities Scoring Matrix
Capabilities << TestsScore max 100Non-Admin APIScored per Release Preliminary Havana Enforced for Juno
Community Feedback
DefCore Depends on Usage Data!
1. Users2. Tools3. Clients
Call to Action!
Next Cycle (“Scale”):1. Process Approval2. Icehouse Artifacts3. (stretch goal) Juno Artifacts
BYLAWS APPROVALNEEDS 25% QUORUM!Read> bit.ly/osbylaws2014
References
RefStack Wiki: https://wiki.openstack.org/wiki/RefStack
DefCore Wiki: https://wiki.openstack.org/wiki/Governance/DefCoreCommittee
Rob’s Blog: http://robhirschfeld.com/tag/defcore/
RefStack: https://github.com/stackforge/refstack
Please reach out to me, @zehicle, or OpenStack DefCore mailing list!