OpenStack DefCore Committee is looking for community feedback about the proposed DefCore Process.
March has been a month for OpenStack DefCore milestones. At the March Board meeting, we approved the first official DefCore Guideline (called DefCore 2015.03) and we are poised to commit the first DefCore Process draft.
Once this initial commit is approved by the DefCore Committee (expected at DefCore Scale.8 Meeting 3/25 @ 9 PT), we’ll be ready for broader input by the community using the standard OpenStack Gerrit review process. If you are not comfortable with Gerrit, we’ll take your input anyway that you want to give it except via telepathy (we’ve already got a lot on our minds).
Note: We’re also looking for input on the 2015.next Guideline targeted for 2015.04,
The DefCore Process documents the rules (who, what, when and where) that will govern how we create the DefCore Guidelines. By design, it has to be detailed and specific without adding complexity and confusion. The why of DefCore is all that work we did on principles that shape the process.
This process reflects nearly a year of gestation starting from the June 2014 DefCore face-to-face. Once of the notable recent refinements was to organize material into time phases and to be more specific about who is responsible for specific actions.
To make review easier, I’ve reposted the draft. Comments are welcome here and on the patch (and here after it lands).
DRAFT: OpenStack DefCore Process 2015A (reposted from OpenStack/DefCore)
This document describes the DefCore process required by the OpenStack bylaws and approved by the OpenStack Technical Committee and Board.
Expected Time line:
|Time Frame||Milestone||Activities||Lead By|
|-3 months||S-3||“preliminary” draft (from current)||DefCore|
|-2 months||S-2||ID new Capabilities||Community|
|-1 month||S-1||Score capabilities||DefCore|
|Advisory items selected||DefCore|
|+2 months||S+2||Test Flagging||DefCore|
|+3 months||S+3||Approve Guidance||Board|
Note: DefCore may accelerate the process to correct errors and omissions.
The DefCore Guideline process has two primary phases: Draft and Review. During the Draft phase (A), the DefCore Committee is working with community leaders to update and score the components of the guideline. During the Review phase (B), general community and vendors have an opportunity to provide input and check the guidelines (C) against actual implementations. Review phase ends with Board approval of the draft guideline (D).
This section provides specific rules and structure for each phase.
NOTE: To ensure continuity of discussion, process components defined below must _not_ reuse numbers in future revisions. The numbering pattern follows draft, section and sub-item numbering, e.g.: 20015A.B2.2. This requirement may create numbering gaps in future iterations that will help indicate changes.
Guidelines Draft Phase (A)
A1. New Guidelines Start From Previous Guidelines
- Receive DefCore Dedicated Section Guidelines
- New Guidelines start from the previous Board approved document.
- New Guidelines are given the preliminary name of the target year and .next.
A2. Community Groups Tests into Capabilities
- DefCore Committee coordinates community activities with the TC and PTLs to revise the capabilities based on current technical needs and functionality.
- Groupings may change between iterations.
- Tests must have unique identifiers that are durable across releases and grouping changes to be considered.
- Tests must be under OpenStack governance.
A3. PTLs Recommend Changes to Designated Sections
A4. DefCore Committee identifies required capabilities
- DefCore uses Board approved DefCore scoring criteria to evaluate capabilities.
- DefCore needs Board approval to change scoring criteria.
- Scoring criteria factor or weights cannot change after Draft is published.
- DefCore identifies cut-off score for determining that a capability is required.
- Capabilities will not be removed without being deprecated in the previous Guideline.
- Capabilities will not be added without being advisory in the previous Guideline.
A5. Foundation recommends OpenStack Components and OpenStack Platform Scope
- Foundation recommends capabilities to include in each OpenStack Component.
- Foundation recommends which Components are required for the OpenStack Platform.
A6. Additional Capabilities and Tests
- DefCore will work with the community to define new capabilities.
- Test grouping for new capabilities will be included in the DefCore documents.
- DefCore will publish a list of missing and gapped capabilities.
A7. DefCore Committee creates recommendation for Draft.
- DefCore Committee coordinates activities to create draft.
- DefCore Committee may choose to ignore recommendations with documented justification.
Guidelines Review Phase (B)
B1. All Reference Artifacts are reviewed via Gerrit
- Draft Guideline
- Designated sections
- Test-Capability groupings
- Flagged Test List
- Capability Scoring criteria and weights
- Not in Gerrit: Working materials (spreadsheets, etc)
B2. Presentation of Draft Guidelines
- DefCore will present Draft Guidelines to the Board for Review
- DefCore will distribute Draft Guidelines to the community
- Foundation provides Draft to vendors for review
B3. Changes to Guideline made by Gerrit Review Process
- Community discussion including vendors must go through Gerrit
- All changes to draft must go through Gerrit process
B4. For Gerrit reviews, DefCore CoChairs act as joint PTLs
- Board committee members of DefCore serve as “core” reviewers (+2).
- Requests for changes, must be submitted as patches by the requested party.
- DefCore Committee members cannot proxy for community change requests.
Community Review & Vendor Self-Test (C)
Starting: S and continues past S+3
C1. Vendor Self-Tests
- Vendors are responsible for executing these tests identified by the DefCore committee.
- The Foundation may, but is not required to, provide tooling for running tests.
- The Foundation may, but is not required to, define a required reporting format.
- Self-test results may be published by Vendors in advance of Foundation review, but must be clearly labeled as “Unofficial Results – Not Yet Accepted By The OpenStack Foundation”. Vendors who publish self-tests MUST provide them in the same format that would be submitted to the OpenStack Foundation but MAY provide additional formats if they choose to do so.
- Self-test results cannot be used as proof of compliance.
C2. Vendor submits results to Foundation for review
- The Foundation determines the acceptable format for submissions.
- The Foundation has final authority to determine if Vendor meets criteria.
- The Foundation must provide a review of the results within 30 days.
C3. Vendor Grievance Process
- Vendors may raise concerns with specific tests to the DefCore committee.
- The DefCore committee may choose to remove tests from a Guideline (known as flagging).
- The DefCore committee must respond to vendor requests to flag tests within 30 days.
- Vendors may not request flagging all tests in a capability.
C4. Results of Vendor Self-Tests will be open
- The Foundation will make the final results of approved vendors available to the community.
- The Foundation will not publish incomplete or unapproved results.
- Only “pass” results will be reported. Skipped and failed results will be omitted from the reports.
- Reports will include individual test results, not just capability scoring.
C5. API Usage Data Report
- The Foundation will provide DefCore committee with an open report about API usage based on self-tests.
- To the extent the data is available, capabilities beyond the DefCore list will be included in the report.
Guideline Approval (D)
D1. Board will review and approve DefCore Guideline from draft
- Guidelines are set at the Platform, Component and Capability level only.
- Text guideline document is authorative over the JSON representation.
- DefCore will provide JSON representation for automated scoring
- Guidelines only apply to the identified releases (a.k.a. release tags).
D2. DefCore Committee has authority on test categorization
- Can add flagged tests before and after Guideline approval.
- Cannot change Test to Capability mappings after approval.
- Maintains the test to capability mappings in the JSON representation.
D3. Designated sections only enforced for projects with required capabilities
- Designated sections may be defined for any project.
- Designated sections applies to the release (a.k.a. release tags) identified in the Guideline.
D4. Guidelines are named based on the date of Board approval
- Naming pattern will be 4 digital year dot and 2 digit month.
Pingback: OpenStack Community Weekly Newsletter (Mar 20 – 27) - GREENSTACK
Pingback: OpenStack DefCore Community Review – TWO Sessions April 21 (agenda) | Rob Hirschfeld
Pingback: OpenSource.com Interview on DefCore, project management, and the future of OpenStack | Rob Hirschfeld
Pingback: My OpenStack 2016 Analysis: Continue Core, Stop Confusing Ecosystem, Change Hybrid Approach | Rob Hirschfeld