From f1d59a8130dce2ac9295bc5495e628fdb752b74d Mon Sep 17 00:00:00 2001
From: ahothan <ahothan@cisco.com>
Date: Thu, 1 Nov 2018 08:17:49 -0700
Subject: NFVBENCH-105 ARP not working with NFVbench 2.0

Fix type in arp record field.
Remove unneeded code.

Change-Id: I7a77f66c5e1c357907f4fd113f864708a351f152
Signed-off-by: ahothan <ahothan@cisco.com>
---
 docs/development/design/ndrpdr.rst            | 4 ++--
 docs/development/design/versioning.rst        | 8 +-------
 docs/testing/developer/devguide/index.rst     | 8 ++++++++
 docs/testing/user/configguide/configguide.rst | 8 ++++++++
 4 files changed, 19 insertions(+), 9 deletions(-)

(limited to 'docs')

diff --git a/docs/development/design/ndrpdr.rst b/docs/development/design/ndrpdr.rst
index e34e8ba..dd769c0 100644
--- a/docs/development/design/ndrpdr.rst
+++ b/docs/development/design/ndrpdr.rst
@@ -79,5 +79,5 @@ consideration:
 - actual Tx rate is always <= requested Tx rate
 - the measured drop rate should always be relative to the actual Tx rate
 - if the actual Tx rate is < requested Tx rate and the measured drop rate is already within threshold
- (<NDR/PDR threshold) then the binary search must stop with proper warning because the actual NDR/PDR
- might probably be higher than the reported values
+  (<NDR/PDR threshold) then the binary search must stop with proper warning because the actual NDR/PDR
+  might probably be higher than the reported values
diff --git a/docs/development/design/versioning.rst b/docs/development/design/versioning.rst
index 870ed86..8103534 100644
--- a/docs/development/design/versioning.rst
+++ b/docs/development/design/versioning.rst
@@ -8,15 +8,9 @@ Versioning
 ==========
 
 NFVbench uses semver compatible git tags such as "1.0.0". These tags are also called project tags and applied at important commits on the master branch exclusively.
-Rules for the version numbers follow the semver 2.0 specification (http://semver.org).
+Rules for the version numbers follow the semver 2.0 specification (https://semver.org).
 These git tags are applied indepently of the OPNFV release tags which are applied only on the stable release branches (e.g. "opnfv-5.0.0").
 
 In general it is recommeneded to always have a project git version tag associated to any OPNFV release tag content obtained from a sync from master.
 
 NFVbench Docker containers will be versioned based on the OPNF release tags or based on NFVbench project tags.
-
-
-
-
-
-
diff --git a/docs/testing/developer/devguide/index.rst b/docs/testing/developer/devguide/index.rst
index e69de29..e219889 100644
--- a/docs/testing/developer/devguide/index.rst
+++ b/docs/testing/developer/devguide/index.rst
@@ -0,0 +1,8 @@
+.. _nfvbench-releasenotes:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+
+***************
+Developer Guide
+***************
diff --git a/docs/testing/user/configguide/configguide.rst b/docs/testing/user/configguide/configguide.rst
index e69de29..f790d21 100644
--- a/docs/testing/user/configguide/configguide.rst
+++ b/docs/testing/user/configguide/configguide.rst
@@ -0,0 +1,8 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International
+.. License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) Cisco Systems, Inc
+
+*******************
+Configuration Guide
+*******************
-- 
cgit 1.2.3-korg