aboutsummaryrefslogtreecommitdiffstats
path: root/tests/func/honeycomb/mgmt-cfg-l2fib-apihc-apivat-func.robot
blob: 9a299df231024c367d9a3a8ab60729b241480f9e (plain)
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
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
# Copyright (c) 2016 Cisco and/or its affiliates.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at:
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

*** Settings ***
| Resource | resources/libraries/robot/default.robot
| Resource | resources/libraries/robot/honeycomb/honeycomb.robot
| Resource | resources/libraries/robot/honeycomb/interfaces.robot
| Resource | resources/libraries/robot/honeycomb/bridge_domain.robot
| Resource | resources/libraries/robot/honeycomb/l2_fib.robot
| Variables | resources/test_data/honeycomb/l2_fib.py | ${node} | ${interface}
| ... | ${interface2}
| Documentation | *Honeycomb L2 FIB management test suite.*
| Suite Setup | Run keywords
| ... | Set test interface down
| ... | AND
| ... | Honeycomb removes all bridge domains | ${node} | ${interface}
| Suite Teardown | Run keywords
| ... | Run Keyword If Any Tests Failed
| ... | Restart Honeycomb And VPP And Clear Persisted Configuration | ${node}
| ... | AND | Honeycomb removes all bridge domains | ${node}
| Force tags | honeycomb_sanity

*** Variables ***
# Interface to run tests on.
| ${interface}= | ${node['interfaces']['port1']['name']}
| ${interface2}= | ${node['interfaces']['port3']['name']}

*** Test Cases ***
| TC01: Honeycomb adds L2 FIB entry (forward)
| | [Documentation] | Honeycomb creates a bridge domain and assignes an \
| | ... | interface to it. Then adds an L2 FIB entry (forward) to the bridge \
| | ... | domain.
| | ...
| | [Teardown] | Honeycomb removes L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper['phys-address']}
| | ...
| | Given Interface state from Honeycomb should be
| | ... | ${node} | ${interface} | down
| | When Honeycomb sets interface state
| | ... | ${node} | ${interface} | up
| | Then Interface state from Honeycomb should be
| | ... | ${node} | ${interface} | up
| | When Honeycomb creates first l2 bridge domain
| | ... | ${node} | ${bd_name} | ${bd_settings}
| | Then Bridge domain configuration from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${bd_settings}
| | Given Bridge domain configuration in interface operational data should be empty
| | ... | ${node} | ${interface}
| | When Honeycomb adds interface to bridge domain
| | ... | ${node} | ${interface} | ${bd_name} | ${if_bd_settings}
| | Then Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | Given L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_forward_vat}

| TC02: Honeycomb adds L2 FIB entry (static, forward)
| | [Documentation] | Honeycomb adds an L2 FIB entry (static, forward) to the \
| | ... | bridge domain.
| | ...
| | [Teardown] | Honeycomb removes L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_static_forward_oper['phys-address']}
| | ...
| | Given Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | And L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_static_forward_cfg}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_static_forward_oper}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_static_forward_vat}

| TC03: Honeycomb adds L2 FIB entry (static, filter)
| | [Documentation] | Honeycomb adds an L2 FIB entry (static, filter) to the \
| | ... | bridge domain.
| | ...
| | [Teardown] | Honeycomb removes L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_filter_oper['phys-address']}
| | ...
| | Given Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | And L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_filter_cfg}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_filter_oper}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_filter_vat}

| TC04: Honeycomb adds and removes L2 FIB entry (forward)
| | [Documentation] | Honeycomb adds an L2 FIB entry (forward) to the bridge \
| | ... | domain and then Honeycomb removes it from the bridge domain.
| | ...
| | [Teardown] | Honeycomb removes L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper['phys-address']}
| | ...
| | Given Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | And L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_forward_vat}
| | When Honeycomb removes L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper['phys-address']}
| | Then L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}

| TC05: Honeycomb adds more than one L2 FIB entry
| | [Documentation] | Honeycomb adds three L2 FIB entries to the bridge domain.
| | ...
| | [Teardown] | Honeycomb removes all L2 FIB entries
| | ... | ${node} | ${bd_name}
| | ...
| | Given Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | And L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg}
| | And Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_static_forward_cfg}
| | And Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_filter_cfg}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper}
| | And L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_static_forward_oper}
| | And L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_filter_oper}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_forward_vat}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_static_forward_vat}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_filter_vat}

| TC06: Honeycomb fails to set wrong L2 FIB entry
| | [Documentation] | Honeycomb tries to add an L2 FIB entry with wrong \
| | ... | parameters to the bridge domain. It must fail.
| | ...
| | [Teardown] | Honeycomb removes all L2 FIB entries
| | ... | ${node} | ${bd_name}
| | ...
| | Given Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | And L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb fails to add wrong L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg_wrong_mac}
| | Then L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb fails to add wrong L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg_wrong_if}
| | Then L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb fails to add wrong L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg_wrong_action}
| | Then L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}

| TC07: Honeycomb fails to modify existing L2 FIB entry
| | [Documentation] | Honeycomb tries to modify an existing L2 FIB entry. It \
| | ... | must fail.
| | ...
| | [Teardown] | Honeycomb removes all L2 FIB entries
| | ... | ${node} | ${bd_name}
| | ...
| | Given Bridge domain configuration in interface operational data should be
| | ... | ${node} | ${interface} | ${if_bd_settings}
| | And L2 FIB Table from Honeycomb should be empty
| | ... | ${node} | ${bd_name}
| | And L2 FIB Table from VAT should be empty
| | ... | ${node} | ${bd_index}
| | When Honeycomb adds L2 FIB entry to bridge domain
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_cfg}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper}
| | When Honeycomb fails to modify L2 FIB entry
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper['phys-address']}
| | ... | outgoing-interface
| | ... | ${l2_fib_forward_modified_cfg['outgoing-interface']}
| | Then L2 FIB Entry from Honeycomb should be
| | ... | ${node} | ${bd_name} | ${l2_fib_forward_oper}
| | And L2 FIB entry from VAT should be
| | ... | ${node} | ${bd_index} | ${l2_fib_forward_vat}

*** Keywords ***
| Set test interface down
| | [Documentation] | Set the interface used in tests down.
| | ...
| | Honeycomb sets interface state
| | ... | ${node} | ${interface} | down