Install O-Cloud DaemonSet

Daemonset pod contains Monitor Container and MessageQueue Container. These containers are used to monitor the PTP notifications and push the notifications to the DU application, respectively.

Procedure

1. Add the following label to the nodepools where PTP o-cloud daemonset pods are running:
   • telco.vmware.com.node-restriction.kubernetes.io/ptp-notifications: true
2. Onboard the ptp-ocloud-notification-daemonset.csar to Telco Cloud Automation in the Network Function Catalog.
   wget https://vmwaresaas.jfrog.io/artifactory/generic-registry/ptp-ocloud-notifications-daemonset-1.0.0.csar
3. Instantiate the onboarded CSAR to the specific workload cluster.
   • Namespace : tca-system.
   • Helm Repository URL : https://vmwaresaas.jfrog.io/ui/native/helm-registry/.
   • Use the values.yaml file to override the default values and specify the NodeSelector.
   You must match the label added to the nodepools for the PTP o-cloud daemonSet.

   container:
     monitor:
       image:
         repository: vmwaresaas.jfrog.io/registry/ptp-ocloud-notifications-monitor
         tag: 1.0.0
       holdoverPeriod: 120
       pollFrequency: 1
       ptpSimulated: False
    
   nodeSelector:
     telco.vmware.com.node-restriction.kubernetes.io/ptp-notifications: true