Remaining work: - phc2sys YANG model (infix-phc2sys.yang, instance-index + servo params) - ts2phc YANG model (GPS/PPS → PHC → ptp4l GM path) - timemaster coordination (Phase 3, after phc2sys YANG is stable) - show ptp network (YANG action or background-polled topology container) - CMLDS (requires upstream linuxptp + 802.1ASdm foundation) - Full 12-bit sdoId, fault log, performance monitoring Backported patches from linuxptp master: - port: fix unicast negotiation recovery after FAULT_DETECTED - udp: fix port-specific ptp/p2p_dst_ipv4 configuration - pmc: avoid race conditions in agent update - phc2sys: wait until pmc agent is subscribed (startup race) - fix MAC driver incorrect SIOCGHWTSTAMP adjustment flags - pmc_agent: longer update interval when not subscribed - phc2sys: don't disable pmc agent with -s/-d/-w options - port_signaling: respect ptp_minor_version in message header - port: refresh link status on faults - uds: copy server socket ownership in pmc clients (non-root pmc) - uds: don't call chmod() on client socket - port: allow mixing wildcard and exact clock identities - Add pidfile support to ptp4l, phc2sys, and timemaster Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Configuration Daemon
confd is the Infix configuration daemon that serves as the glue
between sysrepo and netopeer2 (NETCONF) and the UNIX system under
it all.
Factory & Failure Config
Infix supports both static and dynamically generated factory-config. At
boot the dynamic is always generated to /run/confd/factory-config.gen,
which is installed to /etc/factory-config.cfg and used by default, if
that file does not already exist. The same applies to the failure mode
configuration.
The following describes how a vendor/product specific config is found
and installed into /etc/factory-config.cfg before the dynamic one is
installed.
/etc/factory-config.cfg: built into the image, e.g., r2s/usr/share/product/<PRODUCT>/etc/factory-config.cfg, where the<PRODUCT>is determined from the VPD, which is available afterprobehas run, in/run/system.jsonas"product-name". The lower case version of the string is used
In the second option a script running just after probe will in fact
cp the complete product specific directory to /, meaning any file
and directory that is writable at runtime can be overloaded with device
specific versions.
Origin & References
Based on the Open Source dklibc/sysrepo_plugin_ietf_system project by Denis Kalashnikov.