Merge pull request #80692 from aireilly/remove-amqp-TELCODOCS-1862

TELCODOCS-1862 - remove EOL AMQP docs for 4.17

Author: aireilly

edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc

@@ -69,9 +69,7 @@ include::modules/ztp-provisioning-lvm-storage.adoc[leveloffset=+1]
 [id="ztp-advanced-policy-config-ptp_{context}"]
 == Configuring PTP events with {policy-gen-cr} CRs
 
-You can use the {ztp} pipeline to configure PTP events that use HTTP or AMQP transport.
-
-include::snippets/ptp-amq-interconnect-eol.adoc[]
+You can use the {ztp} pipeline to configure PTP events that use HTTP transport.
 
 include::modules/ztp-configuring-ptp-fast-events.adoc[leveloffset=+2]
 
@@ -80,13 +78,9 @@ include::modules/ztp-configuring-ptp-fast-events.adoc[leveloffset=+2]
 
 * xref:../../edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc#ztp-using-pgt-to-update-source-crs_ztp-advanced-policygenerator-config[Using {policy-gen-cr} CRs to override source CRs content]
 
-include::modules/ztp-configuring-ptp-fast-events-amqp.adoc[leveloffset=+2]
-
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/using-ptp-events.adoc#cnf-installing-amq-interconnect-messaging-bus_using-ptp-events[Installing the AMQ messaging bus]
-
 * xref:../../registry/index.adoc#registry-overview[{product-registry} overview]
 
 include::modules/ztp-add-local-reg-for-sno-duprofile.adoc[leveloffset=+1]

edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc

@@ -65,9 +65,7 @@ include::modules/ztp-provisioning-lvm-storage.adoc[leveloffset=+1]
 [id="ztp-advanced-policy-config-ptp_{context}"]
 == Configuring PTP events with PolicyGenTemplate CRs
 
-You can use the {ztp} pipeline to configure PTP events that use HTTP or AMQP transport.
-
-include::snippets/ptp-amq-interconnect-eol.adoc[]
+You can use the {ztp} pipeline to configure PTP events that use HTTP transport.
 
 include::modules/ztp-configuring-ptp-fast-events.adoc[leveloffset=+2]
 
@@ -76,13 +74,9 @@ include::modules/ztp-configuring-ptp-fast-events.adoc[leveloffset=+2]
 
 * xref:../../edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc#ztp-using-pgt-to-update-source-crs_ztp-advanced-policy-config[Using PolicyGenTemplate CRs to override source CRs content]
 
-include::modules/ztp-configuring-ptp-fast-events-amqp.adoc[leveloffset=+2]
-
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/using-ptp-events.adoc#cnf-installing-amq-interconnect-messaging-bus_using-ptp-events[Installing the AMQ messaging bus]
-
 * xref:../../registry/index.adoc#registry-overview[{product-registry} overview]
 
 include::modules/ztp-add-local-reg-for-sno-duprofile.adoc[leveloffset=+1]

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

@@ -10,11 +10,9 @@ Loss of PTP synchronization is a critical error for a RAN network. If synchroniz
 
 Event notifications are available to vRAN applications running on the same DU node. 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 or Advanced Message Queuing Protocol (AMQP) message bus.
+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.
 
 [NOTE]
 ====
 PTP fast event notifications are available for network interfaces configured to use PTP ordinary clocks, PTP grandmaster clocks, or PTP boundary clocks.
 ====
-
-include::snippets/ptp-amq-interconnect-eol.adoc[]

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

@@ -13,12 +13,10 @@ Use the Precision Time Protocol (PTP) fast event notifications framework to subs
 The fast events notifications framework uses a REST API for communication. The REST API 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].
 ====
 
-The framework consists of a publisher, subscriber, and an AMQ or HTTP messaging protocol to handle communications between the publisher and subscriber applications.
+The framework consists of a publisher, subscriber, and an HTTP messaging protocol to handle communications between the publisher and subscriber applications.
 Applications run the `cloud-event-proxy` container in a sidecar pattern to subscribe to PTP events.
 The `cloud-event-proxy` sidecar container can access the same resources as the primary application container without using any of the resources of the primary application and with no significant latency.
 
-include::snippets/ptp-amq-interconnect-eol.adoc[]
-
 .Overview of PTP fast events
 image::319_OpenShift_PTP_bare-metal_OCP_nodes_0323_4.13.png[Overview of PTP fast events]
 
@@ -34,14 +32,14 @@ image:darkcircle-3.png[20,20] Event is persisted::
 The `cloud-event-proxy` sidecar in the PTP Operator-managed pod processes the event and publishes the cloud-native event by using a REST API.
 
 image:darkcircle-4.png[20,20] Message is transported::
-The message transporter transports the event to the `cloud-event-proxy` sidecar in the application pod over HTTP or AMQP 1.0 QPID.
+The message transporter transports the event to the `cloud-event-proxy` sidecar in the application pod over HTTP.
 
 image:darkcircle-5.png[20,20] Event is available from the REST API::
 The `cloud-event-proxy` sidecar in the Application pod processes the event and makes it available by using the REST API.
 
 image:darkcircle-6.png[20,20] Consumer application requests a subscription and receives the subscribed event::
 The consumer application sends an API request to the `cloud-event-proxy` sidecar in the application pod to create a PTP events subscription.
