Jump to: navigation, search

Difference between revisions of "Governance/InteropWG"

(→‎Important Artifacts)
m (→‎Current Committee Leaders)
 
(151 intermediate revisions by 19 users not shown)
Line 1: Line 1:
 
This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.
 
This Committee was formed during the OpenStack Ice House Summit in Hong Kong by Board Resolution on 11/4.
  
−
''DefCore 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."''
+
''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 labelled "OpenStack."''
  
−
Our mission is to define "OpenStack Core" as chartered by the by-laws and guided by [[Governance/CoreDefinition]]
+
Our mission is to define "OpenStack Core" that is supported by all implementations as chartered by the by-laws.
  
 
== Important Artifacts ==
 
== Important Artifacts ==
−
# Terms Definition: [[Governance/DefCoreLexicon]]
+
# [https://docs.opendev.org/openinfra/interop/latest/process/Lexicon.html Terms Definition]
−
# 10 Core Principles: [[Governance/CoreDefinition]]  (board approved Hong Kong Summit)
+
# [https://docs.opendev.org/openinfra/interop/latest/process/CoreDefinition.html 10 Core Principles]  (board approved Hong Kong Summit)
−
# 12 Scoring Criteria: [[Governance/CoreCriteria]]  (board approved Atlanta Summit)
+
# [https://opendev.org/openinfra/interop/blob/master/doc/source/process/CoreCriteria.rst 12 Scoring Criteria]  (board approved Atlanta Summit)
−
# Draft Process Flow: [[File:DefCoreProcessFlow.pdf]] (review for November approval)
+
# [https://docs.opendev.org/openinfra/interop/latest/process/DesignatedSections.html10 Designed Sections Principles]  (board approved December 2014)
−
# Capabilities
+
# [https://docs.opendev.org/openinfra/interop/latest/process/GovernanceProcess.html  Interop Working Group Governance:]
−
## Havana Advisory: [[File:DefCore_Capabilities_Scoring.pdf]]  (board approved 2014 July 22)
+
# [https://docs.opendev.org/openinfra/interop/latest/process/2021A.html Interop Working Group Process] (board approved June 2021)
−
# Proposed bylaws changes: [[File:Change-Pro_Redline_-_233015232-v15-OpenStackFoundation_Bylaws_FINAL_(as_amended_September_7,_2012)_and_233015232-v24-OpenStackFoundation_Bylaws_FINAL_.pdf]]
+
# Capabilities & Sections
 +
## Current Guidelines
 +
###  [https://opendev.org/openinfra/interop/src/branch/master/guidelines/2020.11.json Current OpenStack Powered guideline]
 +
###  [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/orchestration.2020.11.json Current Orchestration add-on program guideline (Heat)]
 +
###  [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/dns.2020.11.json Current DNS add-on program guideline (Designate)]
 +
### [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/shared_file_system.2020.11.json Current Shared File System add-on program guideline (Manila)]
 +
## Draft of the Next Guidelines
 +
### [https://opendev.org/openinfra/interop/src/branch/master/guidelines/next.json draft of the next OpenStack Powered guideline]
 +
###  [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/orchestration.next.json draft of the next Orchestration add-on program guideline (Heat)]
 +
###  [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/dns.next.json draft of the next DNS add-on program guideline (Designate)]
 +
###  [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/shared_file_system.next.json draft of the next Shared File System add-on program guideline (Manila)]
 +
## Previous Guidelines
 +
### [https://docs.opendev.org/openinfra/interop/latest/guidelines/index.html OpenStack Powered and Add-on Guidelines]
 +
### [https://opendev.org/openinfra/interop/src/branch/master/guidelines Source Directory of all previous OpenStack Powered Guidelines]
 +
### [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/ Source Directory of all previous Add-on Guidelines]
  
 
== Objective / Scope ==
 
== Objective / Scope ==
  
−
The DefCore charter 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.
+
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 the 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.
 
There are three ways in which the community uses the OpenStack brand including referring to projects.
 
# General community use of the mark
 
# General community use of the mark
 
# Project-specific use associated with development activity
 
# Project-specific use associated with development activity
−
# DefCore-governed commercial use
+
# Governed commercial use
−
 
 
−
While the top two of these uses are out of scope for DefCore, the committee has a need to participate in the discussion to ensure consistent and clear use.
 
−
 
 
−
== Current Committee Participants ==
 
−
 
 
−
=== Defcore committee (board members) ===
 
−
*  Rob H. (Co-chair)
 
−
*  Josh M. (Co-chair)
 
−
*  Alan Clark
 
−
*  Sean Roberts
 
−
*  Troy Toman
 
−
*  Randy Bias
 
−
*  Eileen Evans
 
−
*  Lew Tucker
 
