CSIT-563: HC Test: improved Lisp test coverage

added TC09-TC14 with following features:
Map Resolver
Map Server
PETR configuration
RLOC Probing
Map Register
Map Request mode

Change-Id: I0e8a573e9a0f7ef3c688a014ff879e2b3d6b9b1e
Signed-off-by: jan.hradil <jan.hradil@pantheon.tech>
Signed-off-by: selias <samelias@cisco.com>

1 files changed, 350 insertions, 4 deletions

diff --git a/resources/libraries/robot/honeycomb/lisp.robot b/resources/libraries/robot/honeycomb/lisp.robot
index e1d69ed316..0ee1314f71 100644
--- a/resources/libraries/robot/honeycomb/lisp.robot
+++ b/resources/libraries/robot/honeycomb/lisp.robot
@@ -24,10 +24,26 @@
 | | ... | - node - Information about a DUT node. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb enables Lisp \| ${nodes['DUT1']} \|
+| | ...
 | | [Arguments] | ${node}
 | | ...
-| | Set Lisp state | ${node} | enable
+| | Set Lisp state | ${node} | ${TRUE}
+
+| Honeycomb disables Lisp
+| | [Documentation] | Uses Honeycomb API to disable Lisp.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Honeycomb disables Lisp \| ${nodes['DUT1']} \|
+| | ...
+| | [Arguments] | ${node}
+| | ...
+| | Set Lisp state | ${node} | ${FALSE}
 
 | Honeycomb adds locator set
 | | [Documentation] | Uses Honeycomb API to enable Lisp.
@@ -38,12 +54,15 @@
 | | ... | - locator_set - Name for the new locator set. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb enables Lisp \| ${nodes['DUT1']} \| GigabitEthernet0/8/0\
 | | ... | \| loc_01 \|
+| | ...
 | | [Arguments] | ${node} | ${interface} | ${locator_set}
+| | ...
 | | Add locator | ${node} | ${interface} | ${locator_set}
 
-| Honeycomb adds Lisp mapping
+| Honeycomb adds Lisp Mapping
 | | [Documentation] | Uses Honeycomb API to configure a Lisp mapping.
 | | ...
 | | ... | *Arguments:*
@@ -51,9 +70,12 @@
 | | ... | - data - Lisp settings to use. Type: dictionary
 | | ...
 | | ... | *Example:*
-| | ... | \| Honeycomb adds Lisp mapping \| ${nodes['DUT1']} \| ${data} \|
+| | ...
+| | ... | \| Honeycomb adds Lisp Mapping \| ${nodes['DUT1']} \| ${data} \|
+| | ...
 | | [Arguments] | ${node} | ${data}
-| | Configure lisp mapping | ${node} | ${data}
+| | ...
+| | Configure Lisp Mapping | ${node} | ${data}
 
 | Honeycomb removes all Lisp mappings
 | | [Documentation] | Uses Honeycomb API to clear the eid-table.
@@ -62,8 +84,11 @@
 | | ... | - node - Information about a DUT node. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb removes all Lisp mappings \| ${nodes['DUT1']} \|
+| | ...
 | | [Arguments] | ${node}
+| | ...
 | | Configure lisp mapping | ${node} | ${NONE}
 
 | Lisp should not be configured
@@ -74,7 +99,9 @@
 | | ... | - node - Information about a DUT node. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp should not be configured \| ${nodes['DUT1']} \|
+| | ...
 | | [Arguments] | ${node}
 | | ...
 | | Run keyword and Expect Error | KeyError: 'lisp-feature-data'
@@ -89,10 +116,13 @@
 | | ... | - state - Expected Lisp state. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp state From Honeycomb Should Be \| ${nodes['DUT1']} \
 | | ... | \| enabled \|
+| | ...
 | | [Arguments] | ${node} | ${state}
 | | ${data}= | Get Lisp operational data | ${node}
+| | ...
 | | Run keyword if | $state == 'enabled'
 | | ... | Should be equal as strings
 | | ... | ${data['lisp-state']['enable']} | ${True}
@@ -109,8 +139,11 @@
 | | ... | - state - Expected Lisp state. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp state From VAT Should Be \| ${nodes['DUT1']} \| enabled \|
+| | ...
 | | [Arguments] | ${node} | ${state}
+| | ...
 | | ${status}= | VPP show Lisp State | ${node}
 | | Should match | ${status['feature_status']} | ${state}
 
@@ -123,9 +156,12 @@
 | | ... | - settings - Expected Lisp mapping data. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp mapping From Honeycomb Should Be \| ${nodes['DUT1']} \
 | | ... | \| ${settings} \|
+| | ...
 | | [Arguments] | ${node} | ${settings}
