You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One useful feature that Andy show me was the ability to set the dest-node in the psConfig mesh configuration. I couldn't find any documentation on it. The use case specifically for this is if you are trying to use multiple linux network name spaces.
Specifically in this example look at the "pscheduler-address"
"address": "Foo",
"contexts": [
"linuxnns_i2px"
],
"pscheduler-address": "Bar",
"_meta": {
"display-name": "I2 Cloud Clev I2PX",
"display-url": "https://Bar/toolkit/"
}
}```
Then you would use in your test spec the pscheduler address like below
``` "tests": {
"throutput": {
"type": "throughput",
"spec": {
"duration": "PT30S",
"source": "{% address[0] %}",
"dest": "{% address[1] %}",
"dest-node": "{% pscheduler_address[1] %}",
"omit": "PT5S",
"ip-version": 4
}
}
}```
The text was updated successfully, but these errors were encountered:
Hi Guys
One useful feature that Andy show me was the ability to set the dest-node in the psConfig mesh configuration. I couldn't find any documentation on it. The use case specifically for this is if you are trying to use multiple linux network name spaces.
Specifically in this example look at the "pscheduler-address"
The text was updated successfully, but these errors were encountered: