sfc_brahmaputra_testing
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
sfc_brahmaputra_testing [2015/11/30 16:45] Brady Johnson created |
sfc_brahmaputra_testing [2016/03/09 15:41] (current) Al Morton [Table] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| This wiki details the identified test cases for the OPNFV SFC Brahmaputra release. | This wiki details the identified test cases for the OPNFV SFC Brahmaputra release. | ||
| + | ===== Common testing setup ===== | ||
| + | |||
| + | Use the following slide for a logical overview of the testing scenario: | ||
| + | [[ https://docs.google.com/presentation/d/1gbhAnrTYbLCrNMhMXin0lxjyg-7IHNPjrlBTIjwAzys/edit#slide=id.gdd18a1c0d_38_0 | Logical Testing Overview ]] | ||
| + | |||
| + | - Create 2 Service Chains via Tacker: Chain1 and Chain2 | ||
| + | - Chain1 will only traverse SF1, which will block HTTP and allow everything else to pass | ||
| + | - Chain2 will only traverse SF2, which will block SSH and allow everything else to pass | ||
| + | - The 2 Service Functions (SF1 and SF2) will be created by Tacker | ||
| + | - Create the setup in the aforementioned slide with the following: | ||
| + | - 2 Client VMs, in the respective Group Based Policy End Point Groups, EpgClient1 and EpgClient2 (This is done by creating Security Groups in OpenStack, which GBP will map to EPGs) | ||
| + | - 1 Server VM in the Group Based Policy End Point Group, EpgServer | ||
| + | - Configure the GBP policy for EpgClient1 to EpgServer to be Chain1 | ||
| + | - Configure the GBP policy for EpgClient2 to EpgServer to be Chain2 | ||
| + | |||
| + | ===== Test Cases ===== | ||
| + | |||
| + | ==== Test Case: TC1 - VM Creation ==== | ||
| + | |||
| + | | Yardstick Id | Name | Description | Jira | | ||
| + | | TC029 | VM Creation | Verify that only 2 Service Function VMs are created for Service Chains Chain1 and Chain2 | https://jira.opnfv.org/browse/YARDSTICK-189 | | ||
| + | |||
| + | |||
| + | |||
| + | The Service Function VMs will be created by Tacker when the Service Chains Chain1 and Chain2 are created. This test verifies that the VMs are indeed created, but only 2. | ||
| + | |||
| + | ==== Test Case TC2 - Block HTTP ==== | ||
| + | |||
| + | | Yardstick Id | Name | Description | Jira | | ||
| + | | TC030 | Block HTTP | Verify that Client1 can not do HTTP traffic, but can do SSH traffic | https://jira.opnfv.org/browse/YARDSTICK-190 | | ||
| + | |||
| + | |||
| + | Client1 should be using Chain1, which will only send traffic through Service Function SF1 before sending the traffic on o the server. SF1 is a firewall configured to block all HTTP traffic, but let everything else pass through. | ||
| + | |||
| + | ==== Test Case TC3 - Block SSH ==== | ||
| + | |||
| + | | Yardstick Id | Name | Description | Jira | | ||
| + | | TC031 | Block SSH | Verify that Client2 can not do SSH traffic, but can do HTTP traffic | https://jira.opnfv.org/browse/YARDSTICK-191 | | ||
| + | |||
| + | |||
| + | Client2 should be using Chain2, which will only send traffic through Service Function SF2 before sending the traffic on o the server. SF2 is a firewall configured to block all SSH traffic, but let everything else pass through. | ||
sfc_brahmaputra_testing.1448901944.txt.gz · Last modified: 2015/11/30 16:45 by Brady Johnson
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
