Jump to: navigation, search

Difference between revisions of "Governance/InteropWG"

(Current Committee Participants)
 
(48 intermediate revisions by 8 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 labeled "OpenStack."''
  
Our mission is to define "OpenStack Core" as chartered by the by-laws.
+
Our mission is to define "OpenStack Core" that is supported by all implementations as chartered by the by-laws.
  
 
== Important Artifacts ==
 
== Important Artifacts ==
# [https://github.com/openstack/defcore/blob/master/doc/source/process/Lexicon.rst Terms Definition]
+
# [https://docs.opendev.org/openinfra/interop/latest/process/Lexicon.html Terms Definition]
# [https://github.com/openstack/defcore/blob/master/doc/source/process/CoreDefinition.rst 10 Core Principles]  (board approved Hong Kong Summit)
+
# [https://docs.opendev.org/openinfra/interop/latest/process/CoreDefinition.html 10 Core Principles]  (board approved Hong Kong Summit)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/PlatformCap.rst Capability Levels: Component and Platform]  (board approved October 2014)
+
# [https://opendev.org/openinfra/interop/blob/master/doc/source/process/CoreCriteria.rst 12 Scoring Criteria]  (board approved Atlanta Summit)
# [https://github.com/openstack/defcore/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://github.com/openstack/defcore/blob/master/doc/source/process/DesignatedSections.rst 10 Designed Sections Principles]  (board approved December 2014)
+
# [https://docs.opendev.org/openinfra/interop/latest/process/GovernanceProcess.html Interop Working Group Governance:]
# [https://github.com/openstack/defcore/blob/master/doc/source/process/GovernanceProcess.rst DefCore Governance:]
+
# [https://docs.opendev.org/openinfra/interop/latest/process/2021A.html Interop Working Group Process] (board approved June 2021)
# [https://github.com/openstack/defcore/blob/master/doc/source/process/2015A.rst DefCore Process]
 
 
# Capabilities & Sections
 
# Capabilities & Sections
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.03.rst 2015.03] (review [https://github.com/openstack/defcore/blob/master/2015.03.json JSON] for details)
+
## Current Guidelines
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.04.rst 2015.04] (review [https://github.com/openstack/defcore/blob/master/2015.04.json JSON] for details)
+
###  [https://opendev.org/openinfra/interop/src/branch/master/guidelines/2020.11.json Current OpenStack Powered guideline]
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.05.rst 2015.05] (review [https://github.com/openstack/defcore/blob/master/2015.05.json JSON] for details)
+
###  [https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/orchestration.2020.11.json Current Orchestration add-on program guideline (Heat)]
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2015.07.rst 2015.07] (review [https://github.com/openstack/defcore/blob/master/2015.07.json JSON] for details)
+
##[https://opendev.org/openinfra/interop/src/branch/master/add-ons/guidelines/dns.2020.11.json Current DNS add-on program guideline (Designate)]
## [https://github.com/openstack/defcore/blob/master/doc/source/guidelines/2016.01.rst 2016.01] (review [https://github.com/openstack/defcore/blob/master/2016.01.json JSON] for details)
+
###  [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)]
## [https://github.com/openstack/defcore/blob/master/next.json next.json (current draft of next Guideline) ]
+
## 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 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.
+
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? ==
 
== How to Engage? ==
  
* Join the [http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee defcore-committee] list
+
* Join #openstack-interop and #refstack on OFTC IRC
* Join #openstack-defcore on Freenode IRC
+
* 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]
* Follow the code at https://github.com/openstack/defcore
+
* Join our weekly [[Governance/InteropWG#Meetings|meetings]]
* Join our weekly [[Governance/DefCoreCommittee#Meetings|meetings]]
+
* Learn the [https://opendev.org/osf/interop/src/master/HACKING.rst rules for submitting changes]
* Learn the [https://github.com/openstack/defcore/blob/master/HACKING.rst rules for submitting changes]
 
  
 
== Meetings ==
 
== Meetings ==
Meeting times and channels can be found on the [http://eavesdrop.openstack.org/#DefCore_Committee_Meeting official OpenStack IRC meeting list].  An [http://eavesdrop.openstack.org/irc-meetings.ical ICS file] of all OpenStack meetings is also available.  Logs of past meetings [http://eavesdrop.openstack.org/meetings/defcore/ can be found here].
 
  
== Process Cycles ==
+
Since September 23 2021, the Interop WG meetings have been held on meetpad on https://meetpad.opendev.org/interop at 4pm UTC every Thursday
 +
Convert time to your timezone: https://mytime.io/16pm/UTC
  
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).  
+
If you cannot use Meetpad, you can ping the #openstack-interop channel at 4pm UTC on Thursday.
 +
Latest meetings notes/minutes are posted on the Etherpad: https://etherpad.opendev.org/p/interop.
 +
Agenda is also posted to Etherpad: https://etherpad.opendev.org/p/interop and hashed at the start of the meeting.
  
See [https://github.com/openstack/defcore/blob/master/doc/source/process/ProcessCycles.rst Process Cycles]
+
[https://wiki.openstack.org/wiki/Governance/InteropWG/Minutes2020 Minutes of Interop WG 2020 meetings]  
  
The current cycle is named the '''''Scale Cycle'''''.
+
[https://wiki.openstack.org/wiki/Governance/InteropWG/Minutes2021 Minutes of Interop WG 2021 meetings]
 +
 
 +
Logs of past IRC meetings [http://eavesdrop.openstack.org/meetings/interopwg/ can be found here]. Much Older meetings logs from [http://eavesdrop.openstack.org/meetings/defcore/ when the interop group was called "Defcore" are here].
  
 
== Current Committee Leaders ==
 
== Current Committee Leaders ==
 
Current Leaders:
 
Current Leaders:
* [http://www.openstack.org/community/members/profile/3106 Egle Sigler] (board member, co-chair)
+
* [https://www.openstack.org/community/members/profile/102303/martin-kopec Martin Kopec] (chair)
* [https://www.openstack.org/community/members/profile/54 Mark T. Voelker] (co-chair)
+
* [https://www.openstack.org/community/members/profile/35705/goutham-pacharavi Goutham Pacha Ravi] (co-chair)
* [http://www.openstack.org/community/members/profile/10331 Chris Hoge] (Foundation staff)
+
* [https://www.openstack.org/community/members/profile/7713/arkady-kanevsky Arkady Kanevsky] (co-chair)
  
You can also find information about who is contributing to DefCore [http://stackalytics.com/?release=all&metric=commits&project_type=all&module=defcore here].
+
The interop WG is assisted by the [https://review.opendev.org/admin/groups/8cd7203820004ccdb67c999ca3b811534bf76d6f,members "refstack" core group] who help maintain various code repositories.  
  
[[category: defcore]]
+
[[category: InteropWG]]
 
[[Category: Working_Groups]]
 
[[Category: Working_Groups]]

Latest revision as of 21:07, 28 January 2022

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" 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 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 scope for Interop Working Group, the committee has a need to participate in the discussion to ensure consistent and clear use.

How to Engage?

Meetings

Since September 23 2021, the Interop WG meetings have been held on meetpad on https://meetpad.opendev.org/interop at 4pm 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 4pm UTC on Thursday. Latest meetings notes/minutes are posted on the Etherpad: https://etherpad.opendev.org/p/interop. 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 meetings 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.