If you’ve been following my DefCore posts, then you already know that DefCore is an OpenStack Foundation Board managed process “that sets base requirements by defining 1) capabilities, 2) code and 3) must-pass tests for all OpenStack™ products. This definition uses community resources and involvement to drive interoperability by creating the minimum standards for products labeled OpenStack™.”
In this post, I’m going to be very specific about what we think “community resources and involvement” entails.
The draft process flow chart was provided to the Board at our OSCON meeting without additional review. It below boils down to a few key points:
- We are using the documents in the Gerrit review process to ensure that we work within the community processes.
- Going forward, we want to rely on the technical leadership to create, cluster and describe capabilities. DefCore bootstrapped this process for Havana. Further, Capabilities are defined by tests in Tempest so test coverage gaps (like Keystone v2) translate into Core gaps.
- We are investing in data driven and community involved feedback (via Refstack) to engage the largest possible base for core decisions.
- There is a “safety valve” for vendors to deal with test scenarios that are difficult to recreate in the field.
- The Board is responsible for approving the final artifacts based on the recommendations. By having a transparent process, community input is expected in advance of that approval.
- The process is time sensitive. There’s a need for the Board to produce Core definition in a timely way after each release and then feed that into the next one. Ideally, the definitions will be approved at the Board meeting immediately following the release.
Process shows how the key components: designated sections and capabilities start from the previous release’s version and the DefCore committee manages the update process. Community input is a vital part of the cycle. This is especially true for identifying actual use of the capabilities through the Refstack data collection site.
- Blue is for Board activities
- Yellow is or user/vendor community activities
- Green is for technical community activities
- White is for process artifacts
This process is very much in draft form and any input or discussion is welcome! I expect DefCore to take up formal review of the process in October.