perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Oleg Zharov writes:

 

but I'm afraid that pscheduler knows nothing about that command and will try to run just simple "twping/owping/iperf/..."

without any "netns" options. One idea maybe to make a "wrapper" between "tools" and "ip netns exec " but

So far I have limited experience with PS, I will appreciate if someone could point me to the right way to use testpoint setup on Nexus.

 

pScheduler has a feature to cover that case called contexts.  In a nutshell, a context is used to change some aspect of the execution context of the tool before it runs.  There are context plugins for changing the network namespace or VRF on Linux; they’re named linuxnns and linuxvrf.  You’ll find the documentation here:  https://docs.perfsonar.net/pscheduler_ref_contexts.html.   Using contexts complicates matters and requires that people testing with your system understand how to configure their tests so they’ll work properly.

 

I’m not familiar enough with Cisco’s containers or how much control you get, but Internet2 is having good success bringing interfaces directly into Docker containers’ root network namespace using macvlan.  If they have an equivalent feature, that would simplify things considerably.

 

--Mark