This introduces and "Open Infrastructure" page which is designed for a
moderately experienced developer with some understanding of Zuul,
Ansible and basic Linux admin skills to have an entrypoint to
navigating the system-config and related repositories.
It is designed to re-enforce the idea of open infrastructure, and
explain how development, testing and production come together at a
level high enough to be understood, but with links or descriptions of
specific places in the code to get started.
It moves a little of what was in the sysadmin page into this, and
leaves that page as more low-level descriptions of various tasks.
Change-Id: I60a9299df455b98ad549ac0075a59d381722bc06
Update conf.py and index.rst for OpenDev.
Use newer openstackdocstheme and update conf.py for this.
Change-Id: I62312ca1d3fda9221660b7bb664c8ea55dac68a4
Since we're building out roles in system-config now, generate
documentation. We look in roles/* and playbook/roles/* (follow-on
changes will split things up between the two).
Correct the reference names in the exim documentation to avoid
warnings and failure.
This also revealed a single unicode character in the exim readme
(which caused prior versions of zuul-sphinx to barf). For fun, see if
you can find it!
Depends-On: https://review.openstack.org/#/c/579474/
Change-Id: I243a96bbd6d09560f8aa80b6345b90039422547a
We don't run a cloud anymore and don't use these. With the cfg
management update effort, it's unlikely we'd use them in the form they
are in even if we did get more hardware and decide to run a cloud again.
Remove them for clarity.
Change-Id: I88f58fc7f2768ad60c5387eb775a340cac2c822a
Do not link to wiki but instead to special purpose pages - infra manual
for developers, docs main page for users.
Change-Id: Ic8c1aa5ce6b81f9b936290db68f357d6574b9a0e
This does not include many details, and for good reason. Many of these
things are open questions. I am not sure if we should add a section on
the specific hardware/locations or not, so that is up to date.
The document is written in the present tense, so as we make these things
true, they won't have to be altered. The status section should reflect
how close to reality the documentation is until we implement some of it.
story: 2000175
Change-Id: Icb35adf70fa98e64dbbe0464b95af3b5de51a980
This is my recollection of the consensus from some infra folk on a
train late at night: it's probably wrong, but I wanted something I can
point contributors at.
Change-Id: Ic1ad99335ce41481995322f0ee5daadb08a09c2a
It is a HOWTO and it isn't part of the flow of the main docs,
which are focused on how the OpenStack project infrastructure
is used and operated.
Change-Id: I6e783899ab55f952acab81c7c90ca596d9bb1603
This is incomplete, but as I haven't got a full thing up yet I can't
write it all. It is minimally a useful pointer for other folk trying
to do the same thing.
Change-Id: Iefb62a0ff60e5f46f1f0091beef54bfc4a376a53
Move the toctree from the HOWTOs sidebar on the front
page to a hidden toctree after the main toctree.
Create manual links to the HOWTOs docs in the sidebar.
This fixes the fact that the "next" link in the docs
navigated to one of the sidebars first, instead of the
introductory "Infrastructure Project" doc, while keeping
those sidebars in the toctree navigation so if someone
reads the docs straight through they get every page.
Change-Id: I5e1c23b7d3ce324bbd9e333cf6e898b33601982e
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
Reviewed-on: https://review.openstack.org/32630
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Reviewed-by: Elizabeth Krumbach Joseph <lyz@princessleia.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
The goal is to re-orient the documentation as an introduction for new
contributors and a reference for all contributors.
Change-Id: I8702a5ace908c7618a6451bbfef7fc79b07429ff
Reviewed-on: https://review.openstack.org/30515
Reviewed-by: Elizabeth Krumbach Joseph <lyz@princessleia.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Tested-by: Jenkins
Change-Id: I409bd50ae374e0288531f07cfeea34856c5f8067
Reviewed-on: https://review.openstack.org/17319
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: James E. Blair <corvus@inaugust.com>
Add a page for StackForge that includes a blurb about what StackForge is
and is not, and how to add a StackForge project.
Change-Id: I474b626423952018eb23929d395ac038c082cd25
Reviewed-on: https://review.openstack.org/17411
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Tested-by: Jenkins
The existing ci-docs job is a one off job that was configured by hand.
Define the ci-docs job as a Jenkins Job Builder job using the existing
project-docs utilities.
To make the existing utilities work within the puppet repo the doc files
have been moved to doc/source, setup.cfg added to build docs in the new
dir, setup.py builds openstack-ci-puppet (instead of nova), tox now has
a venv virtualenv, and the .gitignore has been updated appropriately.
Change-Id: Ic0f291af181b4ef8eff62c5ec7cf3ccfa5b79800
Reviewed-on: https://review.openstack.org/13729
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
