Content specification

Content specification

Blueprints and specifications

The Documentation team uses specifications in the docs-specs repository to maintain large changes. Approved specifications are published at Documentation Program Specifications. For tracking purposes, a blueprint is created for each specification. It is also good practice to contact the specialty team for the book you want to change to discuss your changes before starting work.

Use blueprints and specifications:

  • When adding large sections to an existing document to ensure involvement of the docs core team.
  • When adding an entirely new deliverable to the docs project.
  • For any work that requires both content and tooling changes, such as addition of the API reference site.
  • For any large reorganization of a deliverable or set of deliverables.
  • For automation work that needs to be designed prior to proposing a patch.
  • For work that should definitely be discussed at a summit.

A specification needs two +2 votes from the docs-specs-core team. See the current list of docs-specs core team.

Use bugs against openstack-manuals or openstack-api-site:

  • For known content issues, even if you have to do multiple patches to close the bug.
  • To add content that is just missing.
  • For known errors in a document.

For more information, see Documentation bugs.

Release-specific documentation

Release-specific documentation is published continuously as changes are made, with different versions for each series.

To patch release-specific documentation, submit your patch to the master branch with “backport: xxxx” (for example, backport: kilo) in the commit message. During Pike, much of the material maintained by the documentation team was moved into project team repositories, so patching the same content for different release series may mean looking for the relevant files in multiple places.

Note

The following guides were release specific before the Pike migration:

  • Configuration reference
  • Command-line reference
  • Installation guides
  • Networking guide

For these guides, the docs.openstack.org site defaults to the current release, with the previous two releases being available under the More Releases & Languages drop-down. At release time, the documentation release team will update the default page to the new release, and remove the link to the oldest release. These docs are still available online for people who have direct URLs to the content, but they are no longer linked from the main site. For books written in DocBook XML, these old versions are clearly marked with the release name in red down the left-hand margin. We are currently developing a similar method of marking older books written in RST. The core team tracks usage of older versions, and as usage falls, can remove them entirely.

Installation Guides

Starting with Pike, the OpenStack Installation Guides are maintained by the project teams, with assistance from the documentation team. The guides describe a manual install process for multiple distributions based on openSUSE and SUSE Linux Enterprise Server; Red Hat Enterprise Linux and CentOS; and Ubuntu 16.04 (LTS).

Prior to Pike, the documentation team maintained OpenStack Installation Guides:

Document Source location Target location
Installation Guide for openSUSE and SUSE Linux Enterprise Server https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide https://docs.openstack.org/ocata/install-guide-obs/
Installation Guide for Red Hat Enterprise Linux and CentOS https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide https://docs.openstack.org/ocata/install-guide-rdo/
Installation Guide for Ubuntu 16.04 (LTS) https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide https://docs.openstack.org/ocata/install-guide-ubuntu/
Installation Guide For Debian With Debconf (is not provided for Ocata) https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide https://docs.openstack.org/newton/install-guide-debconf/
Installation Guide For Debian (is not provided for Ocata) https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide https://docs.openstack.org/newton/install-guide-debian/

Guides for deployers and administrators

As of Pike, the configuration reference and administration guide(s) are maintained by each project team.

Prior to Pike, the documentation team maintained the following combined guides:

Document Source location Target location
Configuration Reference Maintained in project specific repositories https://docs.openstack.org/ocata/config-reference/
OpenStack Networking Guide https://github.com/openstack/neutron/tree/master/doc/source/admin https://docs.openstack.org/ocata/networking-guide/

Continuously released documentation

These guides cover multiple versions and follows the general release information. The guides cover the latest two versions, for example Juno and Kilo. The following exceptions apply:

  • HA Guide: Updated last at Havana timeframe, still needs updates

Guides for end users

Document Source location Target location
OpenStack API Guide https://git.openstack.org/cgit/openstack/api-site/tree/api-quick-start https://developer.openstack.org/api-guide/quick-start/
OpenStack Command-Line Interface Reference hhttps://git.openstack.org/cgit/openstack/oslo.config/tree/master/doc/source/cli https://docs.openstack.org/cli-reference/
OpenStack Project User Guides Maintained in project specific repositories https://docs.openstack.org/user/

