Merge pull request #80109 from rohennes/TELCODOCS-1947

TELCODOCS-1947: Removing BMER from docs as it is EOL

Author: michaelryanpeter

_topic_maps/_topic_map.yml

@@ -3087,8 +3087,6 @@ Topics:
 - Name: Managing bare metal hosts
   File: managing-bare-metal-hosts
   Distros: openshift-origin,openshift-enterprise
-- Name: Monitoring bare-metal events
-  File: using-rfhe
 - Name: What huge pages do and how they are consumed by apps
   File: what-huge-pages-do-and-how-they-are-consumed-by-apps
   Distros: openshift-origin,openshift-enterprise

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

@@ -89,24 +89,6 @@ include::modules/ztp-configuring-ptp-fast-events-amqp.adoc[leveloffset=+2]
 
 * xref:../../registry/index.adoc#registry-overview[{product-registry} overview]
 
-[id="ztp-advanced-policy-config-bare-metal_{context}"]
-== Configuring bare-metal events with {policy-gen-cr} CRs
-
-You can use the {ztp} pipeline to configure bare-metal events that use HTTP or AMQP transport.
-
-include::snippets/ptp-amq-interconnect-eol.adoc[]
-
-include::modules/ztp-configuring-hwevents-using-pgt.adoc[leveloffset=+2]
-
-[role="_additional-resources"]
-.Additional resources
-
-* xref:../../scalability_and_performance/using-rfhe.adoc#nw-rfhe-installing-operator-cli_using-rfhe[Installing the {redfish-operator} using the CLI]
-
-* xref:../../scalability_and_performance/using-rfhe.adoc#nw-rfhe-creating-hardware-event_using-rfhe[Creating the bare-metal event and Secret CRs]
-
-include::modules/ztp-creating-hwevents-amqp.adoc[leveloffset=+2]
-
 include::modules/ztp-add-local-reg-for-sno-duprofile.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

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

@@ -85,24 +85,6 @@ include::modules/ztp-configuring-ptp-fast-events-amqp.adoc[leveloffset=+2]
 
 * xref:../../registry/index.adoc#registry-overview[{product-registry} overview]
 
-[id="ztp-advanced-policy-config-bare-metal_{context}"]
-== Configuring bare-metal events with PolicyGenTemplate CRs
-
-You can use the {ztp} pipeline to configure bare-metal events that use HTTP or AMQP transport.
-
-include::snippets/ptp-amq-interconnect-eol.adoc[]
-
-include::modules/ztp-configuring-hwevents-using-pgt.adoc[leveloffset=+2]
-
-[role="_additional-resources"]
-.Additional resources
-
-* xref:../../scalability_and_performance/using-rfhe.adoc#nw-rfhe-installing-operator-cli_using-rfhe[Installing the {redfish-operator} using the CLI]
-
-* xref:../../scalability_and_performance/using-rfhe.adoc#nw-rfhe-creating-hardware-event_using-rfhe[Creating the bare-metal event and Secret CRs]
-
-include::modules/ztp-creating-hwevents-amqp.adoc[leveloffset=+2]
-
 include::modules/ztp-add-local-reg-for-sno-duprofile.adoc[leveloffset=+1]
 
 [role="_additional-resources"]

modules/baremetal-event-relay.adoc

@@ -1,21 +1,20 @@
 // Module included in the following assemblies:
 //
-// * scalability_and_performance/using-rfhe.adoc
 // * networking/ptp/using-ptp-events.adoc
 
 :_mod-docs-content-type: PROCEDURE
 [id="cnf-migrating-from-amqp-to-http-transport_{context}"]
-= Migrating consumer applications to use HTTP transport for PTP or bare-metal events
+= Migrating consumer applications to use HTTP transport for PTP
 
-If you have previously deployed PTP or bare-metal events consumer applications, you need to update the applications to use HTTP message transport.
+If you have previously deployed PTP consumer applications, you need to update the applications to use HTTP message transport.
 
 .Prerequisites
 
 * You have installed the OpenShift CLI (`oc`).
 
 * You have logged in as a user with `cluster-admin` privileges.
 
-* You have updated the PTP Operator or {redfish-operator} to version 4.13+ which uses HTTP transport by default.
+* You have updated the PTP Operator to version 4.13+ which uses HTTP transport by default.
 
 .Procedure
 
@@ -39,7 +38,6 @@ containers:
 <1> The PTP Operator automatically resolves `NODE_NAME` to the host that is generating the PTP events.
 For example, `compute-1.example.com`.
 +
-In a cluster with bare-metal events configured, set the `http-event-publishers` field to `hw-event-publisher-service.openshift-bare-metal-events.svc.cluster.local:9043` in the cloud event sidecar deployment CR.
 
 . Deploy the `consumer-events-subscription-service` service alongside the events consumer application.
 For example: