Comment 4 for bug 1961358

Reviewed: https://review.opendev.org/c/starlingx/ptp-notification-armada-app/+/862725
Committed: https://opendev.org/starlingx/ptp-notification-armada-app/commit/a5297275b49dc6679f891c0537e37c0fe7ffa078
Submitter: "Zuul (22348)"
Branch: r/stx.6.0

commit a5297275b49dc6679f891c0537e37c0fe7ffa078
Author: Cole Walker <email address hidden>
Date: Fri Mar 4 16:17:28 2022 -0500

    [PTP SyncE] Support ptp-notification on GM node

    This change adds support for the ptp-notification armada app to track
    the clock status on a node operating as GM. This is required for nodes
    running Westport Channel NICs using the GNSS module as the clock and
    time of day source. This will require a rebuild of the
    notificationservice container image.

    The also fixes an issue where ptp-notification would no longer deploy
    with multi-instance ptp because several of the paths that were being
    mounted to the pods have been changed. The fix was to change these paths
    to user-configurable variables which can be supplied to the notification
    application as helm overrides. This change is only to the helm charts
    and does not require an image build.

    Testing:

    PASS: Build and deploy stx-ptp-notification-helm with multi instance
    ptp.

    PASS: Build notificationservice container and deploy with helm charts,
    validated that a GM node reported locked/holdover/freerun status
    correctly.

    Closes-Bug: 1961358
    Story: 2009130
    Task: 44700

    Signed-off-by: Cole Walker <email address hidden>
    Change-Id: Ibc1fc6c6342f873ea75c2e4015eb4c910b7010fd
    (cherry picked from commit f626e3a6b890b4e9990f39d8fe98b39057ee5ed4)