docs: updates and move traffic gens to separate doc

Move the traffic gen instructions to a separate user guide and add
information on usage of the Dummy traffic generator. Update docs
to fix PDF build failure and do general clean-up. Removed the numbering
from the LTD and added the numbered directive to automate numbering for
sections and headers. Add comment anchors that reflect the section
numbers.

Change-Id: I984ca38456a891c439697ebc1da041bc1d828a15
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>

1 files changed, 0 insertions, 48 deletions

diff --git a/docs/guides/installation.rst b/docs/guides/installation.rst
deleted file mode 100755
index 5047dce4..00000000
--- a/docs/guides/installation.rst
+++ /dev/null
@@ -1,48 +0,0 @@
-Installing vswitchperf
-======================
-
-The test suite requires Python 3.3 and relies on a number of other
-packages. These need to be installed for the test suite to function. To
-install Python 3.3 in CentOS 7, an additional repository, Software
-Collections (see
-https://www.softwarecollections.org/en/scls/rhscl/python33) should be
-enabled.
-
-Installation of required packages and preparation of Python 3 virtual
-environment is performed by systems/build_base_machine.sh. It should be
-executed under user account, which will be used for vsperf execution.
-Please Note: Password-less sudo access must be configured for given
-user account before script is executed.
-
-Execution of installation script:
-
-.. code:: bash
-
-    cd systems
-    ./build_base_machine.sh
-
-Please note: you don't need to go into any of the systems subdirectories,
-simply run the top level build_base_machine.sh, your OS will be detected
-automatically.
-
-You will need to activate the virtual environment every time you start a
-new shell session. To activate, simple run:
-
-.. code:: bash
-
-    scl enable python33 bash
-    cd $HOME/vsperfenv
-    source bin/activate
-
---------------
-
-Working Behind a Proxy
-======================
-
-If you're behind a proxy, you'll likely want to configure this before
-running any of the above. For example:
-
-  .. code:: bash
-
-    export http_proxy=proxy.mycompany.com:123
-    export https_proxy=proxy.mycompany.com:123