Go to file
Yolanda Robla efc2da86a7 Zuul could use different yaml files
Currently zuul is relying on a single layout.yaml file. We could
split that on different files as we have in jenkins job builder
to improve usability of the system.

https://storyboard.openstack.org/#!/story/337

Change-Id: Ic826be1406370411bb58bb6fc551d5a748830644
2014-12-05 10:47:18 +01:00
2014-12-05 10:47:18 +01:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-05-20 16:36:13 +00:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-09-10 16:04:35 -04:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00
2014-06-10 16:25:32 -07:00

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.

Repository Structure

The expected structure of the respository is as follows:

specs/
    implemented/

Expected Work Flow

  1. Create a story in StoryBoard with a task affecting the infra-specs project.
  2. Propose review to infra-specs repository (ensure Story:<story number> is in the commit message).
  3. Leave a comment with the Gerrit address of the specification.
  4. Bring forward the proposed item to the infra meeting for summary.
  5. Review happens on proposal by infra-core members and others.
  6. Iterate until review is Approved or Rejected.

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.

Learn As We Go

This is a new way of attempting things, so we're going to be low in process to begin with to figure out where we go from here. Expect some early flexibility in evolving this effort over time.

Description
OpenStack Infrastructure Blueprint Repository
Readme 4.5 MiB
Languages
Python 100%