+| | ...
 | | ${data}= | Get Lisp operational data | ${node}
 | | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
 | | ${data}= | Set Variable | ${data['eid-table']['vni-table'][0]}
@@ -140,9 +176,12 @@
 | | ... | - settings - Expected Lisp mapping data. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp mapping From VAT Should Be \| ${nodes['DUT1']} \
 | | ... | \| ${settings} \|
+| | ...
 | | [Arguments] | ${node} | ${settings}
+| | ...
 | | ${data}= | VPP show Lisp eid table | ${node}
 | | Compare data structures | ${data[0]} | ${settings}
 
@@ -154,9 +193,12 @@
 | | ... | - node - Information about a DUT node. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp mappings from Honeycomb should not exist \
 | | ... | \| ${nodes['DUT1']} \|
+| | ...
 | | [Arguments] | ${node}
+| | ...
 | | ${data}= | Get Lisp operational data | ${node}
 | | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
 | | Should be empty | ${data['eid-table']['vni-table']}
@@ -169,8 +211,11 @@
 | | ... | - node - Information about a DUT node. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Lisp mappings from VAT should not exist \| ${nodes['DUT1']} \|
+| | ...
 | | [Arguments] | ${node}
+| | ...
 | | ${data}= | VPP show Lisp eid table | ${node}
 | | Should be empty | ${data}
 
@@ -185,9 +230,12 @@
 | | ... | - locator_set - Expected locator set name. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Locator set From Honeycomb Should Be \| ${nodes['DUT1']} \
 | | ... | \| GigabitEthernet0/8/0 \| loc01 \|
+| | ...
 | | [Arguments] | ${node} | ${interface} | ${locator_set}
+| | ...
 | | ${data}= | Get Lisp operational data | ${node}
 | | ${loc_data}= | Set Variable
 | | ... | ${data['lisp-state']['lisp-feature-data']['locator-sets']}
@@ -209,9 +257,12 @@
 | | ... | - data - Lisp adjacency settings to use. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb adds Lisp adjacency \| ${nodes['DUT1']} \| ${1} \| map1\
 | | ... | \| adj1 \| ${data} \|
+| | ...
 | | [Arguments] | ${node} | ${vni} | ${map} | ${adjacency} | ${data}
+| | ...
 | | Add Lisp adjacency
 | | ... | ${node} | ${vni} | ${map} | ${adjacency} | ${data}
 
@@ -223,11 +274,46 @@
 | | ... | - ip_address - IP address for the map resolver. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb adds Lisp Map resolver \| ${nodes['DUT1']} \
 | | ... | \| 192.168.0.2 \|
+| | ...
 | | [Arguments] | ${node} | ${ip_address}
+| | ...
 | | Add map resolver | ${node} | ${ip_address}
 
+| Honeycomb adds Lisp Map register
+| | [Documentation] | Uses Honeycomb API to configure Lisp map register.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - add_map_register - Set boolean value of map register. Type: bool
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Honeycomb adds Lisp Map register \| ${nodes['DUT1']} \
+| | ... | \| ${True} \|
+| | ...
+| | [Arguments] | ${node} | ${add_map_register}
+| | ...
+| | Set Map Register | ${node} | ${add_map_register}
+
+| Honeycomb sets Lisp Map request Mode
+| | [Documentation] | Uses Honeycomb API to configure Lisp map request mode.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - set_map_request - Set boolean value of map request mode. Type: bool
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Honeycomb adds Lisp Map Request Mode \| ${nodes['DUT1']} \
+| | ... | \| ${True} \|
+| | ...
+| | [Arguments] | ${node} | ${set_map_request}
+| | ...
+| | Set Map Request Mode | ${node} | ${set_map_request}
+
 | Map resolver from Honeycomb should be
 | | [Documentation] | Retrieves Lisp map resolver from Honeycomb operational\
 | | ... | data, and compares with expected data.
@@ -238,9 +324,12 @@
 | | ... | Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Map resolver From Honeycomb Should Be \| ${nodes['DUT1']} \
 | | ... | \| 192.168.1.2 \|
+| | ...
 | | [Arguments] | ${node} | ${ip_address}
+| | ...
 | | ${data}= | Get Lisp operational data | ${node}
 | | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
 | | ${data}= | Set Variable | ${data['map-resolvers']['map-resolver'][0]}
@@ -256,12 +345,128 @@
 | | ... | Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Map resolver From VAT Should Be \| ${nodes['DUT1']} \
 | | ... | \| 192.168.1.2 \|
+| | ...
 | | [Arguments] | ${node} | ${ip_address}
+| | ...
 | | ${data}= | Vpp show Lisp map resolver | ${node}
 | | Should be equal | ${data[0]['map resolver']} | ${ip_address}
 
