openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Updates for AMQP EOL + HTTP transport

Browse Source
This commit is contained in:
Aidan Reilly
2024-02-26 13:13:02 +00:00
committed by openshift-cherrypick-robot
parent fe29a9994b
commit 3d197d0837
4 changed files with 5 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/nw-rfhe-introduction.adoc
View File

@@ -6,7 +6,7 @@
[id="nw-rfhe-introduction_{context}"]
= How bare-metal events work
The {redfish-operator} enables applications running on bare-metal clusters to respond quickly to Redfish hardware changes and failures such as breaches of temperature thresholds, fan failure, disk loss, power outages, and memory failure. These hardware events are delivered over a reliable low-latency transport channel based on Advanced Message Queuing Protocol (AMQP). The latency of the messaging service is between 10 to 20 milliseconds.
The {redfish-operator} enables applications running on bare-metal clusters to respond quickly to Redfish hardware changes and failures such as breaches of temperature thresholds, fan failure, disk loss, power outages, and memory failure. These hardware events are delivered using an HTTP transport or AMQP mechanism. The latency of the messaging service is between 10 to 20 milliseconds.
The {redfish-operator} provides a publish-subscribe service for the hardware events. Applications can use a REST API to subscribe to the events. The {redfish-operator} supports hardware that complies with Redfish OpenAPI v1.8 or later.

8
modules/ptp-reference-deployment-and-service-crs.adoc
View File

@@ -8,13 +8,7 @@
Use the following example `cloud-event-proxy` deployment and subscriber service CRs as a reference when deploying your PTP events consumer application.
[NOTE]
====
Use HTTP transport instead of AMQP for PTP and bare-metal events where possible.
AMQ Interconnect is EOL from 30 June 2024.
Extended life cycle support (ELS) for AMQ Interconnect ends 30 November 2030.
For more information see, link:https://access.redhat.com/support/policy/updates/jboss_notes#p_Interconnect[Red Hat AMQ Interconnect support status].
====
include::snippets/ptp-amq-interconnect-eol.adoc[]
.Reference cloud-event-proxy deployment with HTTP transport
[source,yaml]

2
modules/ztp-creating-hwevents-amqp.adoc
View File

@@ -8,6 +8,8 @@
You can configure bare-metal events that use AMQP transport on managed clusters that you deploy with the {ztp-first} pipeline.
include::snippets/ptp-amq-interconnect-eol.adoc[]
.Prerequisites
* You have installed the OpenShift CLI (`oc`).

1
snippets/ptp-amq-interconnect-eol.adoc
View File

@@ -1,5 +1,6 @@
[NOTE]
====
HTTP transport is the default transport for PTP and bare-metal events.
Use HTTP transport instead of AMQP for PTP and bare-metal events where possible.
AMQ Interconnect is EOL from 30 June 2024.
Extended life cycle support (ELS) for AMQ Interconnect ends 29 November 2029.