This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.
Interop Working Group 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."
Our mission is to define "OpenStack Core" as chartered by the by-laws.
- Terms Definition
- 10 Core Principles (board approved Hong Kong Summit)
- Capability Levels: Component and Platform (board approved October 2014)
- 12 Scoring Criteria (board approved Atlanta Summit)
- 10 Designed Sections Principles (board approved December 2014)
- Interop Working Group Governance:
- Interop Working Group Process
- Capabilities & Sections
Objective / Scope
The Interop Working Group is around how the OpenStack brand is applied for commercial uses. Initially, this focus is on "what is core" and sustaining that definition over time. The scope will likely expand since brand is an ongoing concern related to specialized marks and other use cases.
There are three ways in which the community uses the OpenStack brand including referring to projects.
- General community use of the mark
- Project-specific use associated with development activity
- Governed commercial use
While the top two of these uses are out of scope for Interop Working Group, the committee has a need to participate in the discussion to ensure consistent and clear use.
How to Engage?
- Join the Interop Working Group list
- Join #openstack-interop on Freenode IRC
- Follow the code at https://github.com/openstack/defcore
- Join our weekly meetings
- Learn the rules for submitting changes
Meeting times and channels can be found on the official OpenStack IRC meeting list. An ICS file of all OpenStack meetings is also available. Logs of past meetings can be found here. Old meetings DefCore.
Defining OpenStack Core is a long term process and we are doing the work in progressive cycles. For reference, we have named the cycles. This helps describe concrete deliverables for a cycle while allowing discussion of the broader long term issues. For example, we may say that "item X is important to Interop Working Group but out of scope for Elephant." We have found that this approach to breaking down the problem is necessary to maintain community consensus because we are taking smaller bites of the larger challenge (aka eating the elephant).
See Process Cycles
The current cycle is named the Scale Cycle.
Current Committee Leaders
You can also find information about who is contributing to Interop Working Group here.