OpenStack Infrastructure Blueprint Repository
c872f8f6a4
The original plan to migrate all OpenStack projects may have been overly-ambitious, but more importantly it's a policy decision outside the Infrastructure team's immediate sphere of control. Most identified gaps in the intervening years have been addressed, with some final ones (like attachments) under review nearing completion or well into a planning stage (like self-service team management). There will always be new features some teams want, and indefinitely delaying completion of this spec for such a treadmill is unnecessary. Update the spec to only cover the original well-established first phase, and remove the hand-wavy stubs for a second phase where "everybody agrees to migrate." Also remove the dependency on central identity management as there is no clear path forward on it presently. Many teams are already relying on StoryBoard today, and the handful of developers and maintainers for it hold fairly regular meetings and can be reached readily with questions, concerns or suggestions. Further improvement to StoryBoard remains a priority for them, but it doesn't need to be a priority spec for the Infrastructure team for that to be the case. Change-Id: I5092211bfe59646f6db0adae6075b41cb312c6ad |
||
|---|---|---|
| doc/source | ||
| specs | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| template.rst | ||
| test-requirements.txt | ||
| tox.ini | ||
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
- Create a story in StoryBoard with a task affecting the opendev/infra-specs project
- Propose a change to this repository and make sure
Task: #<taskid>for the corresponding story's initial task is included as a footer in the commit message (seeCONTRIBUTING.rstfor relevant documentation links). This change should also add an entry for the proposed spec document in theApproved Design Specificationssection of thedoc/source/index.rstfile. - Once proposed, members of the community provide feedback through code review, and the specification should be revised until there seems to be some reasonable consensus as to its fitness.
- When ready for final approval, request addition of a call for votes to the weekly infra meeting agenda.
- If agreed by the meeting attendees, the chair will announce an approval deadline before which members of the Infrastructure Council are asked to cast their roll call votes on the proposal under review.
Once a specification is approved...
- Update the story, copying summary text of specification to there.
- Leave a comment linking to the published URL of the specification on the specs site.
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.