This adds a document that helps clarify the scope of the Nova mission
statement.
We need to keep the Nova project a manageable size. Agreeing on what
Nova should focus on is a great way to make sure we grow Nova in a
consistent way, leaving open opportunities for other projects to do a
better job of things Nova doesn't see as part of its core mission.
Part of blueprint devref-refresh-liberty
Change-Id: I4e46ee252e6b29b063bcc8204d60d670eb79daef
Our docs our wildly out of date and pretty bad, this is a first step at
beginning to clean them up and make them more useful.
* remove the guidelines section. 2 of them are explicitly wrong (API
Compatibility and Open Standards), and no one actually uses these
guidelines during development. Yes we want high availability and fault
tolerance, but listing these design guidelines here is misleading at
best.
* Don't explain how this document is built, don't need to explain that
so prominently
* Update the intro based on Nova's mission statement
Change-Id: Ia564a7cacdac0ddab913464ca1c7f9fefb0ee0b5
The toctree was globbing a nonexistent directory, and not producing
useful output. This patch lists the contents correctly.
Change-Id: I414120d948bd3eeeec84ac279bab11c276ef5eee
Per email discussion[1], v2.1 API is our CURRENT when we get to kilo and
v2 is SUPPORTED. Added links to the v2.1 API, v2 API and v2 extensions
API in our documentation
[1] http://markmail.org/message/p32p5jbvvjedg657
Depends-On: Ibe990ec93d8f9d18ef21c28979e180472df6a33d
Closes-Bug: #1435507
Change-Id: Iaa62be9612dd039f7669ff2b5587c922aba54093
Add document to replace / obsolete the giant table on
https://wiki.openstack.org/wiki/HypervisorSupportMatrix
This initial draft is a fairly straightforward conversion of
that table. Over time, it needs much work to improve the coverage
of API operations and and coverage of important configuration
information that users will care about.
It is using the .ini file syntax in order to record the data in
an easily machine parsable format, while remaining human friendly
by avoiding the syntax heavy approach of XML / JSON / YAML
An extension is registered with sphinx that can convert the
.ini file content into docutils content that then gets rendered
into the developer docs, linked from the index page
Change-Id: I4d3db4bce5737dba30a026a11083a9ea64459cd4
Don't list entire api/autoindex under Developer Docs, we already have a
model index link at the bottom of the page, showing the entire
autoindex on the home page is makes the page overwhelming.
Change-Id: I25c5b50412881b55aa745ce3da2c22466e879fcf
By setting this pbr option in setup.cfg, the doc build will fail in case
of any warnings or errors occur during the build process.
Closes-Bug: #1351350
Change-Id: Id4858062d2aaa4c2fe5b597e40e4e8947f544a4d
The doc todo list didn't actually work, so remove it. Also, the
documentation is not written by Anso Labs quite so much anymore.
Change-Id: I746a26505d331ab55565e952a1a46425458b1412
blueprint sphinx-doc-cleanup
bug 944385
- Fix formatting and markup issues that produce error messages
- Update TOC lists for missing/new files
- Fix a few links
- Update instructions with dependencies for building the documentation
- Updated base on review comments from oubiwann to fix trailing whitespace in modified files
Change-Id: I589152bfab9c543d2b11fa8bed2344259aa90675
This patch fixes the docs so that the API extensions documentation gets
included. In passing, also update the API extensions index to include
an extension that was not listed.
Change-Id: Ia16cab2b29bbc121d940dc4ed9f033340935cde8