
If we change configuration files right after installing service packages, automatically started services may pick up changed configuration files rather than the default files they were packaged with. If the neutron-l3-agent starts with our custom configuration file which refers to the external bridge br-ex while that bridge is not there (yet), the port is permanently marked as unavailable (vlan tag=4095). In such a case, a line like this can be found in /etc/openvswitch/conf.db: {"_date":1435514607570, "Port":{"20b0e96c-6103-46e6-a234-a4d5439eece7":{"tag":4095}}, "_comment":" ovs-vsctl: /usr/bin/ovs-vsctl --timeout=10 set Port qr-4be1ab91-60 tag=4095" ,"Open_vSwitch":{"e00f3d6f-e55a-419a-a605-141021026dee":{"next_cfg":15}}} For additional information, check this neutron bug: Neutron openvswitch-agent doesn't recover ports from binding_failed status https://bugs.launchpad.net/neutron/+bug/1399249 This is another race -- waiting for a few seconds before changing the configuration files fixes the problem. The alternative used in this patch is to stop the neutron-l3-agent before editing the configuration files and to start it only once the bridge is ready. Change-Id: I55762d17817e5e1cdb4c0420374c9fbc314bdff1 Co-Authored-By: Vigneshvar.A.S <vigneshvar.a.s@gmail.com> Co-Authored-By: sayalilunkad <sayali.92720@gmail.com>
OpenStack Training Guides
This repository contains open source training manuals that can be used to learn about the OpenStack project.
For more details, see the OpenStack Training Guides wiki page.
It includes these guides:
- Associate Guide
- Operator Guide
- Developer Guide
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 maven
On Fedora 20 and later:
yum install maven
Building
The different guides are in subdirectories of the doc/
directory.
To build the guides, look for a pom.xml
file within a
subdirectory, then run the mvn
command in that directory.
For example:
cd doc/training-guides/
mvn clean generate-sources
The generated PDF documentation file is:
doc/training-guides/target/docbkx/webhelp/training-guides/training-guides.pdf
The root of the generated HTML documentation is:
doc/training-guides/target/docbkx/webhelp/training-guides/content/index.html
Testing 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.