1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) Huawei Technologies Co.,Ltd
==================================================
Forwarding Packets in Data Path test specification
==================================================
.. toctree::
:maxdepth: 2
Scope
=====
This test area evaluates the ability of the system under test to support basic packet forwarding.
The test in this test area will evaluate basic packet forwarding through virtual IPv4 networks
in data path, including creating server and verifying network connectivity to the created server
with ping operation using MTU sized packets.
References
==========
N/A
Definitions and abbreviations
=============================
The following terms and abbreviations are used in conjunction with this test
area
- API - Application Programming Interface
- ICMP - Internet Control Message Protocol
- MTU - Maximum Transmission Unit
- NFVi - Network Functions Virtualization infrastructure
- SSH - Secure Shell
- VIM - Virtual Infrastructure Manager
- VM - Virtual Machine
System Under Test (SUT)
=======================
The system under test is assumed to be the NFVi and VIM in operation on a
Pharos compliant infrastructure.
Test Area Structure
===================
The test area is structured based on the basic operations of forwarding packets
in data path through virtual networks. Specifically, the test performs
clean-up operations which return the system to the same state as before the test.
This test case is included in the test case dovetail.tempest.tc001 of OVP test suite.
Test Descriptions
=================
API Used and Reference
----------------------
Security Groups: https://developer.openstack.org/api-ref/network/v2/index.html#security-groups-security-groups
- create security group
- delete security group
Networks: https://developer.openstack.org/api-ref/networking/v2/index.html#networks
- create network
- delete network
Routers and interface: https://developer.openstack.org/api-ref/networking/v2/index.html#routers-routers
- create router
- delete router
- add interface to router
Subnets: https://developer.openstack.org/api-ref/networking/v2/index.html#subnets
- create subnet
- delete subnet
Servers: https://developer.openstack.org/api-ref/compute/
- create keypair
- create server
- delete server
- add/assign floating ip
Ports: https://developer.openstack.org/api-ref/networking/v2/index.html#ports
- create port
- delete port
Floating IPs: https://developer.openstack.org/api-ref/networking/v2/index.html#floating-ips-floatingips
- create floating ip
- delete floating ip
----------------------------
MTU Sized Frames Fit Through
----------------------------
Test case specification
-----------------------
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_mtu_sized_frames
Test preconditions
------------------
* Nova has been configured to boot VMs with Neutron-managed networking
* Neutron net-mtu extension API
* One public network
Basic test flow execution description and pass/fail criteria
------------------------------------------------------------
Test execution
''''''''''''''
* Test action 1: Create a security group SG1, which has rules for allowing
incoming and outgoing SSH and ICMP traffic
* Test action 2: Create a neutron network NET1
* Test action 3: Create a tenant router R1 which routes traffic to public network
* Test action 4: Create a subnet SUBNET1 and add it as router interface
* Test action 5: Create a server VM1 with SG1 and NET1, and assign a floating
ip FIP1 (via R1) to VM1
* Test action 6: Set MTU size to be the default MTU size of the SUT's network
* Test action 7: Host sends MTU sized ICMP packets to VM1 using ``ping``
* **Test assertion 1:** Ping FIP1 using MTU sized packets successfully
* Test action 8: SSH to VM1 with FIP1
* **Test assertion 2:** SSH to VM1 with FIP1 successfully
* Test action 9: Delete SG1, NET1, SUBNET1, R1, VM1 and FIP1
Pass / fail criteria
''''''''''''''''''''
This test evaluates the network connectivity using MTU sized frames.
Specifically, the test verifies that:
* With Neutron net-mtu extension configured, MTU sized packets can fit through network.
In order to pass this test, all test assertions listed in the test execution above need to pass.
Post conditions
---------------
N/A
|
