From 55409f779ba0f05ffca52f6ad31ca5b3575c9b53 Mon Sep 17 00:00:00 2001 From: ahothan Date: Sat, 4 Nov 2017 21:13:13 +1100 Subject: Update hw requirements Change-Id: I7e403ec5a550804b43c685bdbfd70c8bff7a2d70 Signed-off-by: ahothan --- docs/testing/user/userguide/hw_requirements.rst | 11 +- .../userguide/images/nfvbench-spirent-setup.svg | 170 --------------- .../user/userguide/images/nfvbench-trex-setup.svg | 227 +++++++-------------- 3 files changed, 80 insertions(+), 328 deletions(-) delete mode 100644 docs/testing/user/userguide/images/nfvbench-spirent-setup.svg diff --git a/docs/testing/user/userguide/hw_requirements.rst b/docs/testing/user/userguide/hw_requirements.rst index acb4c0a..29fcd5c 100644 --- a/docs/testing/user/userguide/hw_requirements.rst +++ b/docs/testing/user/userguide/hw_requirements.rst @@ -25,9 +25,7 @@ To run the TRex traffic generator (that is bundled with NFVbench) you will need Switch Configuration -------------------- -For VLAN encapsulation, the 2 corresponding ports on the switch(es) facing the Trex ports on the Linux server should be configured in trunk mode (NFVbench will instruct TRex to insert the appropriate vlan tag). - -For VxLAN encapsulation, the switch(es) must support the VTEP feature (VxLAN Tunnel End Point) with the ability to attach an interface to a VTEP (this is an advanced feature that requires an NFVbench plugin for the switch). +The 2 corresponding ports on the switch(es) facing the Trex ports on the Linux server should be configured in trunk mode (NFVbench will instruct TRex to insert the appropriate vlan tag). Using a TOR switch is more representative of a real deployment and allows to measure packet flows on any compute node in the rack without rewiring and includes the overhead of the TOR switch. @@ -70,10 +68,3 @@ Finally, the correct iommu options and huge pages to be configured on the Linux - for Trex, pre-allocate 1024 huge pages of 2MB each (for a total of 2GB): "hugepagesz=2M hugepages=1024" More detailed instructions can be found in the DPDK documentation (https://media.readthedocs.org/pdf/dpdk/latest/dpdk.pdf). - - -NFVbench loopback VM image Upload ---------------------------------- - -The NFVbench loopback VM image should be uploaded to OpenStack prior to running NFVbench. -The NFVbench VM qcow2 image can be rebuilt from script or can be copied from the OPNFV artifact repository [URL TBP]. diff --git a/docs/testing/user/userguide/images/nfvbench-spirent-setup.svg b/docs/testing/user/userguide/images/nfvbench-spirent-setup.svg deleted file mode 100644 index e149fc0..0000000 --- a/docs/testing/user/userguide/images/nfvbench-spirent-setup.svg +++ /dev/null @@ -1,170 +0,0 @@ - - - - Produced by OmniGraffle 7.2.1 - 2016-12-03 22:53:19 +0000 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - nfvbench-spirent-setup - - Layer 1 - - - - Mercury Build Node - - - - - - - - - nfvbench - - - - - Compute node 1 - - - - - N9K TOR - - - - - T-rex - - - - - - Spirent - - - - - - Control Node - - - - - Storage - - - - - - Control Node - - - - - Control Node - - - - - Storage - - - - - Storage - - - - - Compute node i - - - - - N9K TOR - - - - - - - - - - Compute node N - - - - vPC - - - - 1 - - - - 2 - - - pull spirent test center - and nfvbench containers - - - - connect spirent to TOR - with 2 x 10G cables - - - - nfvbench/Spirent setup - - - - - Spirent - Test - Center - - - - - diff --git a/docs/testing/user/userguide/images/nfvbench-trex-setup.svg b/docs/testing/user/userguide/images/nfvbench-trex-setup.svg index 3f68006..a313916 100644 --- a/docs/testing/user/userguide/images/nfvbench-trex-setup.svg +++ b/docs/testing/user/userguide/images/nfvbench-trex-setup.svg @@ -1,43 +1,23 @@ - - Produced by OmniGraffle 7.2.2 - 2017-03-17 17:57:44 +0000 + + Produced by OmniGraffle 7.5 + 2017-11-04 10:05:35 +0000 - + - + - + - + - - - - - - - - - - - + - - - - - - - - - - - + @@ -45,125 +25,76 @@ nfvbench-trex-setup Layer 1 - - - - Mercury Build Node - - - - - - - nfvbench - - - - - Compute node 1 - - - - - N9K TOR - - - - - T-rex - - - - - - Intel - X710 - NIC - - - - - - Control Node - - - - - Storage - - - - - - Control Node - - - - - Control Node - - - - - Storage - - - - - Storage - - - - - Compute node i - - - - - N9K TOR - - - - - - - - - - Compute node N - - - - - vPC - - - - 1 - - - - 2 - - - - 3 - - - add Intel X710 NIC - - - - pull nfvbench container - - - - add a 10G cable - to each TOR - - - - nfvbench/T-rex setup + + + + + + Linux Server (x86_64) + + + + + NFVbench + + + + + Compute node 1 + + + + + In + t + el + X710 + NIC + + + + + + Controller/storage + nodes + + + + + TOR B + + + + + Compute node N + + + NFVi pod + + + + + + TOR A + + + + + + Layer 3 + + trunk mode + if only 1 T + OR s + wit + ch, c + onnect both link + s t + o same T + OR + + + 2x10G or higher ports -- cgit 1.2.3-korg