API documentation

Project-specific guides

Each project maintains its own guides for installation, administration, configuration reference, and contributors. They are published from each project repository. See the OpenStack Projects and the OpenStack API Bindings pages for more information.

Each project’s repo has a doc/source directory where RST source files are stored. They are built automatically with Sphinx when the patch is merged. For example, see the ` horizon documentation source <https://git.openstack.org/cgit/openstack/horizon/tree/doc/source>`_ and the built documentation.

  • Infrastructure User Manual: Reference documentation for tools and processes used for all contributors to OpenStack projects. It includes instructions on how to create all the necessary accounts, setup development environment, use gerrit review workflow. The manual also covers more advanced topics, like how to create new git repositories. The manual is maintained by the OpenStack Infrastructure team.
Document Source location Target location
Documentation Contributor Guide https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/doc-contrib-guide https://docs.openstack.org/doc-contrib-guide/
Python Developer Documentation https://git.openstack.org/cgit/openstack/<project>/tree/master/doc/source/, such as https://git.openstack.org/cgit/openstack/nova/tree/doc/source https://docs.openstack.org/openstack-projects.html
Language Bindings and Python Clients https://git.openstack.org/cgit/openstack/python-<project>client/tree/master/doc/source/, such as https://git.openstack.org/cgit/openstack/python-novaclient/tree/doc/source https://docs.openstack.org/language-bindings.html
OpenStack Project Infrastructure https://git.openstack.org/cgit/openstack-infra/system-config/tree/doc/source https://docs.openstack.org/infra/system-config/
Tempest Testing Project https://git.openstack.org/cgit/openstack/tempest/tree/doc/source https://docs.openstack.org/tempest/latest/

Guides for contributors

Licenses

This section shows the license indicators as of March 20, 2015.

  • OpenStack Architecture Design Guide: Apache 2.0 and CC-by-sa 3.0
  • OpenStack Administrator Guide: Apache 2.0 and CC-by-sa 3.0
  • OpenStack Install Guides (all): Apache 2.0
  • OpenStack High Availability Guide: Apache 2.0
  • OpenStack Configuration Reference: Apache 2.0
  • OpenStack Networking Guide: Apache 2.0
  • OpenStack Security Guide: CC-by 3.0
  • Virtual Machine Image Guide: CC-by 3.0
  • OpenStack Operations Guide: CC-by 3.0
  • OpenStack End User Guide: CC-by 3.0
  • Command-Line Interface Reference: CC-by 3.0
  • Contributor dev docs (docs.openstack.org/<projectname>/latest): none indicated in output; Apache 2.0 in repo
  • OpenStack API Quick Start: none indicated in output; Apache 2.0 in repo
  • API Complete Reference: none indicated in output; Apache 2.0 in repo
  • Infrastructure User Manual: none indicated in output; CC-by 3.0 in repo

What to do to make more consistent output:

  • OpenStack Architecture Design Guide: Apache 2.0 and CC-by 3.0
  • OpenStack Administrator Guide: Apache 2.0 and CC-by 3.0
  • OpenStack Install Guides (all): Apache 2.0 and CC-by 3.0
  • OpenStack High Availability Guide: Apache 2.0 and CC-by 3.0
  • OpenStack Security Guide: CC-by 3.0
  • Virtual Machine Image Guide: CC-by 3.0
  • OpenStack Operations Guide: CC-by 3.0
  • OpenStack End User Guide: CC-by 3.0

These guides are created by “scraping” code:

  • OpenStack Configuration Reference: Apache 2.0 and CC-by 3.0
  • Command-Line Interface Reference: Apache 2.0 and CC-by 3.0

These guides have no indicator in output:

  • Contributor dev docs (docs.openstack.org/<projectname>/latest): none indicated in output; Apache 2.0 in repo
  • OpenStack API Quick Start: none indicated in output; Apache 2.0 in repo
  • API Complete Reference: none indicated in output; Apache 2.0 in repo

This guide has a review in place to get a license indicator in output:

  • Infrastructure User Manual: none indicated in output; CC-by 3.0 in repo
Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.