Library scope: | GLOBAL |
---|
Documentation for resource file Coe
.
Check on switches(except master) where pods were created and deleted to ensure there are no stale veth ports left behind.
Checks if the pods created have been terminated.The keyword is repeated until the pods are deleted
Checks the status of nodes.This keyword is repeated until the status of all nodes is Ready
Checks the status of pods.This keyword is repeated until the status of all pods is Running
COE project requires start suite to be executed only for the first test suite.This keyword find the current suite,compares it with the stored first suite value and executes Coe.Start suite only if the cuurent suite is equal to the first suite.
COE project requires stop suite to be executed only for the last test suite.This keyword find the current suite,compares it with the stored last suite value and executes Coe.Stop suite only if the cuurent suite is equal to the last suite.
Logs of the command journalctl -u kubelet is copied to ${JENKINS_WORKSPACE}/archives/journal.log
This keyword collects the pod names and checks connectivity between each and every pod with respect to one another.
Watcher running in background logs into watcher.out which is copied to ${JENKINS_WORKSPACE}/archives/watcher.log
Ansible playbook which does all basic configuration for kubernetes nodes.
Creates pods using the labels of the nodes and busy box names passed as arguments.
Waits till the keyword delete status succeeds implying that all pods created have been deleted
Logs the configuration files present in all nodes
This keyword returns the name of current test suite.Appropriate replacement in text is done to make test suite names in SUITES and SUITE_NAME similar.
Reset K8s to clear up all stale entries
Create labels for minions so that random allocation of pods to minions is avoided
Sets the connection ids for all the nodes and get the bridge from configuration file .
Suite setup keyword.
Suite teardown keyword
Kill the watcher running at the background after completion of tests cases
Test teardown to get dumpflows,ovsconfig,model dump,node status,pod status and to dump config files and delete pods.
Checks if the configuration files are present in all nodes
Checks if watcher is running in the background