Code Review
/
apex.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
review
|
tree
raw
|
inline
| side by side
Allow all in one deployments
[apex.git]
/
docs
/
release
/
installation
/
troubleshooting.rst
diff --git
a/docs/release/installation/troubleshooting.rst
b/docs/release/installation/troubleshooting.rst
index
ed0d1ff
..
f5b4208
100644
(file)
--- a/
docs/release/installation/troubleshooting.rst
+++ b/
docs/release/installation/troubleshooting.rst
@@
-5,7
+5,7
@@
This section aims to explain in more detail the steps that Apex follows
to make a deployment. It also tries to explain possible issues you might find
in the process of building or deploying an environment.
to make a deployment. It also tries to explain possible issues you might find
in the process of building or deploying an environment.
-After installing the Apex RPMs in the
jumph
ost, some files will be located
+After installing the Apex RPMs in the
Jump H
ost, some files will be located
around the system.
1. /etc/opnfv-apex: this directory contains a bunch of scenarios to be
around the system.
1. /etc/opnfv-apex: this directory contains a bunch of scenarios to be
@@
-17,13
+17,10
@@
around the system.
2. /usr/bin/: it contains the binaries for the commands opnfv-deploy,
opnfv-clean and opnfv-util.
2. /usr/bin/: it contains the binaries for the commands opnfv-deploy,
opnfv-clean and opnfv-util.
-3. /var/opt/opnfv/: it contains several files and directories.
+3. /usr/share/opnfv/: contains Ansible playbooks and other non-python based
+ configuration and libraries.
- 3.1. images/: this folder contains the images that will be deployed
- according to the chosen scenario.
-
- 3.2. lib/: bunch of scripts that will be executed in the different phases
- of deployment.
+4. /var/opt/opnfv/: contains disk images for Undercloud and Overcloud
Utilization of Images
Utilization of Images
@@
-85,18
+82,11
@@
executed. However, some other cases it could be worth it to try to debug it.
OpenDaylight Integration
------------------------
OpenDaylight Integration
------------------------
-When a user deploys any of the following scenarios:
-
- - os-odl-bgpvpn-ha.yaml
- - os-odl_l2-fdio-ha.yaml
- - os-odl_l2-fdio-noha.yaml
- - os-odl_l2-nofeature-ha.yaml
- - os-odl_l2-sfc-noha.yaml
- - os-odl_l3-nofeature-ha.yaml
+When a user deploys a scenario that starts with os-odl*:
-OpenDaylight (ODL) SDN controller will be deployed
too and completely
-integrated with OpenStack. ODL is running as a systemd service, so you can
-
manage it
as a regular service:
+OpenDaylight (ODL) SDN controller will be deployed
and integrated with
+OpenStack. ODL will run as a systemd service, and can be managed as
+as a regular service:
``systemctl start/restart/stop opendaylight.service``
``systemctl start/restart/stop opendaylight.service``
@@
-142,3
+132,13
@@
some possible solutions or workarounds to get the process continued.
it will pass a different value for step each time. There is a total of
five steps. Some of these steps will not be executed depending on the
type of scenario that is being deployed.
it will pass a different value for step each time. There is a total of
five steps. Some of these steps will not be executed depending on the
type of scenario that is being deployed.
+
+Reporting a Bug
+---------------
+
+Please report bugs via the `OPNFV Apex JIRA <https://wiki.opnfv.org/apex>`_
+page. You may now use the log collecting utility provided by Apex in order
+to gather all of the logs from the overcloud after a deployment failure. To
+do this please use the ``opnfv-pyutil --fetch-logs`` command. The log file
+location will be displayed at the end of executing the script. Please attach
+this log to the JIRA Bug.