perfSONAR User Q&A and Other Discussion

["Garnizov, Ivan (RRZE)" <>]

Dear Murillo,

 

Your findings are correct. pScheduler is programmed to operate only in the default context. There are implemented functions, which allow the daemon to initiate the measurements in different contexts though.

Here is a documentation reference: http://docs.perfsonar.net/release_candidates/4.1b1/pscheduler_ref_contexts.html

Please note the tag of the documentation is: pS 4.1b1

 

It would be great to hear back from you with feedback, since you will be one of the few testers of this feature.

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

Jubiläumsjahr 2018 - IT in Bewegung

Das RRZE - der IT-Dienstleister der FAU

www.50-jahre.rrze.fau.de

 

 

 

From: [mailto:] On Behalf Of Murilo Vetter
Sent: Mittwoch, 6. Juni 2018 13:39
To: perfsonar-user <>
Subject: [perfsonar-user] Running pscheduler inside a linux namespace

 

Hi list,

 

We are evaluating the use of pscheduler in an atypical scenario. The scenario is described bellow and we already use it to homologate IP network circuits, but we are just using iperf and ping directly. We are wondering if it is possible to use pscheduler to schedule and run the tests inside the Linux namespaces.

 

SCENARIO DESCRIPTION:

- 1 LINUX HOST configure with:

  + 3 network interfaces:

  +-- ens192 (no namepace configure)

  +-- ens224 (namepace configure - ns-ens224)

  +-- ens256 (namepace configure - ns-ens256)

 

WHAT I AM TRYING TO DO:

* Run pscheduler (IPERF3) between both interfaces configure in the namespace

 

NODE CONFIGURATION:

Configure namespace to ens224 and ens256:

---

ip netns add ns-ens256
ip link set ens256 netns ns-ens256
ip netns exec ns-ens256 iptables -A INPUT -p icmp --icmp-type 5 -j DROP
ip netns exec ns-ens256 ifconfig ens256 mtu 9000
ip netns exec ns-ens256 ifconfig ens256 up
ip netns exec ns-ens256 ifconfig ens256 192.168.0.39 netmask 255.255.255.240 mtu 9000
ip netns exec ns-ens256 ifconfig ens256 up
ip netns exec ns-ens256 ifconfig lo up
ip netns exec ns-ens256 ip route add default via 192.168.0.33

ip netns add ns-ens224
ip link set ens224 netns ns-ens224
ip netns exec ns-ens224 iptables -A INPUT -p icmp --icmp-type 5 -j DROP
ip netns exec ns-ens224 ifconfig ens224 mtu 9000
ip netns exec ns-ens224 ifconfig ens224 up
ip netns exec ns-ens224 ifconfig ens224 192.168.0.45 netmask 255.255.255.240 mtu 9000
ip netns exec ns-ens224 ifconfig ens224 up
ip netns exec ns-ens224 ifconfig lo up
ip netns exec ns-ens224 ip route add default via 192.168.0.33

---

 

I checked if pscheduler is running of all interfaces independently if it is configure with namespace or not. I didn't change any configuration, just tried to restart service. But when I run:

 

# pscheduler ping <IP>

The only address that is up is from the Linux context, not the others 2 from the namespace.

 

Is there a way to run pscheduler in this scenario?

 

Other thing that I was trying to undestand is how linux context works in pscheduler task call. Does it just run the tool defining the namespace that it should run?

 

Regards,

--

Murilo Vetter
Analista REMEP-FLN/PoP-SC
PoP-SC - Ponto de Presença da RNP em Santa Catarina
REMEP-FLN - Rede Metropolitana de Educação e Pesquisa da Região de Florianópolis
RNP - Rede Nacional de Ensino e Pesquisa
UFSC - Universidade Federal de Santa Catarina
SETIC - Superintendência de Governança Eletrônica e Tecnologia da Informação e Comunicação
Fundações de Apoio FEESC e FEPESE
--/--

www.pop-sc.rnp.br
remep.pop-sc.rnp.br
CHAMADOS:
+55(48)3721-3000
INOC: 11242*100