This will create a bridge and add it to the OVSDB node.

Connect OVS to the list of controllers in the ${controller_index_list} or all if no list is provided.

Add higher levels of OVS logging

Using the json data body file as a template, a REST config request is made to create a termination-point ${tp_name} on ${bridge} for the given ${node_id}. The ports remote-ip defaults to ${TOOLS_SYSTEM_IP}

This request will create vxlan port for vxlan tunnel and attach it to the specific bridge

Check OVS instance with IP ${tools_system} has ${of_connections} OpenFlow connections.

General Use Keyword attempting to sanitize test environment for OVSDB related tests. Not every step will always be neccessary, but should not cause any problems for any new ovsdb test suites.

Used to log useful test debugs for OVSDB related system tests.

This will check that only the expected output is there for both operational and config topology data stores. Empty probably means that only ovsdb:1 is there.

This will Initiate the connection to OVSDB node from controller

This request will delete the bridge node from the OVSDB

Delete OVS groups from ${br}

Delete controller from OVS

Delete manager from OVS

List all ports of ${br} and delete ${type} ports

This request will disconnect the OVSDB node from the controller

This keyword returns first bridge name and UUID from list of bridges.

Returns the default gateway at the given ip address using route command.

Returns the dpnid from the system at the given ip address using ovs-ofctl assuming br-int is present.

Get the OvsConfig and Flow entries from OVS

Returns the ethernet adapter name from the system at the given ip address using ip addr show.

Return flow entries on the given Node.

Queries the topology in the operational datastore and searches for the node that has the ${ovs_system_ip} argument as the "remote-ip". If found, the value returned will be the value of node-id stripped of "ovsdb://uuid/". If not found, ${EMPTY} will be returned.

Get the Metadata for a given port

Get the port number for the given sub-port id

Get ${type} ports for a bridge ${br} on node ${ovs_ip}.

Return the subnet from the system at the given ip address and interface

Get tunnel id and packet count from specified table id Using regex get the n_packet and the tunnel_id from the table flow.

For debugging purposes, this will log both config and operational topo data stores

Updates two port names for the given ${bridge} in config store

Reset the OVS logging

Restart the OVS node without cleaning the current configuration.

Sets controller for the OVS bridge ${bridge} using ${controller_opt} and OF version ${ofversion}.

start the OVS node.

Stop the OVS node.

Cleans up test environment, close existing sessions.

To Verify flows are present for the corresponding table Number

Verify Flows Are Present On The Given Node

Uses "vsctl show" to check for string "is_connected"

A wrapper keyword to make it easier to validate ovs-vsctl output, and gives an easy way to check this output in a WUKS. The argument ${should_match} can control if the match should exist (True} or not (False) or don't care (anything but True or False). ${should_match} is True by default

Verify ovsdb state for the given DPN

Verify the packet count after the traffic sent