
Updates/additions to: -System Config PTP section -Guest Integration -Admin Tasks -Updates and Upgrades Additional examples for T-BC Incorporated patchset 3 review comments. Added Limitations section. Integrated patchset 5 comments. Remove PTP Instance Removal - moved to RNs. *Do not pick 100.019 alarm update to r6 Story: 2009130 Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibdf449fe1d7282302d9be6d90e1c1b6dd70456b4
1.6 KiB
1.6 KiB
Install PTP Notifications
notification is packaged as a system application and is managed using
the system application
and system-helm-override
commands.
provides the capability for application(s) to subscribe to asynchronous status notifications and pull for the state on demand.
You must provide helm override values indicating the
ptp4l
and phc2sys
instances being tracked by
ptp-notification
.
You must also remove your existing ptp-notification
application and upload/apply the new version. Because multiple
ptp4l
instances can be supported on a node, you must
specify which instance ptp-notification
is tracking.
For example:
Upload
ptp-notification
.~(keystone_admin)]$ system application-upload <path to application>
Edit application overrides.
cat ~/notification-override.yaml ptptracking: ptp4lSocket: /var/run/ptp4l-ptp1 ptp4lServiceName: ptp1 phc2sysServiceName: phc2sys1
Apply the overrides.
~(keystone_admin)]$ system helm-override-update ptp-notification ptp-notification notification --values notification-override.yaml
Apply
ptp-notification
.~(keystone_admin)]$ system application-apply ptp-notification