
Moved k8S Container and OpenStack VNF sections into respective subdirs following "kubernetes" and "openstack" conventions under guest_integration and added shared index. This follows pattern used for other docs. Rebase merge conflicts, formatting corrections and removed 2x NA files Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ic56322108cdb03ab1f9e4dadf5f50fe20cd7b2d6 Signed-off-by: Ron Stone <ronald.stone@windriver.com>
1.5 KiB
1.5 KiB
Override Default Application Values
You can override default application values using the commands described in this section.
View existing values.
~(keystone_admin)]$ system helm-override-show ptp-notification ptp-notification notification
Create a yaml file and update the fields that require Helm overrides.
cat ~/override.yaml ptptracking: device: holdover_seconds: 25 poll_freq_seconds: 2
Apply the values.
Application values can be added by the user and applied, using the following commands.
Note
The application could be in the "uploaded" or "applied" state.
~(keystone_admin)]$ system helm-override-update ptp-notification ptp-notification notification -–values <<override.yaml>>
~(keystone_admin)]$ system application-apply ptp-notification
where the values are:
- simulated
-
value must be 'false' for a normal operation (used only for troubleshooting).
- holdover_seconds
-
value is the holdover time provided by the specification. The default is 15 seconds.
- poll_freq_seconds
-
is the frequency that the tracking function monitors the ptp4l to derive the sync state. The default is 2 seconds.