716f387f93
Worked on the comments. Corrected broken link in index. Added container integration guide. Signed-off-by: Adil <mohamed.adilassakkali@windriver.com> Change-Id: Id9d8e1abd8f15a51d9069cf7543e1b559a118369
61 lines
1.5 KiB
ReStructuredText
61 lines
1.5 KiB
ReStructuredText
|
||
.. bdx1614099833159
|
||
.. _override-default-application-values:
|
||
|
||
===================================
|
||
Override Default Application Values
|
||
===================================
|
||
|
||
You can override default application values using the commands described in this section.
|
||
|
||
|
||
|
||
.. rubric:: |proc|
|
||
|
||
|
||
#. View existing values.
|
||
|
||
.. code-block:: none
|
||
|
||
~(keystone_admin)]$ system helm-override-show ptp-notification
|
||
ptp-notification notification
|
||
|
||
#. Create a yaml file and update the fields that require Helm overrides.
|
||
|
||
.. code-block:: none
|
||
|
||
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.
|
||
|
||
.. code-block:: none
|
||
|
||
~(keystone_admin)]$ system helm-override-update ptp-notification ptp-notification notification -–values <<override.yaml>>
|
||
|
||
.. code-block:: none
|
||
|
||
~(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 |NIC| specification. The default is 15 seconds.
|
||
|
||
**poll\_freq\_seconds**
|
||
is the frequency that the tracking function monitors the ptp4l to
|
||
derive the |PTP| sync state. The default is 2 seconds.
|
||
|
||
|