diff options
| author |   ahothan <ahothan@cisco.com> | 2018-11-01 08:17:49 -0700 |
|---|---|---|
| committer | ahothan <ahothan@cisco.com> | 2018-11-01 08:17:49 -0700 |
| commit | f1d59a8130dce2ac9295bc5495e628fdb752b74d (patch) | |
| tree | b924612036158d7d3cbc448390e1a897ffc67302 /docs/development | |
| parent | ed33e56c9b8771ed9d22fc3cc19e049a76137db8 (diff) | |
NFVBENCH-105 ARP not working with NFVbench 2.02.0.2
Fix type in arp record field.
Remove unneeded code.
Change-Id: I7a77f66c5e1c357907f4fd113f864708a351f152
Signed-off-by: ahothan <ahothan@cisco.com>
Diffstat (limited to 'docs/development')
| -rw-r--r-- | docs/development/design/ndrpdr.rst | 4 | ||||
| -rw-r--r-- | docs/development/design/versioning.rst | 8 |
2 files changed, 3 insertions, 9 deletions
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. - - - - - - |