CSIT-744 Update report content for proper parsing
[csit.git] / docs / report / nsh_sfc_functional_tests / overview.rst
1 Overview\r
2 ========\r
3 \r
4 Tested Virtual Topologies\r
5 -------------------------\r
6 \r
7 CSIT NSH_SFC functional tests are executed on virtualized topologies created using\r
8 :abbr:`VIRL (Virtual Internet Routing Lab)` simulation platform contributed by\r
9 Cisco. VIRL runs on physical baremetal servers hosted by LF FD.io project.\r
10 Majority of the tests are executed in the three node logical test topology -\r
11 Traffic Generator (TG) node and two Systems Under Test (SUT) nodes connected in\r
12 a loop. Some tests use two node logical test topology - TG node and SUT1 node.\r
13 Both logical test topologies are shown in the figures below.::\r
14 \r
15     +------------------------+           +------------------------+\r
16     |                        |           |                        |\r
17     |  +------------------+  |           |  +------------------+  |\r
18     |  |                  <----------------->                  |  |\r
19     |  |                  |  |           |  |                  |  |\r
20     |  |       DUT1       <----------------->       DUT2       |  |\r
21     |  +--^--^------------+  |           |  +------------^--^--+  |\r
22     |     |  |               |           |               |  |     |\r
23     |     |  |         SUT1  |           |  SUT2         |  |     |\r
24     +------------------------+           +------------------------+\r
25           |  |                                           |  |\r
26           |  |                                           |  |\r
27           |  |               +-----------+               |  |\r
28           |  +--------------->           <---------------+  |\r
29           |                  |    TG     |                  |\r
30           +------------------>           <------------------+\r
31                              +-----------+\r
32 \r
33                        +------------------------+\r
34                        |                        |\r
35                        |  +------------------+  |\r
36           +--------------->                  <--------------+\r
37           |            |  |                  |  |           |\r
38           |  |------------>       DUT1       <-----------+  |\r
39           |  |         |  +------------------+  |        |  |\r
40           |  |         |                        |        |  |\r
41           |  |         |                  SUT1  |        |  |\r
42           |  |         +------------------------+        |  |\r
43           |  |                                           |  |\r
44           |  |                                           |  |\r
45           |  |               +-----------+               |  |\r
46           |  +--------------->           <---------------+  |\r
47           |                  |    TG     |                  |\r
48           +------------------>           <------------------+\r
49                              +-----------+\r
50 \r
51 SUT1 and SUT2 are two VMs (Ubuntu or Centos, depending on the test suite), TG\r
52 is a Traffic Generator (TG, another Ubuntu VM). SUTs run VPP SW application in\r
53 Linux user-mode as a Device Under Test (DUT) within the VM. TG runs Scapy SW\r
54 application as a packet Traffic Generator. Logical connectivity between SUTs\r
55 and to TG is provided using virtual NICs using VMs' virtio driver.\r
56 \r
57 Virtual testbeds are created on-demand whenever a verification job is started\r
58 (e.g. triggered by the gerrit patch submission) and destroyed upon completion\r
59 of all functional tests. Each node is a Virtual Machine and each connection\r
60 that is drawn on the diagram is available for use in any test case. During the\r
61 test execution, all nodes are reachable thru the Management network connected\r
62 to every node via dedicated virtual NICs and virtual links (not shown above\r
63 for clarity).\r
64 \r
65 For the test cases that require DUT (VPP) to communicate with VM over the\r
66 vhost-user interfaces, a nested VM is created on SUT1 and/or SUT2 for the\r
67 duration of these particular test cases only. DUT (VPP) test topology with VM\r
68 is shown in the figure below including the applicable packet flow thru the VM\r
69 (marked in the figure with ``***``).::\r
70 \r
71     +------------------------+           +------------------------+\r
72     |      +----------+      |           |      +----------+      |\r
73     |      |    VM    |      |           |      |    VM    |      |\r
74     |      |  ******  |      |           |      |  ******  |      |\r
75     |      +--^----^--+      |           |      +--^----^--+      |\r
76     |        *|    |*        |           |        *|    |*        |\r
77     |  +------v----v------+  |           |  +------v----v------+  |\r
78     |  |      *    *      |**|***********|**|      *    *      |  |\r
79     |  |  *****    *******<----------------->*******    *****  |  |\r
80     |  |  *    DUT1       |  |           |  |       DUT2    *  |  |\r
81     |  +--^---------------+  |           |  +---------------^--+  |\r
82     |    *|                  |           |                  |*    |\r
83     |    *|            SUT1  |           |  SUT2            |*    |\r
84     +------------------------+           +------------------^-----+\r
85          *|                                                 |*\r
86          *|                                                 |*\r
87          *|                  +-----------+                  |*\r
88          *|                  |           |                  |*\r
89          *+------------------>    TG     <------------------+*\r
90          ******************* |           |********************\r
91                              +-----------+\r
92 \r
93 NSH_SFC Functional Tests Coverage\r
94 ---------------------------------\r
95 \r
96 Following NSH_SFC functional test areas are covered in the CSIT |release| with\r
97 results listed in this report:\r
98 \r
99 - **NSH SFC Classifier** - TG sends some TCP packets to test NSH SFC\r
100   Classifier functional. DUT1 will receive these packets from one NIC and loopback\r
101   the VXLAN-GPE-NSH encapsulated packets to the TG from other NIC.\r
102   - Test case count: 7\r
103 - **NSH SFC Proxy Inbound** - TG sends some VXLAN-GPE-NSH encapsulated packets\r
104   to test NSH SFC Proxy Inbound functional. DUT1 will receive these packets from one\r
105   NIC and loopback the VXLAN encapsulated packets to the TG from other NIC.\r
106   - Test case count: 6\r
107 - **NSH SFC Proxy Outbound** - TG sends some VXLAN encapsulated packets to test\r
108   NSH SFC Proxy Outbound functional. DUT1 will receive these packets from one NIC\r
109   and loopback the VXLAN-GPE-NSH encapsulated packets to the TG from other NIC.\r
110   - Test case count: 6\r
111 - **NSH SFC Service Function Forward** - TG sends some VXLAN-GPE-NSH encapsulated\r
112   packets to test NSH SFC Service Function Forward functional. DUT1 will receive these\r
113   packets from one NIC and swap the VXLAN-GPE-NSH header, after that DUT1 loopback the\r
114   VXLAN-GPE-NSH encapsulated packtes to the TG from other NIC.\r
115   - Test case count: 6\r
116 \r
117 Total 25 NSH SFC functional tests in the CSIT |release|.\r
118 \r

©2016 FD.io a Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation. Linux is a registered trademark of Linus Torvalds.
Please see our privacy policy and terms of use.