starlingx/docs
Code Issues Proposed changes
bc21cba0e3
docs/doc/source/guest_integration/kubernetes/install-ptp-notifications.rst
egoncalv cd1f0e68ff Inclusive Language Updates 
Patch 1: Worked on Bart and Mary's comments.

Patch 2: Worked on Bart's comments.

Signed-off-by: egoncalv <elisamaraaoki.goncalves@windriver.com>
Change-Id: Ida78101e923dbce32a1c17ba45becb4b62f17c4d
2021-06-11 17:18:40 -03:00

2.8 KiB
Raw Blame History

Install PTP Notifications

notification is packaged as an Armada 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.

  • The port must be configured as Subordinate mode (Secondary mode). For more information, see,
  • Configuring PTP Service Using Horizon <configuring-ptp-service-using-horizon>
  • Configuring PTP Service Using the CLI <configuring-ptp-service-using-the-cli>

Use the following steps to install the ptp-notification application.

  1. Label the controller(s).

    1. Source the platform environment.

      $ source /etc/platform/openrc
~(keystone_admin)]$

    2. Assign the registration label to the controller(s).

      ~(keystone_admin)]$ system host-label-assign controller-0 ptp-registration=true
~(keystone_admin)]$ system host-label-assign controller-1 ptp-registration=true

    3. Assign the notification label to the node that is configured with a Secondary port. For example:

      ~(keystone_admin)]$ system host-label-assign controller-0 ptp-notification=true

  2. Upload the application using the following command:

    ~(keystone_admin)]$ system application-upload /usr/local/share/applications/helm/ptp-notification-1.0-26.tgz

  3. Verify the application has been uploaded.

    ~(keystone_admin)]$ system application-list

  4. Apply the notification application.

    $ system application-apply ptp-notification

  5. Monitor the status.

    $ watch –n 5 system application-list

    and/or

    $ watch kubectl get pods –n notification

    The default configuration for notification pod is:

    • -notification pod:
      • Runs as a daemonset (1 pod per node with label ptp-notification=true)
    • Three containers:
      • ptp-notification-rabbitmq
      • ptp-notification-location
      • ptp-notification-ptptracking
    • Registration pod:
      • Runs as a deployment on nodes labeled with ptp-registration=true
      • Replica count of 1
      • One container: Rabbitmq