+| Honeycomb adds Lisp Map Server
+| | [Documentation] | Uses Honeycomb API to configure Lisp Map Server.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - ip_addresses - IP addresses for the Map Server.\
+| | ... | Type: any number of strings
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Honeycomb adds Lisp Map Server \| ${nodes['DUT1']} \
+| | ... | \| 192.168.0.2 \| 192.168.0.3 \|
+| | ...
+| | [Arguments] | ${node} | @{ip_addresses}
+| | ...
+| | Add Map Server | ${node} | @{ip_addresses}
+
+| Map Register from Honeycomb should be
+| | [Documentation] | Retrieves Lisp Map Register from Honeycomb operational\
+| | ... | data, and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - state - Desired state - True. Type: bool
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Map Register From Honeycomb Should Be \| ${nodes['DUT1']} \
+| | ... | \| ${True} \|
+| | ...
+| | [Arguments] | ${node} | ${state}
+| | ...
+| | ${data}= | Get Lisp operational data | ${node}
+| | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
+| | ${data}= | Set Variable | ${data['map-register']}
+| | Should be equal | ${data['enabled']} | ${state}
+
+| Map Server from Honeycomb should be
+| | [Documentation] | Retrieves Lisp Map Server from Honeycomb operational\
+| | ... | data, and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - ip_addresses - IP addresses that should be referenced\
+| | ... | in Map Server. Type: any number of strings
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Map Server From Honeycomb Should Be \| ${nodes['DUT1']} \
+| | ... | \| 192.168.1.2 \| 192.168.1.7 \|
+| | ...
+| | [Arguments] | ${node} | @{ip_addresses}
+| | ...
+| | ${data}= | Get Lisp operational data | ${node}
+| | Verify Map Server Data from Honeycomb | ${data} | ${ip_addresses}
+
+
+| Map Server from VAT should be
+| | [Documentation] | Retrieves Lisp mapping from VAT,\
+| | ... | and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - ip_addresses - IP addresses that should be referenced\
+| | ... | in Map Server. Type: any number of strings
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Map Server From VAT Should Be \| ${nodes['DUT1']} \
+| | ... | \| 192.168.1.2 \| 192.168.1.7 \|
+| | ...
+| | [Arguments] | ${node} | @{ip_addresses}
+| | ...
+| | ${data}= | Vpp show Lisp Map Server | ${node}
+| | Verify Map Server Data from VAT | ${data} | ${ip_addresses}
+
+| Map Register from VAT should be
+| | [Documentation] | Retrieves Lisp mapping from VAT,\
+| | ... | and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - state - Desired state - "enabled". Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Map Register From VAT Should Be \| ${nodes['DUT1']} \
+| | ... | \| enabled \|
+| | ...
+| | [Arguments] | ${node} | ${state}
+| | ...
+| | ${data}= | Vpp show Lisp Map Register | ${node}
+| | Should be equal | ${data['state']} | ${state}
+
+| Map Request Mode from VAT should be
+| | [Documentation] | Retrieves Lisp Request Mode from VAT,\
+| | ... | and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - destination - Source or Destination in Map\
+| | ... | Request Mode. Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Map Request Mode From VAT Should Be \| ${nodes['DUT1']} \
+| | ... | \| src-dst \|
+| | ...
+| | [Arguments] | ${node} | ${destination}
+| | ...
+| | ${data}= | Vpp show Lisp Map Request Mode | ${node}
+| | Should be equal | ${data['map_request_mode']} | ${destination}
+
 | Honeycomb enables Lisp PITR feature
 | | [Documentation] | Uses Honeycomb API to configure Lisp PITR feature.
 | | ...
@@ -270,10 +475,44 @@
 | | ... | - locator_set - Name of an existing locator set. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb enables Lisp PITR feature \| ${nodes['DUT1']} \| loc1 \|
+| | ...
 | | [Arguments] | ${node} | ${locator_set}
+| | ...
 | | Configure PITR | ${node} | ${locator_set}
 
+| Honeycomb enables Lisp PETR feature
+| | [Documentation] | Uses Honeycomb API to configure Lisp PETR feature.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - ip_address - IP address. Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Honeycomb enables Lisp PETR feature \| ${nodes['DUT1']}\
+| | ... | \| 192.168.0.1 \|
+| | ...
+| | [Arguments] | ${node} | ${ip_address}
+| | ...
+| | Configure PETR | ${node} | ${ip_address}
+
+| Honeycomb enables Lisp RLOC feature
+| | [Documentation] | Uses Honeycomb API to enable the Lisp RLOC feature.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Honeycomb enables Lisp RLOC feature\
+| | ... | \| ${nodes['DUT1']} \|
+| | ...
+| | [Arguments] | ${node}
+| | ...
+| | Set RLOC probe state | ${node} | ${TRUE}
+
 | PITR config from Honeycomb should be
 | | [Documentation] | Retrieves PITR config from Honeycomb operational\
 | | ... | data, and compares with expected data.
