Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[enterprise-4.14] TELCODOCS-1004, TELCODOCS-1207 - CNF-6527/CNF-7078 PTP Operator HW plugin + GNSS monitoring/events #69306

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 16 additions & 7 deletions .vale/styles/Vocab/OpenShiftDocs/accept.txt
Original file line number Diff line number Diff line change
@@ -1,20 +1,29 @@
# Regex terms added to accept.txt are ignored by the Vale linter and override RedHat Vale rules.
# Add terms that have a corresponding incorrectly capitalized form to reject.txt.

# URL slugs
(.*/)+
(?<!.*-)operator
[Ff]ronthaul
[Mm]idhaul
[Pp]assthrough
[Pp]ostinstall
[Pp]reinstall
[Rr]ealtime
[Tt]elco
Assisted Installer
Control Plane Machine Set Operator
custom resource
custom resources
custom resources?
gpsd
gpspipe
linuxptp
Mbps
Mellanox
MetalLB
NICs?
Operator
Operators
[Pp]reinstall
[Pp]ostinstall
NICs?
Mellanox
Operators?
pmc
ubxtool
VFs?
Westport
4 changes: 2 additions & 2 deletions .vale/styles/Vocab/OpenShiftDocs/reject.txt
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# Regex terms added to reject.txt are highlighted as errors by the Vale linter and override RedHat Vale rules.
# Add terms that have a corresponding correctly capitalized form to accept.txt.

(?<!.*-)operators
[Dd]eployment [Cc]onfigs?
[Dd]eployment [Cc]onfigurations?
[Oo]peratorize
Expand All @@ -11,5 +12,4 @@ configuration maps?
MachineSets
machinesets?
minions?
operators?
SNO
SNO
13 changes: 10 additions & 3 deletions _topic_maps/_topic_map.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1239,9 +1239,16 @@ Topics:
File: using-sctp
Distros: openshift-enterprise,openshift-origin
- Name: Using PTP hardware
File: using-ptp
- Name: Developing PTP events consumer applications
File: ptp-cloud-events-consumer-dev-reference
Dir: ptp
Topics:
- Name: About PTP in OpenShift clusters
File: about-ptp
- Name: Configuring PTP hardware
File: configuring-ptp
- Name: Using PTP events
File: using-ptp-events
- Name: Developing PTP events consumer applications
File: ptp-cloud-events-consumer-dev-reference
- Name: External DNS Operator
Dir: external_dns_operator
Topics:
Expand Down
2 changes: 1 addition & 1 deletion authentication/sd-configuring-identity-providers.adoc
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
:_content-type: ASSEMBLY
:_mod-docs-content-type: ASSEMBLY
[id="sd-configuring-identity-providers"]
= Configuring identity providers
include::_attributes/attributes-openshift-dedicated.adoc[]
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
8 changes: 4 additions & 4 deletions modules/cnf-about-collecting-ptp-data.adoc
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
// Module included in the following assemblies:
//
// * networking/using-ptp.adoc
// * networking/ptp/configuring-ptp.adoc

:_mod-docs-content-type: PROCEDURE
[id="cnf-about-collecting-nro-data_{context}"]
= Collecting Precision Time Protocol (PTP) Operator data
= Collecting PTP Operator data

You can use the `oc adm must-gather` CLI command to collect information about your cluster, including features and objects associated with Precision Time Protocol (PTP) Operator.
You can use the `oc adm must-gather` command to collect information about your cluster, including features and objects associated with PTP Operator.

.Prerequisites

Expand All @@ -23,4 +23,4 @@ You can use the `oc adm must-gather` CLI command to collect information about yo
[source,terminal,subs="attributes+"]
----
$ oc adm must-gather --image=registry.redhat.io/openshift4/ptp-must-gather-rhel8:v{product-version}
----
----
4 changes: 2 additions & 2 deletions modules/cnf-about-ptp-and-clock-synchronization.adoc
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
// Module included in the following assemblies:
//
// * networking/using-ptp.adoc
// * networking/ptp/using-ptp-events.adoc

:_mod-docs-content-type: CONCEPT
[id="cnf-about-ptp-and-clock-synchronization_{context}"]
= About PTP and clock synchronization error events

