Merge pull request openshift#88823 from slovern/TELCODOCS-2107

TELCODOCS-2107 - CNF-13189 - Remove the internal API and sidecar support

Author: xenolinux

_topic_maps/_topic_map.yml

@@ -1518,10 +1518,6 @@ Topics:
     File: ptp-cloud-events-consumer-dev-reference-v2
   - Name: PTP events REST API v2 reference
     File: ptp-events-rest-api-reference-v2
-  - Name: Developing PTP events consumer applications with the REST API v1
-    File: ptp-cloud-events-consumer-dev-reference
-  - Name: PTP events REST API v1 reference
-    File: ptp-events-rest-api-reference
 - Name: CIDR range definitions
   File: cidr-range-definitions
 - Name: Multiple networks

modules/cnf-about-ptp-and-clock-synchronization.adoc

@@ -3,6 +3,7 @@
 // * networking/ptp/about-ptp.adoc
 
 :_mod-docs-content-type: CONCEPT
+:ptp-events-rest-api: v2
 [id="cnf-about-ptp-and-clock-synchronization_{context}"]
 = About PTP and clock synchronization error events
 
@@ -17,7 +18,8 @@ Event notifications are available to vRAN applications running on the same DU no
 A publish/subscribe REST API passes events notifications to the messaging bus.
 Publish/subscribe messaging, or pub-sub messaging, is an asynchronous service-to-service communication architecture where any message published to a topic is immediately received by all of the subscribers to the topic.
 
-The PTP Operator generates fast event notifications for every PTP-capable network interface. You can access the events by using a `cloud-event-proxy` sidecar container over an HTTP message bus.
+The PTP Operator generates fast event notifications for every PTP-capable network interface. 
+The consumer application can subscribe to PTP events by using the PTP events REST API {ptp-events-rest-api}.
 
 [NOTE]
 ====

modules/cnf-about-ptp-fast-event-notifications-framework.adoc

@@ -11,7 +11,5 @@ Use the Precision Time Protocol (PTP) fast event REST API v2 to subscribe cluste
 
 [NOTE]
 ====
-The fast events notifications framework uses a REST API for communication. The PTP events REST API v1 and v2 are based on the _O-RAN O-Cloud Notification API Specification for Event Consumers 3.0_ that is available from link:https://orandownloadsweb.azurewebsites.net/specifications[O-RAN ALLIANCE Specifications].
-
-Only the PTP events REST API v2 is O-RAN v3 compliant.
+The fast events notifications framework uses a REST API for communication. The PTP events REST API v2 is based on the _O-RAN O-Cloud Notification API Specification for Event Consumers 3.0_ that is available from link:https://orandownloadsweb.azurewebsites.net/specifications[O-RAN ALLIANCE Specifications].
 ====

modules/cnf-configuring-the-ptp-fast-event-publisher.adoc

@@ -29,11 +29,6 @@ endif::[]
 ifeval::["{ptp-events-rest-api}" == "v2"]
 include::snippets/ptp-event-config-api-v2.adoc[]
 endif::[]
-+
-[NOTE]
-====
-In {product-title} 4.13 or later, you do not need to set the `spec.ptpEventConfig.transportHost` field in the `PtpOperatorConfig` resource when you use HTTP transport for PTP events.
-====
 
 .. Update the `PtpOperatorConfig` CR:
 +

networking/ptp/configuring-ptp.adoc

@@ -30,7 +30,7 @@ include::modules/nw-ptp-configuring-linuxptp-services-as-grandmaster-clock-dual-
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
+* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
 
 include::modules/nw-ptp-grandmaster-clock-configuration-reference.adoc[leveloffset=+2]
 
@@ -56,7 +56,7 @@ include::modules/nw-ptp-configuring-linuxptp-services-as-boundary-clock.adoc[lev
 
 * xref:../../networking/ptp/configuring-ptp.adoc#cnf-configuring-fifo-priority-scheduling-for-ptp_configuring-ptp[Configuring FIFO priority scheduling for PTP hardware]
 
-* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
+* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
 
 include::modules/ptp-configuring-linuxptp-services-as-boundary-clock-dual-nic.adoc[leveloffset=+2]
 
@@ -69,7 +69,7 @@ include::modules/nw-ptp-configuring-linuxptp-services-as-ordinary-clock.adoc[lev
 
 * xref:../../networking/ptp/configuring-ptp.adoc#cnf-configuring-fifo-priority-scheduling-for-ptp_configuring-ptp[Configuring FIFO priority scheduling for PTP hardware]
 
-* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
+* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
 
 include::modules/nw-columbiaville-ptp-config-refererence.adoc[leveloffset=+2]
 

networking/ptp/ptp-cloud-events-consumer-dev-reference.adoc

@@ -10,9 +10,6 @@ spec:
   daemonNodeSelector:
     node-role.kubernetes.io/worker: ""
   ptpEventConfig:
-    apiVersion: "2.0" <1>
-    enableEventPublisher: true <2>
+    enableEventPublisher: true <1>
 ----
-<1> Enable the PTP events REST API v2 for the PTP event producer by setting the `ptpEventConfig.apiVersion` to "2.0".
-The default value is "1.0".
-<2> Enable PTP fast event notifications by setting `enableEventPublisher` to `true`.
+<1> Enable PTP fast event notifications by setting `enableEventPublisher` to `true`.