4.22 RN for TELCODOCS features#111780
Conversation
openshift-ci
Bot
added
the
size/M
| // TELCODOCS-2488 | ||
| Support for GNR-D telecom boundary clock with holdover on a GNR-D platform:: | ||
| + | ||
| You can configure a Intel® Granite Rapids-D (GNR-D) platform device as telecom boundary clock (T-BC) with holdover support by using the PTP Operator. | ||
| + | ||
| In this configuration, one time receiver (TR) port synchronizes to an upstream telecom grandmaster clock, while time transmitter (TT) ports distribute synchronized time to downstream devices. If the upstream timing source degrades, disconnects, or becomes unavailable, the system enters holdover mode and maintains timing by using configured digital phase-locked loop (DPLL) devices. | ||
| + | ||
| For more information, see TBD[Configuring GNR-D T-BC holdover on a GNR-D platform]. | ||
| // xref will be added after merging the PR |
There was a problem hiding this comment.
@vitus133
Could you please review the release note for https://redhat.atlassian.net/browse/TELCODOCS-2488?
Thanks!
| // TELCODOCS-2607 | ||
| Support for PTP boundary clock without holdover on Intel Granite Rapids-D hardware:: | ||
| + | ||
| You can now configure Precision Time Protocol (PTP) boundary clock (BC) without holdover on Intel Granite Rapids-D (GNR-D) hardware that uses onboard Network Acceleration Complex (NAC) ports and optional Carter Flat expansion network interface cards (NICs). | ||
| + | ||
| In this deployment, one time receiver (TR) port synchronizes to an upstream timing source while time transmitter (TT) ports distribute synchronized time downstream. GNR-D BC without holdover deployments on Carter Flat hardware require a continuous upstream PTP timing source because monitored holdover is not supported. | ||
| + | ||
| For more information, see TBD[Boundary clocks without holdover on Intel Granite Rapids-D hardware]. | ||
| // xref will be added after merging the PR |
There was a problem hiding this comment.
@lack
Could you please this release note for https://redhat.atlassian.net/browse/TELCODOCS-2607?
Thanks!
| // TELCODOCS-2637 | ||
| Parallel worker node upgrades for large clusters with custom machine config pools:: | ||
| + | ||
| You can accelerate upgrades in large clusters by partitioning worker nodes into custom Machine Config Pools (MCPs) that align with Kubernetes failure domains (KFDs). This approach changes the default sequential node-by-node update process into a parallel partition-based strategy. | ||
| + | ||
| This strategy is particularly relevant for bare metal and on-premise environments where you cannot add temporary surge capacity during upgrades. By updating all nodes in a single failure domain simultaneously, you can reduce upgrade time while keeping other failure domains available to maintain High Availability (HA) for workloads. | ||
| + | ||
| For more information, see TBD[Configuring custom machine config pools for parallel upgrades]. | ||
| // xref will be added after merging the feature docs PR. |
There was a problem hiding this comment.
@imiller0
Could you please review this release note for https://redhat.atlassian.net/browse/TELCODOCS-2637?
Thanks!
|
🤖 Thu May 21 14:04:08 - Prow CI generated the docs preview: |
sr1kar99
changed the title
| // TELCODOCS-2607 | ||
| Support for PTP boundary clock without holdover on Intel Granite Rapids-D hardware:: | ||
| + | ||
| You can now configure Precision Time Protocol (PTP) boundary clock (BC) without holdover on Intel Granite Rapids-D (GNR-D) hardware that uses onboard Network Acceleration Complex (NAC) ports and optional Carter Flat expansion network interface cards (NICs). | ||
| + | ||
| In this deployment, one time receiver (TR) port synchronizes to an upstream timing source while time transmitter (TT) ports distribute synchronized time downstream. GNR-D BC without holdover deployments on Carter Flat hardware require a continuous upstream PTP timing source because monitored holdover is not supported. | ||
| + | ||
| For more information, see TBD[Boundary clocks without holdover on Intel Granite Rapids-D hardware]. | ||
| // xref will be added after merging the PR | ||
|
|
||
| // TELCODOCS-2488 | ||
| Support for GNR-D telecom boundary clock with holdover on a GNR-D platform:: | ||
| + | ||
| You can configure a Intel® Granite Rapids-D (GNR-D) platform device as telecom boundary clock (T-BC) with holdover support by using the PTP Operator. | ||
| + | ||
| In this configuration, one time receiver (TR) port synchronizes to an upstream telecom grandmaster clock, while time transmitter (TT) ports distribute synchronized time to downstream devices. If the upstream timing source degrades, disconnects, or becomes unavailable, the system enters holdover mode and maintains timing by using configured digital phase-locked loop (DPLL) devices. | ||
| + | ||
| You can configure T-BC holdover on GNR-D platforms `dell/XR8720t` and `hpe/EL140-Gen12`. | ||
|
|
||
| For more information, see TBD[Configuring GNR-D T-BC holdover on a GNR-D platform]. | ||
| // xref will be added after merging the PR |
There was a problem hiding this comment.
Granite Rapids-D is GNR-D.
To keep it DRY could we go with this format?
Parent - HW support
Body
Child 1 - Feature
Body
Child 2 - Feature
Body
|
/lgtm |
openshift-ci
Bot
added
the
needs-rebase
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@Bonnie-Block: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
New changes are detected. LGTM label has been removed. |
openshift-ci
Bot
added
size/XS
|
@sr1kar99: Failed to re-open PR: state cannot be changed. There are no new commits on the sr1kar99:2637-rn branch. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@sr1kar99: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
6 participants
Version(s):
4.22
Issue:
Link to docs preview:
QE review:
Additional information: