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

   1 # Copyright (c) 2017 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 # Interface to run tests on.
  16 | ${interface}= | ${node['interfaces']['port1']['name']}
  17
  18 *** Settings ***
  19 | Resource | resources/libraries/robot/shared/default.robot
  20 | Resource | resources/libraries/robot/honeycomb/honeycomb.robot
  21 | Resource | resources/libraries/robot/honeycomb/interfaces.robot
  22 | Resource | resources/libraries/robot/honeycomb/bgp.robot
  23 | Resource | resources/libraries/robot/honeycomb/routing.robot
  24 | Variables | resources/test_data/honeycomb/bgp.py
  25 | ...
  26 | Suite Setup | Run Keywords
  27 | ... | Enable Honeycomb Feature | ${node} | BGP | AND
  28 | ... | Set Up Honeycomb Functional Test Suite | ${node}
  29 | ...
  30 | Suite Teardown | Run Keywords
  31 | ... | Tear Down Honeycomb Functional Test Suite | ${node} | AND
  32 | ... | Disable Honeycomb Feature | ${node} | BGP
  33 | ...
  34 | Force Tags | HC_FUNC
  35 | ...
  36 | Documentation | *Honeycomb BGP management test suite.*
  37
  38 *** Test Cases ***
  39 | TC01: Honeycomb configures BGP peer - Internal
  40 | | [Documentation] | Check if Honeycomb can configure an internal BGP peer.
  41 | | ...
  42 | | When Honeycomb adds BGP peer
  43 | | ... | ${node} | ${address_internal} | ${peer_internal}
  44 | | Then BGP peer from Honeycomb should be
  45 | | ... | ${node} | ${address_internal} | ${peer_internal}
  46
  47 | TC03: Honeycomb removes peer configuration
  48 | | [Documentation] | Check if Honeycomb can remove a configured BGP peer.
  49 | | ...
  50 | | Given BGP peer from Honeycomb should be
  51 | | ... | ${node} | ${address_internal} | ${peer_internal}
  52 | | When Honeycomb removes BGP peer | ${node} | ${address_internal}
  53 | | Then No BGP peers should be configured | ${node}
  54
  55 | TC02: Honeycomb updates existing BGP peer - Internal
  56 | | [Documentation] | Check if Honeycomb can update an existing BGP peer.
  57 | | ...
  58 | | [Teardown] | Honeycomb removes BGP peer | ${node} | ${address_internal}
  59 | | ...
  60 | | Given No BGP peers should be configured | ${node}
  61 | | When Honeycomb adds BGP peer
  62 | | ... | ${node} | ${address_internal} | ${peer_internal}
  63 | | And Honeycomb adds BGP peer
  64 | | ... | ${node} | ${address_internal} | ${peer_internal_update}
  65 | | Then BGP peer from Honeycomb should be
  66 | | ... | ${node} | ${address_internal} | ${peer_internal_update}
  67
  68 | TC04: Honeycomb configures BGP peer - Application
  69 | | [Documentation] | Check if Honeycomb can configure an application BGP peer.
  70 | | ...
  71 | | [Teardown] | Honeycomb removes BGP peer | ${node} | ${address_application}
  72 | | ...
  73 | | Given No BGP peers should be configured | ${node}
  74 | | When Honeycomb adds BGP peer
  75 | | ... | ${node} | ${address_application} | ${peer_application}
  76 | | Then BGP peer from Honeycomb should be
  77 | | ... | ${node} | ${address_application} | ${peer_application}
  78
  79 | TC05: Honeycomb configures a second BGP peer
  80 | | [Documentation] | Check if Honeycomb can configure more than one BGP peer.
  81 | | ...
  82 | | [Teardown] | Run Keywords
  83 | | ... | Honeycomb removes BGP peer | ${node} | ${address_internal} | AND
  84 | | ... | Honeycomb removes BGP peer | ${node} | ${address_internal2}
  85 | | ...
  86 | | Given No BGP peers should be configured | ${node}
  87 | | When Honeycomb adds BGP peer
  88 | | ... | ${node} | ${address_internal} | ${peer_internal}
  89 | | And Honeycomb adds BGP peer
  90 | | ... | ${node} | ${address_internal2} | ${peer_internal2}
  91 | | Then BGP peer from Honeycomb should be
  92 | | ... | ${node} | ${address_internal} | ${peer_internal}
  93 | | And BGP peer from Honeycomb should be
  94 | | ... | ${node} | ${address_internal2} | ${peer_internal2}
  95
  96 | TC06: Honeycomb configures IPv4 route using BGP
  97 | | [Documentation] | Check if Honeycomb can configure a BGP route under a peer.
  98 | | ...
  99 | | Given Honeycomb adds BGP peer
 100 | | ... | ${node} | ${address_internal} | ${peer_internal}
 101 | | When Honeycomb configures BGP route
 102 | | ... | ${node} | ${address_internal} | ${route_data_ipv4}
 103 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 104 | | Then BGP Route from Honeycomb should be
 105 | | ... | ${node} | ${address_internal} | ${route_data_ipv4}
 106 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 107
 108 | TC08: Honeycomb removes IPv4 route configuration
 109 | | [Documentation] | Check if Honeycomb can remove a configured BGP route.
 110 | | ...
 111 | | Given BGP peer from Honeycomb should be
 112 | | ... | ${node} | ${address_internal} | ${peer_internal}
 113 | | And BGP Route from Honeycomb should be
 114 | | ... | ${node} | ${address_internal} | ${route_data_ipv4}
 115 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 116 | | When Honeycomb removes BGP route | ${node} | ${address_internal}
 117 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 118 | | Then No BGP Routes Should be Configured
 119 | | ... | ${node} | ${address_internal} | ipv4
 120
 121 | TC07: Honeycomb updates existing IPv4 route using BGP
 122 | | [Documentation] | Check if Honeycomb can update an existing BGP route.
 123 | | ...
 124 | | [Teardown] | Honeycomb removes BGP route | ${node} | ${address_internal}
 125 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 126 | | ...
 127 | | Given BGP peer from Honeycomb should be
 128 | | ... | ${node} | ${address_internal} | ${peer_internal}
 129 | | And No BGP Routes Should be Configured
 130 | | ... | ${node} | ${address_internal} | ipv4
 131 | | When Honeycomb configures BGP route
 132 | | ... | ${node} | ${address_internal} | ${route_data_ipv4}
 133 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 134 | | And Honeycomb configures BGP route
 135 | | ... | ${node} | ${address_internal} | ${route_data_ipv4_update}
 136 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 137 | | Then BGP Route from Honeycomb should be
 138 | | ... | ${node} | ${address_internal} | ${route_data_ipv4_update}
 139 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 140
 141 | TC09: Honeycomb configures a second IPv4 route
 142 | | [Documentation] | Check if Honeycomb can configure more than one BGP route.
 143 | | ...
 144 | | [Teardown] | Run Keywords
 145 | | ... | Honeycomb removes BGP route | ${node} | ${address_internal}
 146 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4 | AND
 147 | | ... | Honeycomb removes BGP route | ${node} | ${address_internal}
 148 | | ... | ${route_address_ipv4_2} | ${route_id_ipv4_2} | ipv4
 149 | | ...
 150 | | Given BGP peer from Honeycomb should be
 151 | | ... | ${node} | ${address_internal} | ${peer_internal}
 152 | | When Honeycomb configures BGP route
 153 | | ... | ${node} | ${address_internal} | ${route_data_ipv4}
 154 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 155 | | And Honeycomb configures BGP route
 156 | | ... | ${node} | ${address_internal} | ${route_data_ipv4_2}
 157 | | ... | ${route_address_ipv4_2} | ${route_id_ipv4_2} | ipv4
 158 | | Then BGP Route from Honeycomb should be
 159 | | ... | ${node} | ${address_internal} | ${route_data_ipv4}
 160 | | ... | ${route_address_ipv4} | ${route_id_ipv4} | ipv4
 161 | | And BGP Route from Honeycomb should be
 162 | | ... | ${node} | ${address_internal} | ${route_data_ipv4_2}
 163 | | ... | ${route_address_ipv4_2} | ${route_id_ipv4_2} | ipv4