be794fb168
MANILA_MULTI_BACKEND has been deprecated for five years now, we should remove it from our code base. This variable was removed from the settings scripts along with: MANILA_BACKEND1_CONFIG_GROUP_NAME and MANILA_SHARE_BACKEND1_NAME; MANILA_BACKEND2_CONFIG_GROUP_NAME and MANILA_SHARE_BACKEND2_NAME. Because they work in the same context. Instead of them, the already implemented and in use, MANILA_ENABLED_BACKENDS variable was placed to garantee the successful back-end setup. The same replacement was made in the contribution samples scripts. Apart from this, we avoid configuring generic1 and generic2 if another backend/s are selected. Closes-Bug: #1898791 Closes-Bug: #1878477 Change-Id: I67036a65da9255694a00a9c8d56cfdefbdf23c05 |
||
|---|---|---|
| .. | ||
| ext | ||
| source | ||
| README.rst | ||
| requirements.txt | ||
Manila Development Docs
Files under this directory tree are used for generating the documentation for the manila source code.
Developer documentation is built to: https://docs.openstack.org/manila/latest/
Tools
- Sphinx
-
The Python Sphinx package is used to generate the documentation output. Information on Sphinx, including formatting information for RST source files, can be found in the Sphinx online documentation.
- Graphviz
-
Some of the diagrams are generated using the
dotlanguage from Graphviz. See the Graphviz documentation for Graphviz and dot language usage information.
Building Documentation
Doc builds are performed using tox with the docs
target:
% cd ..
% tox -e docs