Loss of PTP synchronization is a critical error for a RAN network. If synchronization is lost on a node, the radio might be shut down and the network Over the Air (OTA) traffic might be shifted to another node in the wireless network. Fast event notifications mitigate against workload errors by allowing cluster nodes to communicate PTP clock sync status to the vRAN application running in the DU.

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

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * networking/using-ptp.adoc
// * networking/ptp/using-ptp-events.adoc

:_mod-docs-content-type: CONCEPT
[id="cnf-about-ptp-fast-event-notifications-framework_{context}"]
Expand Down
6 changes: 2 additions & 4 deletions modules/cnf-configuring-fifo-priority-scheduling-for-ptp.adoc
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
// Module included in the following assemblies:
//
// * networking/using-ptp.adoc
// * networking/ptp/configuring-ptp.adoc

:_mod-docs-content-type: PROCEDURE
[id="cnf-configuring-fifo-priority-scheduling-for-ptp_{context}"]
= Configuring FIFO priority scheduling for PTP hardware

In telco or other deployment configurations that require low latency performance, PTP daemon threads run in a constrained CPU footprint alongside the rest of the infrastructure components. By default, PTP threads run with the `SCHED_OTHER` policy. Under high load, these threads might not get the scheduling latency they require for error-free operation.
In telco or other deployment types that require low latency performance, PTP daemon threads run in a constrained CPU footprint alongside the rest of the infrastructure components. By default, PTP threads run with the `SCHED_OTHER` policy. Under high load, these threads might not get the scheduling latency they require for error-free operation.

To mitigate against potential scheduling latency errors, you can configure the PTP Operator `linuxptp` services to allow threads to run with a `SCHED_FIFO` policy. If `SCHED_FIFO` is set for a `PtpConfig` CR, then `ptp4l` and `phc2sys` will run in the parent container under `chrt` with a priority set by the `ptpSchedulingPriority` field of the `PtpConfig` CR.

Expand Down Expand Up @@ -76,5 +76,3 @@ $ oc -n openshift-ptp logs linuxptp-daemon-lgm55 -c linuxptp-daemon-container|gr
----
I1216 19:24:57.091872 1600715 daemon.go:285] /bin/chrt -f 65 /usr/sbin/ptp4l -f /var/run/ptp4l.0.config -2 --summary_interval -4 -m
----


6 changes: 3 additions & 3 deletions modules/cnf-configuring-log-filtering-for-linuxptp.adoc
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
// Module included in the following assemblies:
//
// * networking/using-ptp.adoc
// * networking/ptp/configuring-ptp.adoc

:_mod-docs-content-type: PROCEDURE
[id="cnf-configuring-log-filtering-for-linuxptp_{context}"]
= Configuring log filtering for linuxptp services

The `linuxptp` daemon generates logs that you can use for debugging purposes. In telco or other deployment configurations that feature a limited storage capacity, these logs can add to the storage demand.
The `linuxptp` daemon generates logs that you can use for debugging purposes. In telco or other deployment types that feature a limited storage capacity, these logs can add to the storage demand.

To reduce the number log messages, you can configure the `PtpConfig` custom resource (CR) to exclude log messages that report the `master offset` value. The `master offset` log message reports the difference between the current node's clock and the master clock in nanoseconds.

Expand Down Expand Up @@ -77,4 +77,4 @@ $ oc -n openshift-ptp logs <linux_daemon_container> -c linuxptp-daemon-container
----
<1> <linux_daemon_container> is the name of the `linuxptp-daemon` pod, for example `linuxptp-daemon-gmv2n`.
+
When you configure the `logReduce` specification, this command does not report any instances of `master offset` in the logs of the `linuxptp` daemon.
When you configure the `logReduce` specification, this command does not report any instances of `master offset` in the logs of the `linuxptp` daemon.
2 changes: 1 addition & 1 deletion modules/cnf-configuring-the-ptp-fast-event-publisher.adoc
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// * networking/using-ptp.adoc
// * networking/ptp/using-ptp-events.adoc

:_mod-docs-content-type: PROCEDURE
[id="cnf-configuring-the-ptp-fast-event-publisher_{context}"]
Expand Down
Loading