Reorganize docs into the appropriate folders for the new sphinx build.
JIRA: VSPERF-80
Change-Id: I9dcd74e092ce52546a0986b92a1ebb2b5b7419bf
Signed-off-by: Ramprasad Velavarthipati <ram.v@freescale.com>
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
Reviewed-by: Trinath Somanchi <trinath.somanchi@gmail.com>
--- /dev/null
+.. OPNFV Release Engineering documentation, created by
+ sphinx-quickstart on Tue Jun 9 19:12:31 2015.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+.. image:: ../etc/opnfv-logo.png
+ :height: 40
+ :width: 200
+ :alt: OPNFV
+ :align: left
+
+VSPERF Design
+=======================================
+
+Contents:
+
+.. toctree::
+ :numbered:
+ :maxdepth: 4
+
+ vswitchperf_design.rst
+
+* :ref:`search`
+
+Revision: _sha1_
+
+Build date: |today|
This is a typical flow of control for a test.
-.. image:: images/vsperf.png
+.. image:: ../images/vsperf.png
Configuration
Traffic Controller's Role
-------------------------
-.. image:: images/traffic_controller.png
+.. image:: ../images/traffic_controller.png
Loader & Component Factory
The working of the Loader package (which is responsible for *finding* arbitrary classes based on configuration data) and the Component Factory which is responsible for *choosing* the correct class for a particular situation - e.g. Deployment Scenario can be seen in this diagram.
-.. image:: images/factory_and_loader.png
+.. image:: ../images/factory_and_loader.png
Routing Tables
==============
--- /dev/null
+.. OPNFV Release Engineering documentation, created by
+ sphinx-quickstart on Tue Jun 9 19:12:31 2015.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+.. image:: ../etc/opnfv-logo.png
+ :height: 40
+ :width: 200
+ :alt: OPNFV
+ :align: left
+
+VSPERF Guides and Installation
+========================================
+
+Contents:
+
+.. toctree::
+ :numbered:
+ :maxdepth: 4
+
+ quickstart.rst
+ installation.rst
+
+* :ref:`search`
+
+Revision: _sha1_
+
+Build date: |today|
--------------
-.. |Alt text| image:: images/TCLServerProperties.png
+.. |Alt text| image:: ../images/TCLServerProperties.png
--- /dev/null
+.. OPNFV Release Engineering documentation, created by
+ sphinx-quickstart on Tue Jun 9 19:12:31 2015.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+.. image:: etc/opnfv-logo.png
+ :height: 40
+ :width: 200
+ :alt: OPNFV
+ :align: left
+
+VSPERF
+=======================================
+
+Contents:
+
+.. toctree::
+ :maxdepth: 4
+ :titlesonly:
+
+ guides/index
+ design/index
+ test_spec/index
+ updates/index
+
+* :ref:`search`
+
+Revision: _sha1_
+
+Build date: |today|
:alt: OPNFV
:align: left
-Example Documentation table of contents
+VSPERF Test Specification
=======================================
Contents:
:maxdepth: 4
quickstart.rst
+ installation.rst
NEWS.rst
vswitchperf_ltd.rst
- installation.rst
-
-Indices and tables
-==================
+ vswitchperf_design.rst
* :ref:`search`
meaning to different groups of people. In this document we will
simply use the term packet delay variation. The preferred form for this
metric is the PDV form of delay variation defined in `RFC5481
- <https://www.rfc-editor.org/rfc/rfc5481.txt>`__. The most relevant
+ <https://www.rfc-editor.org/rfc/rfc5481.txt>`__. The most relevant
measurement of PDV considers the delay variation of a single user flow,
as this will be relevant to the size of end-system buffers to compensate
- for delay variation. The measurement system's ability to store the
- delays of individual packets in the flow of interest is a key factor
- that determines the specific measurement method. At the outset, it is
+ for delay variation. The measurement system's ability to store the
+ delays of individual packets in the flow of interest is a key factor
+ that determines the specific measurement method. At the outset, it is
ideal to view the complete PDV distribution. Systems that can capture
- and store packets and their delays have the freedom to calculate the
+ and store packets and their delays have the freedom to calculate the
reference minimum delay and to determine various quantiles of the PDV
- distribution accurately (in post-measurement processing routines).
+ distribution accurately (in post-measurement processing routines).
Systems without storage must apply algorithms to calculate delay and
- statistical measurements on the fly. For example, a system may store
- temporary estimates of the mimimum delay and the set of (100) packets
+ statistical measurements on the fly. For example, a system may store
+ temporary estimates of the mimimum delay and the set of (100) packets
with the longest delays during measurement (to calculate a high quantile,
- and update these sets with new values periodically.
- In some cases, a limited number of delay histogram bins will be
+ and update these sets with new values periodically.
+ In some cases, a limited number of delay histogram bins will be
available, and the bin limits will need to be set using results from
repeated experiments. See section 8 of `RFC5481
<https://www.rfc-editor.org/rfc/rfc5481.txt>`__.
--- /dev/null
+.. OPNFV Release Engineering documentation, created by
+ sphinx-quickstart on Tue Jun 9 19:12:31 2015.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+.. image:: ../etc/opnfv-logo.png
+ :height: 40
+ :width: 200
+ :alt: OPNFV
+ :align: left
+
+VSPERF News
+=======================================
+
+Contents:
+
+.. toctree::
+ :numbered:
+ :maxdepth: 4
+
+ NEWS.rst
+
+* :ref:`search`
+
+Revision: _sha1_
+
+Build date: |today|