@@ -284,14 +523,115 @@
 | | ... | in PITR config. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| PITR config from Honeycomb should be \| ${nodes['DUT1']} \
 | | ... | \| loc01 \|
+| | ...
 | | [Arguments] | ${node} | ${locator_set}
+| | ...
 | | ${data}= | Get Lisp operational data | ${node}
 | | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
 | | ${data}= | Set Variable | ${data['pitr-cfg']}
 | | Should be equal | ${data['locator-set']} | ${locator_set}
 
+| PETR configuration from Honeycomb should be
+| | [Documentation] | Retrieves PETR config from Honeycomb operational\
+| | ... | data, and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - ip_address - IP address for PETR config. Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| PETR config from Honeycomb should be \| ${nodes['DUT1']} \
+| | ... | \| 192.168.0.1 \|
+| | ...
+| | [Arguments] | ${node} | ${ip_address}
+| | ...
+| | ${data}= | Get Lisp operational data | ${node}
+| | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
+| | ${data}= | Set Variable | ${data['petr-cfg']['petr-address']}
+| | Should be equal | ${data} | ${ip_address}
+
+| Map Request Mode from Honeycomb should be
+| | [Documentation] | Retrieves List Map Request Mode from Honeycomb\
+| | ... | operational data, and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - destination - source-destination. Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| List Map Request Mode from Honeycomb should be \| ${nodes['DUT1']}\
+| | ... | \| 192.168.0.1 \|
+| | ...
+| | [Arguments] | ${node} | ${destination}
+| | ...
+| | ${data}= | Get Lisp operational data | ${node}
+| | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
+| | ${data}= | Set Variable | ${data['map-request-mode']['mode']}
+| | Should be equal | ${data} | ${destination}
+
+| RLOC probing from Honeycomb should be
+| | [Documentation] | Retrieves RLOC config from Honeycomb operational\
+| | ... | data, and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - state - desired state -True/False. Type: bool
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| RLOC probing from Honeycomb should be \| ${nodes['DUT1']} \
+| | ... | \| ${True} \|
+| | ...
+| | [Arguments] | ${node} | ${state}
+| | ...
+| | ${data}= | Get Lisp operational data | ${node}
+| | ${data}= | Set Variable | ${data['lisp-state']['lisp-feature-data']}
+| | ${data}= | Set Variable | ${data['rloc-probe']['enabled']}
+| | Should be equal | ${data} | ${state}
+
+| PETR configuration from VAT should be
+| | [Documentation] | Retrieves Lisp mapping from VAT,\
+| | ... | and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - state - state of PETR config - enabled/disabled.\
+| | ... | Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| PETR configuration From VAT Should Be \| ${nodes['DUT1']} \
+| | ... | \| enabled \|
+| | ...
+| | [Arguments] | ${node} | ${state}
+| | ...
+| | ${data}= | Vpp show Lisp PETR config | ${node}
+| | Should be equal | ${data['status']} | ${state}
+
+| RLOC probing from VAT should be
+| | [Documentation] | Retrieves Lisp mapping from VAT,\
+| | ... | and compares with expected data.
+| | ...
+| | ... | *Arguments:*
+| | ... | - node - Information about a DUT node. Type: dictionary
+| | ... | - state - state of RLOC config - enabled/disabled.\
+| | ... | Type: string
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| RLOC configuration From VAT Should Be \| ${nodes['DUT1']} \
+| | ... | \| enabled \|
+| | ...
+| | [Arguments] | ${node} | ${state}
+| | ...
+| | ${data}= | Vpp show Lisp RLOC config | ${node}
+| | Should be equal | ${data['state']} | ${state}
+
 | PITR config from VAT should be
 | | [Documentation] | Retrieves PITR config from VAT,\
 | | ... | and compares with expected data.
@@ -302,9 +642,12 @@
 | | ... | in PITR config. Type: string
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| PITR config from VAT should be \| ${nodes['DUT1']} \
 | | ... | \| loc01 \|
+| | ...
 | | [Arguments] | ${node} | ${locator_set}
+| | ...
 | | ${data}= | VPP show Lisp PITR | ${node}
 | | Should be equal | ${data['status']} | enabled
 | | Should be equal | ${data['locator_set']} | ${locator_set}
@@ -316,6 +659,9 @@
 | | ... | - node - Information about a DUT node. Type: dictionary
 | | ...
 | | ... | *Example:*
+| | ...
 | | ... | \| Honeycomb disables all Lisp features \| ${nodes['DUT1']} \|
+| | ...
 | | [Arguments] | ${node}
+| | ...
 | | Disable Lisp | ${node}
\ No newline at end of file