-The `cloud-event-proxy` sidecar creates an AMQ or HTTP messaging listener protocol for the resource specified in the subscription.
+The `cloud-event-proxy` sidecar creates an HTTP messaging listener protocol for the resource specified in the subscription.
 
 The `cloud-event-proxy` sidecar in the application pod receives the event from the PTP Operator-managed pod, unwraps the cloud events object to retrieve the data, and posts the event to the consumer application.
 The consumer application listens to the address specified in the resource qualifier and receives and processes the PTP event.

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

@@ -41,7 +41,6 @@ spec:
 [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.
-Set `transportHost` only when you use AMQP transport for PTP events.
 ====
 
 .. Update the `PtpOperatorConfig` CR:

modules/cnf-installing-amq-interconnect-messaging-bus.adoc

@@ -8,8 +8,6 @@
 
 Use the following example `cloud-event-proxy` deployment and subscriber service CRs as a reference when deploying your PTP events consumer application.
 
-include::snippets/ptp-amq-interconnect-eol.adoc[]
-
 .Reference cloud-event-proxy deployment with HTTP transport
 [source,yaml]
 ----
@@ -64,57 +62,6 @@ spec:
               emptyDir: {}
 ----
 
-.Reference cloud-event-proxy deployment with AMQ transport
-[source,yaml]
-----
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: cloud-event-proxy-sidecar
-  namespace: cloud-events
-  labels:
-    app: cloud-event-proxy
-spec:
-  selector:
-    matchLabels:
-      app: cloud-event-proxy
-  template:
-    metadata:
-      labels:
-        app: cloud-event-proxy
-    spec:
-      nodeSelector:
-        node-role.kubernetes.io/worker: ""
-      containers:
-        - name: cloud-event-sidecar
-          image: openshift4/ose-cloud-event-proxy
-          args:
-            - "--metrics-addr=127.0.0.1:9091"
-            - "--store-path=/store"
-            - "--transport-host=amqp://router.router.svc.cluster.local"
-            - "--api-port=8089"
-          env:
-            - name: <node_name>
-              valueFrom:
-                fieldRef:
-                  fieldPath: spec.nodeName
-            - name: <node_ip>
-              valueFrom:
-                fieldRef:
-                  fieldPath: status.hostIP
-          volumeMounts:
-            - name: pubsubstore
-              mountPath: /store
-          ports:
-            - name: metrics-port
-              containerPort: 9091
-            - name: sub-port
-              containerPort: 9043
-          volumes:
-            - name: pubsubstore
-              emptyDir: {}
-----
-
 .Reference cloud-event-proxy subscriber service
 [source,yaml]
 ----

modules/ptp-reference-deployment-and-service-crs.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ztp-advanced-policy-config.adoc
-// * edge_computing/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc
 
 :_module-type: CONCEPT
 [id="ztp-add-local-reg-for-sno-duprofile_{context}"]

modules/ztp-add-local-reg-for-sno-duprofile.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ztp-advanced-policy-config.adoc
-// * edge_computing/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc
 
 :_mod-docs-content-type: PROCEDURE
 

modules/ztp-adding-new-content-to-gitops-ztp.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ztp-advanced-policy-config.adoc
-// * edge_computing/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc
 
 :_module-type: PROCEDURE
 [id="ztp-configuring-disk-partitioning_{context}"]
@@ -63,7 +63,7 @@ $ butane storage.bu
 ----
 --
 
-. Use a tool such as link:https://jsonformatter.org/json-pretty-print[JSON Pretty Print] to convert the output into JSON format. 
+. Use a tool such as link:https://jsonformatter.org/json-pretty-print[JSON Pretty Print] to convert the output into JSON format.
 
 . Copy the output into the `.spec.clusters.nodes.ignitionConfigOverride` field in the `SiteConfig` CR.
 +
@@ -115,13 +115,13 @@ spec:
                 }
               ]
             }
-          }   
+          }
 [...]
 ----
 +
 [NOTE]
 ====
-If the `.spec.clusters.nodes.ignitionConfigOverride` field does not exist, create it.  
+If the `.spec.clusters.nodes.ignitionConfigOverride` field does not exist, create it.
 ====
 
 .Verification
@@ -141,7 +141,7 @@ $ oc get bmh -n my-sno-ns my-sno -ojson | jq '.metadata.annotations["bmac.agent-
 ----
 --
 
-. After installation, check the {sno} disk status. 
+. After installation, check the {sno} disk status.
 
 .. Enter into a debug session on the {sno} node by running the following command. This step instantiates a debug pod called `<node_name>-debug`:
 +
@@ -200,4 +200,4 @@ tmpfs           126G  4.0K  126G   1% /tmp
 /dev/sda5       203G  119G   85G  59% /var/lib/containers
 /dev/sda3       350M  110M  218M  34% /boot
 tmpfs            26G     0   26G   0% /run/user/1000
-----
+----

modules/ztp-configuring-disk-partitioning.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ztp-advanced-policy-config.adoc
-// * edge_computing/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="ztp-configuring-pgt-compliance-eval-timeouts_{context}"]

modules/ztp-configuring-pgt-compliance-eval-timeouts.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ztp-advanced-policy-config.adoc
-// * edge_computing/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc
 
 :_module-type: PROCEDURE
 [id="ztp-configuring-pgt-image-registry_{context}"]

modules/ztp-configuring-pgt-image-registry.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/ztp-advanced-policy-config.adoc
-// * edge_computing/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygenerator_for_ztp/ztp-advanced-policygenerator-config.adoc
+// * edge_computing/policygentemplate_for_ztp/ztp-advanced-policy-config.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="ztp-configuring-ptp-fast-events_{context}"]