tests/func/honeycomb/090_provider_backbone_bridge.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/honeycomb/provider_backbone_bridge.robot
  19 | Variables | resources/test_data/honeycomb/pbb/pbb.py
  20 | Documentation | *Honeycomb provider backbone bridge test suite.*
  21 | Suite Teardown | Run Keyword If Any Tests Failed
  22 | ... | Restart Honeycomb And VPP And Clear Persisted Configuration | ${node}
  23 | Force Tags | honeycomb_sanity
  24
  25 *** Test Cases ***
  26 | TC01: Honeycomb sets PBB sub-interface
  27 | | [Documentation] | Honeycomb creates a new PBB sub-interface and checks its\
  28 | | ... | operational data.
  29 | | ...
  30 | | Given PBB sub interface operational data from Honeycomb should be empty
  31 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID}
  32 | | When Honeycomb creates PBB sub interface | ${node} | ${super_if}
  33 | | ... | ${cfg_pbb_sub_if_1_ID} | ${cfg_pbb_sub_if_1}
  34 | | Then PBB sub interface operational data from Honeycomb should be
  35 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} | ${oper_pbb_sub_if_1}
  36
  37 | TC02: Honeycomb modifies existing PBB sub-interface
  38 | | [Documentation] | Honeycomb modifies an existing PBB sub-interface and\
  39 | | ... | checks its operational data.
  40 | | ...
  41 | | Given PBB sub interface operational data from Honeycomb should be
  42 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID} | ${oper_pbb_sub_if_1}
  43 | | When Honeycomb creates PBB sub interface | ${node} | ${super_if}
  44 | | ... | ${cfg_pbb_sub_if_1_ID} | ${cfg_pbb_sub_if_1_mod}
  45 | | Then PBB sub interface operational data from Honeycomb should be
  46 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID}
  47 | | ... | ${oper_pbb_sub_if_1_mod}
  48
  49 | TC03: Honeycomb deletes existing PBB sub-interface
  50 | | [Documentation] | Honeycomb deletes an existing PBB sub-interface and\
  51 | | ... | checks operational data.
  52 | | ...
  53 | | Given PBB sub interface operational data from Honeycomb should be
  54 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID}
  55 | | ... | ${oper_pbb_sub_if_1_mod}
  56 | | When Honeycomb Removes PBB sub interface
  57 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID}
  58 | | Given PBB sub interface operational data from Honeycomb should be empty
  59 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_1_ID}
  60
  61 | TC04: Honeycomb creates two PBB sub-interface
  62 | | [Documentation] | Honeycomb creates two PBB sub-interfaces on the same\
  63 | | ... | super interface and checks their operational data.
  64 | | ...
  65 | | Given PBB sub interface operational data from Honeycomb should be empty
  66 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_2_ID}
  67 | | And PBB sub interface operational data from Honeycomb should be empty
  68 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_3_ID}
  69 | | When Honeycomb creates PBB sub interface | ${node} | ${super_if}
  70 | | ... | ${cfg_pbb_sub_if_2_ID} | ${cfg_pbb_sub_if_2}
  71 | | And Honeycomb creates PBB sub interface | ${node} | ${super_if}
  72 | | ... | ${cfg_pbb_sub_if_3_ID} | ${cfg_pbb_sub_if_3}
  73 | | Then PBB sub interface operational data from Honeycomb should be
  74 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_2_ID} | ${oper_pbb_sub_if_2}
  75 | | And PBB sub interface operational data from Honeycomb should be
  76 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_3_ID} | ${oper_pbb_sub_if_3}
  77
  78 | TC05: Honeycomb fails to set wrong destination-address for new PBB sub-interface
  79 | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\
  80 | | ... | wrong value of parameter destination-address, type yang:mac-address.
  81 | | ...
  82 | | Given PBB sub interface operational data from Honeycomb should be empty
  83 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
  84 | | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if}
  85 | | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_dst_addr}
  86 | | Then PBB sub interface operational data from Honeycomb should be empty
  87 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
  88
  89 | TC06: Honeycomb fails to set wrong source-address for new PBB sub-interface
  90 | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\
  91 | | ... | wrong value of parameter source-address, type yang:mac-address.
  92 | | ...
  93 | | Given PBB sub interface operational data from Honeycomb should be empty
  94 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
  95 | | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if}
  96 | | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_src_addr}
  97 | | Then PBB sub interface operational data from Honeycomb should be empty
  98 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
  99
 100 | TC07: Honeycomb fails to set wrong b-vlan-tag-vlan-id for new PBB sub-interface
 101 | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\
 102 | | ... | wrong value of parameter b-vlan-tag-vlan-id, type uint16, 12 bit\
 103 | | ... | range, range "1..4095".
 104 | | ...
 105 | | Given PBB sub interface operational data from Honeycomb should be empty
 106 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
 107 | | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if}
 108 | | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_vlan_tag}
 109 | | Then PBB sub interface operational data from Honeycomb should be empty
 110 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
 111
 112 | TC08: Honeycomb fails to set wrong i-tag-isid for new PBB sub-interface
 113 | | [Documentation] | Honeycomb fails to create a new PBB sub-interface with\
 114 | | ... | wrong value of parameter i-tag-isid, type uint32, 24 bit range,\
 115 | | ... | range "1..16777215".
 116 | | ...
 117 | | Given PBB sub interface operational data from Honeycomb should be empty
 118 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
 119 | | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if}
 120 | | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_wrong_i_tag}
 121 | | Then PBB sub interface operational data from Honeycomb should be empty
 122 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
 123
 124 | TC07: Honeycomb fails to create new PBB sub-interface without vlan tag
 125 | | [Documentation] | Honeycomb fails to create a new PBB sub-interface without\
 126 | | ... | parameter b-vlan-tag-vlan-id.
 127 | | ...
 128 | | Given PBB sub interface operational data from Honeycomb should be empty
 129 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}
 130 | | When Honeycomb fails to create PBB sub interface | ${node} | ${super_if}
 131 | | ... | ${cfg_pbb_sub_if_ID} | ${cfg_pbb_sub_if_no_vlan_tag}
 132 | | Then PBB sub interface operational data from Honeycomb should be empty
 133 | | ... | ${node} | ${super_if} | ${cfg_pbb_sub_if_ID}