opendev/infra-specs
Code Issues Proposed changes
f4589a8862
infra-specs/doc/source
History
James E. Blair f4589a8862 Add infra-cloud spec 
This spec describes the overall process of infra-cloud.  The
technical deployment decisions are being worked out in
Icb35adf70fa98e64dbbe0464b95af3b5de51a980.

Story: 2000175
Change-Id: Ie6a6fa331e687567b1b4b7d73499d08103671f02
Co-Authored-By: Clint Byrum <clint@fewbar.com>
2015-06-01 08:50:43 -07:00
..
conf.py Use the current date for the copyright statement 2014-09-10 16:04:37 -04:00
contributing.rst Initial commit 2014-06-10 16:25:32 -07:00
index.rst Add infra-cloud spec 2015-06-01 08:50:43 -07:00
readme.rst Initial commit 2014-06-10 16:25:32 -07:00
specs Initial commit 2014-06-10 16:25:32 -07:00
template.rst Initial commit 2014-06-10 16:25:32 -07:00

readme.rst

Infra Specs Repository

This is a git repository for doing design review on enhancements to the OpenStack Project Infrastructure. This provides an ability to ensure that everyone has signed off on the approach to solving a problem early on.

Expected Work Flow

  1. Create a story in StoryBoard with a task affecting the infra-specs project.
  2. Propose a change to infra-specs repository (ensure Story:<story number> is in the commit message).
  3. Leave a comment with the Gerrit URL of the specification.
  4. Review happens on proposal by infra-core members and others.
  5. When ready for final approval, bring forward the proposed item to the infra meeting.

Once a specification is approved...

  1. Update story, copy summary text of specification to there.
  2. Leave a comment to the git address of the specification.

Revisiting Specifications

We don't always get everything right the first time. If we realize we need to revisit a specification because something changed, either we now know more, or a new idea came in which we should embrace, we'll manage this by proposing an update to the specification in question.