blob: 521d59a24472a6c1091e44c62587a026ab8cd681 (
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
|
# 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/port_mirroring.robot
| Resource | resources/libraries/robot/honeycomb/interfaces.robot
| Resource | resources/libraries/robot/honeycomb/honeycomb.robot
| Force Tags | honeycomb_sanity
| Suite Setup | Add Interface local0 To Topology | ${node}
| Suite Teardown | Run Keyword If Any Tests Failed
| | ... | Restart Honeycomb And VPP And Clear Persisted Configuration | ${node}
| Documentation | *Honeycomb port mirroring test suite.*
| ...
| ... | Test suite uses the first interface of the first DUT node.
*** Variables ***
| ${interface1}= | ${node['interfaces']['port1']['name']}
| ${interface2}= | ${node['interfaces']['port3']['name']}
| ${interface3}= | local0
*** Test Cases ***
# TODO: Add verification once operational data is available (HONEYCOMB-306)
| Honeycomb can configure SPAN on an interface
| | [Documentation] | Honeycomb configures SPAN on interface and verifies/
| | ... | against VPP SPAN dump.
| | Given SPAN configuration from VAT should not exist
| | ... | ${node}
| | When Honeycomb Configures SPAN on interface
| | ... | ${node} | ${interface1} | ${interface2}
| | Then Interface SPAN configuration from VAT should be
| | ... | ${node} | ${interface1} | ${interface2}
| Honeycomb can disable SPAN on interface
| | [Documentation] | Honeycomb removes existing SPAN configuration\
| | ... | on interface and verifies against VPP SPAN dump.
| | Given Interface SPAN configuration from VAT should be
| | ... | ${node} | ${interface1} | ${interface2}
| | When Honeycomb removes interface SPAN configuration
| | ... | ${node} | ${interface1}
| | Then SPAN configuration from VAT should not exist
| | ... | ${node}
| Honeycomb can configure SPAN on one interface to mirror two interfaces
| | [Documentation] | Honeycomb configures SPAN on interface, mirroring\
| | ... | two interfaces at the same time. Then verifies against VPP SPAN dump.
| | [Teardown] | Honeycomb removes interface SPAN configuration
| | ... | ${node} | ${interface1}
| | Given SPAN configuration from VAT should not exist
| | ... | ${node}
| | When Honeycomb Configures SPAN on interface
| | ... | ${node} | ${interface1} | ${interface2} | ${interface3}
| | Then Interface SPAN configuration from VAT should be
| | ... | ${node} | ${interface1} | ${interface2} | ${interface3}
|
