adding documentation about dest-node in psconfig
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 7
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
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"
"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
}
}
}```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing psconfig mesh-configuration documentation and the sections covering the "pscheduler-address" and test-spec fields. Document how "dest-node" supports Linux network namespaces using the provided Foo/Bar configuration and throughput example; done means a reader can understand and reproduce this setup.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100