diff options
author | Juan Vidal <juan.vidal.allende@ericsson.com> | 2017-02-13 14:32:04 +0000 |
---|---|---|
committer | Brady Johnson <brady.allen.johnson@ericsson.com> | 2017-02-17 15:40:39 +0000 |
commit | 72b6571f2b448e27a1d8c50dd8f27e564004d687 (patch) | |
tree | a965201a58eb14bdd36f2aea135686adef1f05c6 /sfc/tests/functest/README.sfc-test-3 | |
parent | 75ac61401c83253d533983de6e2650f82fc4c427 (diff) |
Introduce new test case: symmetric service chain
JIRA: SFC-53
The goal is to verify that the traffic traverses the service chain, not only
in the uplink (client --> server) direction, but also in the downlink
(client <-- server) direction, which is the part that is not currently being
covered by other test cases.
Change-Id: I198a53e5afe3da1b397cee95627834856498b674
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
Diffstat (limited to 'sfc/tests/functest/README.sfc-test-3')
-rw-r--r-- | sfc/tests/functest/README.sfc-test-3 | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/sfc/tests/functest/README.sfc-test-3 b/sfc/tests/functest/README.sfc-test-3 new file mode 100644 index 00000000..865a7cc8 --- /dev/null +++ b/sfc/tests/functest/README.sfc-test-3 @@ -0,0 +1,22 @@ +### ODL-SFC TEST3 DESCRIPTION ### + +One client and one server are created using nova. The server will be running +a web server on port 80. + +Then one Service Function (SF) is created using Tacker. This service function +will be running a firewall that blocks the traffic in a specific port (e.g. +33333). A symmetric service chain routing the traffic throught this SF will be +created as well. + +1st check: The client is able to reach the server using a source port different +from the one that the firewall blocks (e.g 22222), and the response gets back +to the client. + +2nd check: The client is able to reach the server using the source port that +the firewall blocks, but responses back from the server are blocked, as the +symmetric service chain makes them go through the firewall that blocks on the +destination port initially used as source port by the client (e.g. 33333). + +If the client is able to receive the response, it would be a symptom of the +symmetric chain not working, as traffic would be flowing from server to client +directly without traversing the SF. |