049cdc68b7
In the existing documentation it suggests that the OVS agent needs to use the ML2 configuration file, however this is not the case. The Neutron Server needs to use the ML2 configuration, but the OVS agent local to the Neutron node or Compute node needs direct access to the OVS configuration file. The existing documentation guides the user to run a sed replacement of the initscript (or systemd service) for it to work succcessfully and the raw code points to a Red Hat bugzilla entry. This shouldn't be backported, but another patch for stable/icehouse should be implemented. Change-Id: I334127add2816c1967830f58f11fd806cebc71c7 Closes-Bug: #1356290
OpenStack Manuals
This repository contains documentation for the OpenStack project.
For more details, see the OpenStack Documentation wiki page.
It includes these manuals:
- Admin User Guide
- Architecture Design Guide
- Cloud Administrator Guide
- Command-Line Interface Reference
- Configuration Reference
- End User Guide
- High Availability Guide
- Installation Guides
- Virtual Machine Image Guide
In addition to the guides, this repository contains:
- docs.openstack.org:
www
Prerequisites
Apache Maven must be installed to build the documentation.
To install Maven 3 for Ubuntu 12.04 and later, and Debian wheezy and later:
apt-get install mavenOn Fedora 20 and later:
yum install mavenBuilding
The different manuals are in subdirectories of the
openstack-manuals/doc/ directory.
For example, the root directory of the OpenStack User Guide
is openstack-manuals/doc/user-guide.
To build a specific guide, look for a pom.xml file
within a subdirectory, then run the mvn command in that
directory. For example:
cd openstack-manuals/doc/user-guide/
mvn clean generate-sourcesThe generated PDF documentation file is:
openstack-manuals/doc/user-guide/target/docbkx/webhelp/user-guide.pdfThe root of the generated HTML documentation is:
openstack-manuals/doc/user-guide/target/docbkx/webhelp/user-guide/content/index.htmlTesting of changes and building of the manual
Install the python tox package and run tox from the
top-level directory to use the same tests that are done as part of our
Jenkins gating jobs.
If you like to run individual tests, run:
tox -e checkniceness- to run the niceness teststox -e checksyntax- to run syntax checkstox -e checkdeletions- to check that no deleted files are referencedtox -e checkbuild- to actually build the manual
tox will use the openstack-doc-tools package for execution of these tests.
Contributing
Our community welcomes all people interested in open source cloud computing, and encourages you to join the OpenStack Foundation.
The best way to get involved with the community is to talk with
others online or at a meet up and offer contributions through our
processes, the OpenStack wiki,
blogs, or on IRC at #openstack on
irc.freenode.net.
We welcome all types of contributions, from blueprint designs to documentation to testing to deployment scripts.
If you would like to contribute to the documents, please see the Documentation HowTo.
Bugs
Bugs should be filed on Launchpad, not GitHub:
Installing
Refer to http://docs.openstack.org to see where these documents are published and to learn more about the OpenStack project.