tests/vpp/func/honeycomb/mgmt-cfg-nsh-apihc-apivat-func.robot

   1 # Copyright (c) 2016 Cisco and/or its affiliates.
   2 # Licensed under the Apache License, Version 2.0 (the "License");
   3 # you may not use this file except in compliance with the License.
   4 # You may obtain a copy of the License at:
   5 #
   6 #     http://www.apache.org/licenses/LICENSE-2.0
   7 #
   8 # Unless required by applicable law or agreed to in writing, software
   9 # distributed under the License is distributed on an "AS IS" BASIS,
  10 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  11 # See the License for the specific language governing permissions and
  12 # limitations under the License.
  13
  14 *** Variables***
  15 | ${super_if}= | ${node['interfaces']['port1']['name']}
  16
  17 *** Settings ***
  18 | Resource | resources/libraries/robot/shared/default.robot
  19 | Resource | resources/libraries/robot/honeycomb/nsh.robot
  20 | Resource | resources/libraries/robot/honeycomb/honeycomb.robot
  21 | Resource | resources/libraries/robot/honeycomb/vxlan_gpe.robot
  22 | Variables | resources/test_data/honeycomb/nsh.py
  23 | Variables | resources/test_data/honeycomb/vxlan_gpe.py
  24 | ...
  25 | Documentation | *Honeycomb NSH test suite.*
  26 | ...
  27 | Suite Setup | Run Keywords
  28 | ... | Enable Honeycomb Feature | ${node} | NSH | AND
  29 | ... | Set Up Honeycomb Functional Test Suite | ${node}
  30 | ...
  31 | Suite Teardown | Run Keywords
  32 | ... | Tear Down Honeycomb Functional Test Suite | ${node} | AND
  33 | ... | Disable Honeycomb Feature | ${node} | NSH
  34 | ...
  35 # NSHSFC-34: Having NSH plugin installed crashes VPP
  36 #| Force Tags | HC_FUNC
  37
  38
  39 *** Test Cases ***
  40 | TC01: Honeycomb can configure NSH entry
  41 | | [Documentation] | Check if Honeycomb can configure an NSH entry.
  42 | | ...
  43 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  44 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
  45 | | Then NSH entry from Honeycomb should be
  46 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  47
  48 | TC02: Honeycomb can remove NSH entry
  49 | | [Documentation] | Check if Honeycomb can remove an existing NSH entry.
  50 | | ...
  51 | | Given NSH entry from Honeycomb should be
  52 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  53 | | When Honeycomb removes NSH entry | ${node} | entry1
  54 | | Then NSH Operational Data From Honeycomb Should Be empty | ${node}
  55
  56 | TC03: Honeycomb can configure new NSH entry
  57 | | [Documentation] | Check if Honeycomb can configure an NSH antry after one\
  58 | | ... | has been deleted.
  59 | | ...
  60 | | [Teardown] | Honeycomb removes NSH entry | ${node} | entry2
  61 | | ...
  62 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  63 | | When Honeycomb adds NSH entry | ${node} | entry2 | ${nsh_entry2}
  64 | | Then NSH entry from Honeycomb should be
  65 | | ... | ${node} | entry2 | ${nsh_entry2_oper}
  66
  67 | TC04: Honeycomb can configure multiple NSH entries at the same time
  68 | | [Documentation] | Check if Honeycomb can configure an NSH entry when one\
  69 | | ... | already exists.
  70 | | ...
  71 | | [Teardown] | Honeycomb clears NSH configuration | ${node}
  72 | | ...
  73 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  74 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
  75 | | And Honeycomb adds NSH entry | ${node} | entry2 | ${nsh_entry2}
  76 | | Then NSH entry from Honeycomb should be
  77 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  78 | | And NSH entry from Honeycomb should be
  79 | | ... | ${node} | entry2 | ${nsh_entry2_oper}
  80
  81 | TC05: Honeycomb can configure NSH map
  82 | | [Documentation] | Check if Honeycomb can configure an NSH map.
  83 | | ...
  84 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  85 | | And Honeycomb creates VxLAN GPE interface
  86 | | ... | ${node} | ${vxlan_gpe_if1}
  87 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
  88 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
  89 | | And Honeycomb adds NSH map | ${node} | map1 | ${nsh_map1}
  90 | | Then NSH map from Honeycomb should be | ${node} | map1 | ${nsh_map1_oper}
  91
  92 | TC06: Honeycomb can remove NSH map
  93 | | [Documentation] | Check if Honeycomb can remove an existing NSH map.
  94 | | ...
  95 | | Given NSH entry from Honeycomb should be
  96 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  97 | | And VxLAN GPE Operational Data From Honeycomb Should Be
  98 | | ... | ${node} | ${vxlan_gpe_if1}
  99 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
 100 | | And NSH map from Honeycomb should be | ${node} | map1 | ${nsh_map1_oper}
 101 | | When Honeycomb removes NSH map | ${node} | map1
 102 | | Then NSH map from Honeycomb should not exist | ${node} | map1
 103 | | And NSH entry from Honeycomb should be
 104 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 105
 106 | TC07: Honeycomb can modify existing NSH map
 107 | | [Documentation] | Check if Honeycomb can configure an NSH map after one\
 108 | | ... | has been deleted.
 109 | | ...
 110 | | [Teardown] | Honeycomb removes NSH map | ${node} | map1_edit
 111 | | ...
 112 | | Given NSH map from Honeycomb should not exist | ${node} | map1_edit
 113 | | And NSH entry from Honeycomb should be
 114 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 115 | | And VxLAN GPE Operational Data From Honeycomb Should Be
 116 | | ... | ${node} | ${vxlan_gpe_if1}
 117 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
 118 | | When Honeycomb adds NSH map | ${node} | map1_edit | ${nsh_map1_edit}
 119 | | Then NSH map from Honeycomb should be
 120 | | ... | ${node} | map1_edit | ${nsh_map1_edit_oper}
 121 | | And NSH entry from Honeycomb should be
 122 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 123
 124 | TC08: Honeycomb can configure multiple NSH maps at the same time
 125 | | [Documentation] | Check if Honeycomb can configure and NSH map when one\
 126 | | ... | already exists.
 127 | | ...
 128 | | [Teardown] | Run Keywords
 129 | | ... | Honeycomb clears NSH configuration | ${node} | AND
 130 | | ... | Honeycomb removes VxLAN GPE interface
 131 | | ... | ${node} | ${vxlan_gpe_if1} | AND
 132 | | ... | Honeycomb removes VxLAN GPE interface
 133 | | ... | ${node} | ${vxlan_gpe_if2}
 134 | | ...
 135 | | Given NSH map from Honeycomb should not exist | ${node} | map2
 136 | | And NSH entry from Honeycomb should be
 137 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 138 | | And VxLAN GPE Operational Data From Honeycomb Should Be
 139 | | ... | ${node} | ${vxlan_gpe_if1}
 140 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
 141 | | And Honeycomb creates VxLAN GPE interface
 142 | | ... | ${node} | ${vxlan_gpe_if2}
 143 | | ... | ${vxlan_gpe_base_settings2} | ${vxlan_gpe_settings2}
 144 | | When Honeycomb adds NSH map | ${node} | map1 | ${nsh_map1}
 145 | | And Honeycomb adds NSH map | ${node} | map2 | ${nsh_map2}
 146 | | Then NSH map from Honeycomb should be
 147 | | ... | ${node} | map1 | ${nsh_map1_oper}
 148 | | And NSH map from Honeycomb should be
 149 | | ... | ${node} | map2 | ${nsh_map2_oper}