openinfra/interop
Code Issues Proposed changes
96dc21ee32
interop/process/ProcessCycles.rst
Mark T. Voelker 96dc21ee32 Close Scale, Open Flag in ProcessCycles.rst 
Last week at the OpenStack Liberty Design Summit in Vancouver we held
a DefCore workshop that served as the first meeting of the "Flag"
cycle.  During the meeting we discussed a few objectives and started
our first Flag cycle etherpad [1].  Thus, it's time to tidy up some of
our process documentation.

This patch adds a section for the Flag cycle and some objectives for it
that were discussed at prior meetings in the Scale cycle and at the
inaugural Flag cycle meeting.  It also adds all missing meeting
information for the Scale cycle to the appropriate section, thus paving
the way for us to eventually remove it from the wiki (which will become
very cluttered if we don't prune it once in a while) but still have it
archived.

[1] https://etherpad.openstack.org/p/DefCoreFlag.1

Change-Id: I272c07eb232537f0981f187a3ec74e37ea005a72
2015-05-23 14:31:04 -07:00

4.5 KiB
Raw Blame History

Process Cycles

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 (Fall 2013)

Objectives

  • Find a consensus approach to moving forward on DefCore
  • Define process by which Core will be defined

Elephant (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

Meetings

Lighthouse (Fall 2014)

Objectives

* Complete Capabilities Score for Havana (Advisory), Icehouse and Juno

  • Recommend by-laws changes for winter voting
  • Launch refstack site for data collection and sharing

Meetings

Scale Cycle (Spring 2015)

Objectives

  • Capabilities for I & J
  • Process approved by TC & Board

Process Meetings

Capabilities Meetings

Flag Cycle (Spring - Summer 2015)

Objectives

  • Improve and clearly document the test flagging process.
  • Ensure that DefCore/RefStack can include tests that are not run via Tempest.
  • Determine a path forward for components with overlapping capabilities (such as networking).

Meetings

Meeting information for the Flag cycle will be archived here once the cycle is complete. During the cycle, please refer to the DefCore Committee wiki page.

Future

Names to be decided when we get there. Topics that are intentionally pushed into the future:

  • OpenStack API Mark