Jump to: navigation, search

Difference between revisions of "Governance/InteropWG"

(reflect meeting actions)
m (→‎Current Committee Leaders)
 
(163 intermediate revisions by 21 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.
  
−
Our mission is to define "OpenStack Core" as chartered by the by-laws and guided by [[Governance/CoreDefinition]]
+
''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."''
  
−
This page is work in process....
+
Our mission is to define "OpenStack Core" that is supported by all implementations as chartered by the by-laws.
  
−
== How to Engage? ==
+
== Important Artifacts ==
 +
# [https://docs.opendev.org/openinfra/interop/latest/process/Lexicon.html Terms Definition]
 +
# [https://docs.opendev.org/openinfra/interop/latest/process/CoreDefinition.html 10 Core Principles]  (board approved Hong Kong Summit)
 +
# [https://opendev.org/openinfra/interop/blob/master/doc/source/process/CoreCriteria.rst 12 Scoring Criteria]  (board approved Atlanta Summit)
 +
# [https://docs.opendev.org/openinfra/interop/latest/process/DesignatedSections.html10 Designed Sections Principles]  (board approved December 2014)
 +
# [https://docs.opendev.org/openinfra/interop/latest/process/GovernanceProcess.html  Interop Working Group Governance:]
 +
# [https://docs.opendev.org/openinfra/interop/latest/process/2021A.html Interop Working Group Process]  (board approved June 2021)
 +
# 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]
  
−
> There is a lot of pending items here...
+
== Objective / Scope ==
  
−
* Read the (pending) white paper and (pending) watch the video about DefCore.
+
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.
−
* Join the [[http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee defcore-committee]] list
 
−
* Join #refstack on Freenode IRC
 
−
* Follow PlanetOpenStack DefCore Tag (instructions pending)
 
−
* Follow the code at https://github.com/openstack-ops/refstack (instructions pending)
 
−
* Register your user and then upload your test results to [[RefStack.org]] (instructions pending)
 
  
−
== Governance Process ==
+
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
  
−
* Meetings will be interactive using Google Hangouts (we will already stream for non-committee members)
+
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.
−
* 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 ==
+
== How to Engage? ==
−
 
 
−
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).
 
−
 
 
−
=== Spider (previous, Fall 2013) ===
 
−
Objectives
 
−
# Find a consensus approach to moving forward on DefCore
 
−
# Define process by which Core will be defined
 
−
 
 
−
=== Elephant (current, Spring 2014) ===
 
−
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
 
  
−
=== Future ===
+
* Join #openstack-interop and #refstack on OFTC IRC
−
Names to be decided when we get there.
+
* 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]
−
Topics ("Elephants") that are intentionally pushed into the future:
+
* Join our weekly [[Governance/InteropWG#Meetings|meetings]]
−
* OpenStack Compatible Mark
+
* Contact any team member, member profiles can be [https://wiki.openstack.org/wiki/Governance/InteropWG#Current_Committee_Leaders|found below]
−
* ... Committee Chairs will add to this ...
+
* Learn the [https://opendev.org/osf/interop/src/master/HACKING.rst rules for submitting changes]
  
−
== Meetings/Agenda Schedule ==
+
== Meetings ==
  
−
=== Meeting 11/20 prep ===
+
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
  
−
# Agenda / Notes / Minutes [[https://etherpad.openstack.org/p/Core-Prekickoff-Agenda][Committee Structure Planning]]
+
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.
  
−
=== Meeting 12/3 8:30 - 10:30 PDT Agenda ===
+
[https://wiki.openstack.org/wiki/Governance/InteropWG/Minutes2020 Minutes of Interop WG 2020 meetings]
  
−
Conducted on Google Hangout (link on the #DefCore IRC).  Please use https://join.me/490-943-591 as a backup channel.
+
[https://wiki.openstack.org/wiki/Governance/InteropWG/Minutes2021 Minutes of Interop WG 2021 meetings]
  
−
# Approve Timeline for Implementation for Havana & Icehouse
+
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].
−
# Bylaws change - Discuss Bylaws change proposal
 
−
# Kick off the test selection criteria sub-committee
 
−
# [[RefStack.org]] review / demo
 
−
# Question: do we need to have multiple levels?
 
−
## if so, Need to decide on naming for levels of compliance. E.g.: "core/concensus" and "commons" and "edge"  
 
−
# Program vs Project Definition Discussion
 
−
# Define a process by which
 
−
## programs are nominated for use with the mark
 
−
## by which tests certified for use with the mark
 
−
## test list is vetted and approved by the board
 
  
−
=== Meeting 12/17 3pm PDT Agenda  ===
+
== Current Committee Leaders ==
 +
Current Leaders:
 +
* [https://www.openstack.org/community/members/profile/102303/martin-kopec Martin Kopec] (chair) -> mkopec@redhat.com, IRC nick: kopecmartin
 +
* [https://www.openstack.org/community/members/profile/35705/goutham-pacharavi Goutham Pacha Ravi] (co-chair)
 +
* [https://www.openstack.org/community/members/profile/7713/arkady-kanevsky Arkady Kanevsky] (co-chair)
  
−
Agenda & Minutes updated on https://etherpad.openstack.org/p/DefCoreElephant.2
+
The interop WG is assisted by the [https://review.opendev.org/admin/groups/8cd7203820004ccdb67c999ca3b811534bf76d6f,members "refstack" core group] who help maintain various code repositories.  
  
−
# OIN impacts from Core/Commons definition
+
[[category: InteropWG]]
−
# How to figure out where we have gaps in Tempest coverage
+
[[Category: Working_Groups]]
−
# Program vs Project Definition Discussion
 
−
## Define a process by which programs are nominated for use with the mark by which tests certified for use with the mark test list is vetted and approved by the board
 

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"