−
*  Mark McLoughlin
 
−
*  Van Lindberg
 
−
*  John Zannos
 
−
 
 
−
 
 
−
=== Defcore participants (non-board member) ===
 
−
*  Anne Gentle
 
−
*  Jonathan Bryce
 
−
*  Mark Radcliffe
 
−
*  Mark Collier
 
−
*  Michael Still
 
−
*  Rochelle Grober
 
−
 
 
−
 
 
−
=== Criteria Subcommittee ===
 
−
*    Rob H.
 
−
*    Josh M.
 
−
*    John Zannos
 
−
*    Rochelle Grober
 
−
*    Troy Toman
 
−
 
 
−
 
 
−
=== Legal subcommittee ===
 
−
*    Eileen Evans
 
−
*    Mark Radcliffe
 
−
 
 
−
 
 
−
=== Former / Inactive committee participants / member ===
 
−
*      Nicolas Barcet
 
−
*      Monty Taylor
 
−
*      Russell Bryant
 
−
*      Simon Anderson
 
−
*      Todd Moore
 
  
 +
While the top two of these uses are out of the scope of the Interop Working Group, the committee has a need to participate in the discussion to ensure consistent and clear use.
  
 
== How to Engage? ==
 
== How to Engage? ==
  
−
* Read the (pending) white paper and (pending) watch the video about DefCore.
+
* Join #openstack-interop and #refstack on OFTC IRC
−
* Join the [[http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee defcore-committee]] list
+
* Follow the [https://opendev.org/osf/interop Interop code] and associated repositories: [https://opendev.org/osf/refstack Refstack], [https://opendev.org/osf/refstack-client Refstack-client] and [https://opendev.org/x/ansible-role-refstack-client ansible-role-refstack-client]
−
* Join #refstack on Freenode IRC
+
* Join our weekly [[Governance/InteropWG#Meetings|meetings]]
−
* Follow PlanetOpenStack DefCore Tag (instructions pending)
+
* Contact any team member, member profiles can be [https://wiki.openstack.org/wiki/Governance/InteropWG#Current_Committee_Leaders|found below]
−
* Follow the code at https://github.com/stackforge/refstack  
+
* Learn the [https://opendev.org/osf/interop/src/master/HACKING.rst rules for submitting changes]
−
* Register your user and then upload your test results to [[RefStack.org]] (instructions pending)
 
−
 
 
−
== RefStack ==
 
−
 
 
−
RefStack is a way of collecting and comparing test results that support the core definition process.
 
−
 
 
−
Details on using [[RefStack]]
 
−
 
 
−
== Governance Process ==
 
−
 
 
−
* Meetings will be interactive using Google Hangouts (we will already stream for non-committee members)
 
−
* Members are expected to to their homework. We will _not_ be rehashing due to time limits.
 
−
* Meetings will work from resolutions that are proposed in advance with +/- voting (cochairs are +/-2)
 
−
** as per Board of Directors policy, we welcome broad engagement but cannot allow proxies on resolutions
 
−
** resolution +/- could be asserted before the meeting (but may have to be overruled based on discussion)
 
  
−
== Process Cycles ==
+
== Meetings ==
  
−
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 DefCore 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).  
+
Since December 1st, 2022, the Interop WG meetings have been held on meetpad on https://meetpad.opendev.org/interop at 5 pm UTC every Thursday
 +
Convert time to your timezone: https://mytime.io/16pm/UTC
  
−
=== Spider (Fall 2013) ===
+
If you cannot use Meetpad, you can ping the #openstack-interop channel at 5 pm UTC on Thursday.
−
Objectives
+
The latest meeting notes/minutes are posted on the Etherpad: https://etherpad.opendev.org/p/interop.
−
# Find a consensus approach to moving forward on DefCore
+
The agenda is also posted to Etherpad: https://etherpad.opendev.org/p/interop and hashed at the start of the meeting.
−
# Define process by which Core will be defined
 
  
−
=== Elephant (Spring 2014) ===
+
[https://wiki.openstack.org/wiki/Governance/InteropWG/Minutes2020 Minutes of Interop WG 2020 meetings]
−
Objectives:
 
−
# If needed, change the bylaws to reflect the Spider Core Principles
 
−
# Establish the "must-pass" tests, processes and tools
 
−
## Define tests that will be used to determine core based on Spider cycle work
 
−
# Lower the water in the discussion to expose broader issues
 
−
## Clearly identity "elephants" that we are not ready to resolve in this cycle
 
  
−
# https://etherpad.openstack.org/p/DefCoreElephant.2<br/>
+
[https://wiki.openstack.org/wiki/Governance/InteropWG/Minutes2021 Minutes of Interop WG 2021 meetings]
−
# https://etherpad.openstack.org/p/DefCoreElephant.3<br/>
 
−
# https://etherpad.openstack.org/p/DefCoreElephant.4<br />
 
−
# https://etherpad.openstack.org/p/DefCoreElephant.5<br/>
 
  
−
=== Lighthouse (Fall 2014) ===
+
Logs of past IRC meetings [http://eavesdrop.openstack.org/meetings/interopwg/ can be found here]. Much Older meeting logs from [http://eavesdrop.openstack.org/meetings/defcore/ when the interop group was called "Defcore" are here].
−
Objectives:
 
−
# Complete Capabilities Score for Havana (Advisory), Ice House and Juno
 
−
# Recommend by-laws changes for winter voting
 
−
# Launch refstack site for data collection and sharing
 
  
−
# https://etherpad.openstack.org/p/DefCoreLighthouse.1
+
== Current Committee Leaders ==
−
# https://etherpad.openstack.org/p/DefCoreLighthouse.2
+
Current Leaders:
−
# https://etherpad.openstack.org/p/DefCoreLighthouse.3
+
* [https://www.openstack.org/community/members/profile/102303/martin-kopec Martin Kopec] (chair) -> mkopec@redhat.com, IRC nick: kopecmartin
−
# https://etherpad.openstack.org/p/DefCoreLighthouse.Bylaws1
+
* [https://www.openstack.org/community/members/profile/35705/goutham-pacharavi Goutham Pacha Ravi] (co-chair)
−
# https://etherpad.openstack.org/p/DefCoreLighthouse.F2F
+
* [https://www.openstack.org/community/members/profile/7713/arkady-kanevsky Arkady Kanevsky] (co-chair)
−
# https://etherpad.openstack.org/p/DefCoreBylawsIPE
 
  
 +
The interop WG is assisted by the [https://review.opendev.org/admin/groups/8cd7203820004ccdb67c999ca3b811534bf76d6f,members "refstack" core group] who help maintain various code repositories.
  
−
=== Future ===
+
[[category: InteropWG]]
−
Names to be decided when we get there.
+
[[Category: Working_Groups]]
−
Topics that are intentionally pushed into the future:
 
−
* OpenStack API Mark
 

Latest revision as of 17:21, 5 January 2023

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 labelled "OpenStack."

Our mission is to define "OpenStack Core" that is supported by all implementations as chartered by the by-laws.

Important Artifacts

  1. Terms Definition
  2. 10 Core Principles (board approved Hong Kong Summit)
  3. 12 Scoring Criteria (board approved Atlanta Summit)
  4. Designed Sections Principles (board approved December 2014)
  5. Interop Working Group Governance:
  6. Interop Working Group Process (board approved June 2021)
  7. Capabilities & Sections
    1. Current Guidelines
      1. Current OpenStack Powered guideline
      2. Current Orchestration add-on program guideline (Heat)
      3. Current DNS add-on program guideline (Designate)
      4. Current Shared File System add-on program guideline (Manila)
    2. Draft of the Next Guidelines
      1. draft of the next OpenStack Powered guideline
      2. draft of the next Orchestration add-on program guideline (Heat)
      3. draft of the next DNS add-on program guideline (Designate)
      4. draft of the next Shared File System add-on program guideline (Manila)
    3. Previous Guidelines
      1. OpenStack Powered and Add-on Guidelines
      2. Source Directory of all previous OpenStack Powered Guidelines
      3. Source Directory of all previous Add-on Guidelines

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 the 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.

  1. General community use of the mark
  2. Project-specific use associated with development activity
  3. Governed commercial use

While the top two of these uses are out of the scope of the Interop Working Group, the committee has a need to participate in the discussion to ensure consistent and clear use.

How to Engage?

Meetings

Since December 1st, 2022, the Interop WG meetings have been held on meetpad on https://meetpad.opendev.org/interop at 5 pm UTC every Thursday Convert time to your timezone: https://mytime.io/16pm/UTC

If you cannot use Meetpad, you can ping the #openstack-interop channel at 5 pm UTC on Thursday. The latest meeting notes/minutes are posted on the Etherpad: https://etherpad.opendev.org/p/interop. The agenda is also posted to Etherpad: https://etherpad.opendev.org/p/interop and hashed at the start of the meeting.

Minutes of Interop WG 2020 meetings

Minutes of Interop WG 2021 meetings

Logs of past IRC meetings can be found here. Much Older meeting logs from when the interop group was called "Defcore" are here.

Current Committee Leaders

Current Leaders:

The interop WG is assisted by the "refstack" core group who help maintain various code repositories.

Retrieved from "https://wiki.openstack.org/w/index.php?title=Governance/InteropWG&oldid=182463"