.\" Automatically generated by Pandoc 2.9.2.1
.\"
.TH "isochron-orchestrate" "1" "" "" "ISOCHRON"
.hy
.SH NAME
.PP
isochron-orchestrate - Coordinate isochron daemons
.SH SYNOPSIS
.PP
\f[B]isochron\f[R] orchestrate [\f[I]OPTIONS\f[R]]
.SH DESCRIPTION
.PP
This command opens an orchestration file containing descriptions of
daemons: how to reach them, their names, roles and parameters for the
test.
It connects to these daemons, informs them of their parameters, and
coordinates them such that they start sending traffic only when their
synchronization offset becomes lower than the required threshold.
After the test is done, the packet logs are gathered by the orchestrator
from each sender and its associated receiver, and saved on the local
filesystem.
.SH OPTIONS
.TP
\f[B]\f[CB]-h\f[B]\f[R], \f[B]\f[CB]--help\f[B]\f[R]
prints the short help message and exits
.TP
\f[B]\f[CB]-F\f[B]\f[R], \f[B]\f[CB]--input-file\f[B]\f[R] <\f[B]\f[CB]PATH\f[B]\f[R]>
specify the path to the input orchestration file.
.SH ORCHESTRATION FILE FORMAT
.PP
The orchestration file has an INI-style format supporting multi-line
statements, and with comments being delineated by the # character.
Each section denotes an orchestration node, and the lines that follow
have a \[lq]key = value\[rq] format that describe parameters for this
node.
.TP
\f[B]\f[CB]host\f[B]\f[R]
denotes the IP address through which the isochron daemon can be reached
by the orchestrator.
.TP
\f[B]\f[CB]port\f[B]\f[R]
denotes the TCP port through which the isochron daemon can be reached by
the orchestrator.
.TP
\f[B]\f[CB]exec\f[B]\f[R]
denotes the command to be executed by the isochron daemon.
The syntax is identical to what would be specified as command line
arguments to \f[C]isochron-send\f[R].
The expected behavior of a daemon in the role of a sender is also
identical to that of a dedicated sender, with some exceptions.
The \f[C]--output-file\f[R] is interpreted by the orchestrator, not by
the daemon (therefore, files are saved on the orchestrator\[cq]s
filesystem).
Communication through the management socket does not take place between
an orchestrated sender and its receiver.
Instead, the orchestrator deduces the address and port of the receiver
through the \f[C]--client\f[R] and \f[C]--stats-port\f[R] arguments of
the sender, and connects by itself to the receiver.
An orchestrated sender does not monitor sync status by itself and does
not decide when to start sending test packets.
Instead, these are controlled by the orchestrator.
.SH EXAMPLES
.PP
It is possible to orchestrate two senders running on hosts A (10.0.0.1)
and B (10.0.0.2), sending towards two receivers both on host C
(10.0.0.3), from a management node D, for the purpose of creating packet
collisions and measuring the resulting latency.
.PP
The commands on nodes A and B are:
.IP
.nf
\f[C]
ptp4l -i eth0 -2 -P --step_threshold 0.00002 &
phc2sys -a -rr --step_threshold 0.00002 &
isochron daemon
\f[R]
.fi
.PP
The commands on node C are:
.IP
.nf
\f[C]
ptp4l -i eth0 -2 -P --step_threshold 0.00002 &
phc2sys -a -rr --step_threshold 0.00002 &
isochron rcv --interface eth0 --stats-port 5000 --etype 0xdead &
isochron rcv --interface eth0 --stats-port 5001 --etype 0xdeaf &
\f[R]
.fi
.PP
The commands on node D are (the double backslashes are to prevent the
shell from interpreting them when creating the heredoc, the resulting
file will have simple backslashes):
.IP
.nf
\f[C]
cat <<- EOF > orchestration.txt
[A]
host = 10.0.0.1
port = 5000
exec = isochron send \[rs]\[rs]
        --client 10.0.0.3 \[rs]\[rs]
        --stats-port 5000 \[rs]\[rs]
        --interface eth0 \[rs]\[rs]
        --num-frames 10 \[rs]\[rs]
        --base-time 0.000000000 \[rs]\[rs]
        --cycle-time 0.01 \[rs]\[rs]
        --frame-size 1500 \[rs]\[rs]
        --sync-threshold 100 \[rs]\[rs]
        --cpu-mask 0x1 \[rs]\[rs]
        --sched-fifo \[rs]\[rs]
        --sched-priority 98 \[rs]\[rs]
        --etype 0xdead \[rs]\[rs]
        --output-file isochron-host-a.dat

[B]
host = 10.0.0.2
port = 5000
exec = isochron send \[rs]\[rs]
        --client 10.0.0.3 \[rs]\[rs]
        --stats-port 5001 \[rs]\[rs]
        --interface eth0 \[rs]\[rs]
        --num-frames 10 \[rs]\[rs]
        --base-time 0.000000100 \[rs]\[rs]
        --cycle-time 0.01 \[rs]\[rs]
        --frame-size 1500 \[rs]\[rs]
        --sync-threshold 100 \[rs]\[rs]
        --cpu-mask 0x1 \[rs]\[rs]
        --sched-fifo \[rs]\[rs]
        --sched-priority 98 \[rs]\[rs]
        --etype 0xdeaf \[rs]\[rs]
        --output-file isochron-host-b.dat
EOF

isochron orchestrate --input-file orchestration.txt
isochron report --summary --input-file isochron-host-a.dat
isochron report --summary --input-file isochron-host-b.dat
\f[R]
.fi
.SH AUTHOR
.PP
isochron was written by Vladimir Oltean <vladimir.oltean@nxp.com>
.SH SEE ALSO
.PP
isochron(8) isochron-send(8) isochron-daemon(8)
.SH COMMENTS
.PP
This man page was written using pandoc (http://pandoc.org/) by the same
author.