opendev/infra-specs
Code Issues Proposed changes
infra-specs/doc/source
History
Monty Taylor 8117480559
Update config management for the Infra Control Plane 
As the Infra team collectively enjoys hacking on our Puppet system less
and less it's time to look at systemic changes. Any change to these
underlying systems is costly, so rather than undertaking a mild and
incremental update to what we're doing, let's embrace Ansible and
containerized services.

Co-Authored-By: Paul Belanger <pabelanger@redhat.com>
Co-Authored-By: Colleen Murphy <colleen@gazlene.net>
Change-Id: I8f0d96acbfdea3f285d01300ff7b32e9a9bbe606
2018-07-13 07:11:46 -05: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
Update config management for the Infra Control Plane
2018-07-13 07:11:46 -05: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 on the story 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.