tests/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/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 Teardown | Run Keyword If Any Tests Failed
  28 | ... | Restart Honeycomb and VPP | ${node}
  29 # disabled pending NSH version 17.04
  30 #| Force Tags | honeycomb_sanity | honeycomb_odl
  31
  32 *** Test Cases ***
  33 | TC01: Honeycomb can configure NSH entry
  34 | | [Documentation] | Check if Honeycomb can configure an NSH entry.
  35 | | ...
  36 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  37 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
  38 | | Then NSH entry from Honeycomb should be
  39 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  40
  41 | TC02: Honeycomb can remove NSH entry
  42 | | [Documentation] | Check if Honeycomb can remove an existing NSH entry.
  43 | | ...
  44 | | Given NSH entry from Honeycomb should be
  45 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  46 | | When Honeycomb removes NSH entry | ${node} | entry1
  47 | | Then NSH Operational Data From Honeycomb Should Be empty | ${node}
  48
  49 | TC03: Honeycomb can configure new NSH entry
  50 | | [Documentation] | Check if Honeycomb can configure an NSH antry after one\
  51 | | ... | has been deleted.
  52 | | ...
  53 | | [Teardown] | Honeycomb removes NSH entry | ${node} | entry2
  54 | | ...
  55 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  56 | | When Honeycomb adds NSH entry | ${node} | entry2 | ${nsh_entry2}
  57 | | Then NSH entry from Honeycomb should be
  58 | | ... | ${node} | entry2 | ${nsh_entry2_oper}
  59
  60 | TC04: Honeycomb can configure multiple NSH entries at the same time
  61 | | [Documentation] | Check if Honeycomb can configure an NSH entry when one\
  62 | | ... | already exists.
  63 | | ...
  64 | | [Teardown] | Honeycomb clears NSH configuration | ${node}
  65 | | ...
  66 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  67 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
  68 | | And Honeycomb adds NSH entry | ${node} | entry2 | ${nsh_entry2}
  69 | | Then NSH entry from Honeycomb should be
  70 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  71 | | And NSH entry from Honeycomb should be
  72 | | ... | ${node} | entry2 | ${nsh_entry2_oper}
  73
  74 | TC05: Honeycomb can configure NSH map
  75 | | [Documentation] | Check if Honeycomb can configure an NSH map.
  76 | | ...
  77 | | Given NSH Operational Data From Honeycomb Should Be empty | ${node}
  78 | | And Honeycomb creates VxLAN GPE interface
  79 | | ... | ${node} | ${vxlan_gpe_if1}
  80 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
  81 | | When Honeycomb adds NSH entry | ${node} | entry1 | ${nsh_entry1}
  82 | | And Honeycomb adds NSH map | ${node} | map1 | ${nsh_map1}
  83 | | Then NSH map from Honeycomb should be | ${node} | map1 | ${nsh_map1_oper}
  84
  85 | TC06: Honeycomb can remove NSH map
  86 | | [Documentation] | Check if Honeycomb can remove an existing NSH map.
  87 | | ...
  88 | | Given NSH entry from Honeycomb should be
  89 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  90 | | And VxLAN GPE Operational Data From Honeycomb Should Be
  91 | | ... | ${node} | ${vxlan_gpe_if1}
  92 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
  93 | | And NSH map from Honeycomb should be | ${node} | map1 | ${nsh_map1_oper}
  94 | | When Honeycomb removes NSH map | ${node} | map1
  95 | | Then NSH map from Honeycomb should not exist | ${node} | map1
  96 | | And NSH entry from Honeycomb should be
  97 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
  98
  99 | TC07: Honeycomb can modify existing NSH map
 100 | | [Documentation] | Check if Honeycomb can configure an NSH map after one\
 101 | | ... | has been deleted.
 102 | | ...
 103 | | [Teardown] | Honeycomb removes NSH map | ${node} | map1_edit
 104 | | ...
 105 | | Given NSH map from Honeycomb should not exist | ${node} | map1_edit
 106 | | And NSH entry from Honeycomb should be
 107 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 108 | | And VxLAN GPE Operational Data From Honeycomb Should Be
 109 | | ... | ${node} | ${vxlan_gpe_if1}
 110 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
 111 | | When Honeycomb adds NSH map | ${node} | map1_edit | ${nsh_map1_edit}
 112 | | Then NSH map from Honeycomb should be
 113 | | ... | ${node} | map1_edit | ${nsh_map1_edit_oper}
 114 | | And NSH entry from Honeycomb should be
 115 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 116
 117 | TC08: Honeycomb can configure multiple NSH maps at the same time
 118 | | [Documentation] | Check if Honeycomb can configure and NSH map when one\
 119 | | ... | already exists.
 120 | | ...
 121 | | [Teardown] | Run Keywords
 122 | | ... | Honeycomb clears NSH configuration | ${node} | AND
 123 | | ... | Honeycomb removes VxLAN GPE interface
 124 | | ... | ${node} | ${vxlan_gpe_if1} | AND
 125 | | ... | Honeycomb removes VxLAN GPE interface
 126 | | ... | ${node} | ${vxlan_gpe_if2}
 127 | | ...
 128 | | Given NSH map from Honeycomb should not exist | ${node} | map2
 129 | | And NSH entry from Honeycomb should be
 130 | | ... | ${node} | entry1 | ${nsh_entry1_oper}
 131 | | And VxLAN GPE Operational Data From Honeycomb Should Be
 132 | | ... | ${node} | ${vxlan_gpe_if1}
 133 | | ... | ${vxlan_gpe_base_settings1} | ${vxlan_gpe_settings1}
 134 | | And Honeycomb creates VxLAN GPE interface
 135 | | ... | ${node} | ${vxlan_gpe_if2}
 136 | | ... | ${vxlan_gpe_base_settings2} | ${vxlan_gpe_settings2}
 137 | | When Honeycomb adds NSH map | ${node} | map1 | ${nsh_map1}
 138 | | And Honeycomb adds NSH map | ${node} | map2 | ${nsh_map2}
 139 | | Then NSH map from Honeycomb should be
 140 | | ... | ${node} | map1 | ${nsh_map1_oper}
 141 | | And NSH map from Honeycomb should be
 142 | | ... | ${node} | map2 | ${nsh_map2_oper}