Install O-Cloud Daemonset for Systemd Deployment

O-Cloud Daemonset is required for receiving PTP notifications. The daemonset pod contains Monitor Container and MessageQueue Container. The Monitor Container monitors the PTP notifications and pushes the notifications to the DU application through the MessageQueue and Sidecar containers.

Procedure

Add the following label to the nodepools where PTP o-cloud daemonset pods needs to run:
```
telco.vmware.com.node-restriction.kubernetes.io/ptp-notifications: true
```

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-5.0.0.csar

Instantiate the onboarded CSAR to the specific workload cluster.

Enter the namespace you want to use in the Namespace field.
Enter the following value in the Helm Repository URL field.
```
https://vmwaresaas.jfrog.io/ui/native/helm-registry/
```

Use the values.yaml file with the following content to override the default values and specify the NodeSelector.

container:
  monitor:
    image:
      repository: "sebu-tcp-ran-docker-local.artifactory.eng.vmware.com/ptp-ocloud-notifications-monitor"
      tag: 5.0.0
 
nodeSelector:
  telco.vmware.com.node-restriction.kubernetes.io/ptp-notifications: true