The KNE Binding is an implementation of the Ondatra binding interface that runs on a network topology created with openconfig/kne.
The KNE Binding requires a YAML config file that lets the binding know how to
connect to your KNE topology. The YAML must be specified in a -config flag
passed to the Ondatra test. The file supports the following keys:
| Key | Required? | Description |
|---|---|---|
username |
yes | username to log into the KNE nodes |
password |
yes | password to log into the KNE nodes |
topology |
yes | path to a KNE topology text proto |
cli |
no | path to the kne binary |
kubecfg |
no | path to your kubeconfig file |
skip_reset |
no | if true, skip initial device reset that happens during reservation |
If cli and kubecfg are not specified, they will be inferred from the PATH
environment.
An example YAML config file:
username: tester
password: hunter2
topology: /home/tester/topo.textproto
This repo includes an example integration test that uses the KNE binding, a testbed file for that test, and a KNE topology file that is matched by the testbed. To execute the test, you must:
- create a local KNE topology with at least two linked nodes, as the testbed requires
- create a config file for your topology, as specified above
- run the test passing both the testbed and config file flags:
go test -testbed=testbed.textproto -config=path/to/config.yaml
A YAML config file that works with that topology is:
username: admin
password: admin
topology: /[YOUR GIT CLONE PATH]/ondatra/knebind/integration/topology.textproto