Skip to content

Conversation

@rohennes
Copy link
Contributor

@rohennes rohennes commented Mar 27, 2025

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 27, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 27, 2025

@rohennes: This pull request references TELCODOCS-2099 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

TELCODOCS-2099: Support for dual-port ordinary clock in PTP

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/TELCODOCS-2099

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Mar 27, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Mar 27, 2025

@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 27, 2025
@rohennes rohennes force-pushed the TELCODOCS-2099 branch 3 times, most recently from 420bd84 to aafa737 Compare March 28, 2025 15:12
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 28, 2025

@rohennes: This pull request references TELCODOCS-2099 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

TELCODOCS-2099: Support for dual-port ordinary clock in PTP

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/TELCODOCS-2099

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@rohennes rohennes force-pushed the TELCODOCS-2099 branch 2 times, most recently from 42a2c64 to acbd9af Compare March 31, 2025 10:48
+
[NOTE]
====
You must configure the NVIDIA BlueField-3 series DPU in NIC mode before configuring the interface as an ordinary clock with improved redundancy. For further information about configuring NIC mode, see link:https://docs.nvidia.com/networking/display/bluefielddpubspv422/modes+of+operation#src-141856548_ModesofOperation-NICModeforBlueField-3[NIC Mode for BlueField-3] (NVIDIA documentation).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add the link to the reset procedure here as well as it is not clearly mentioned in the documentation. Something like "a reset is required after changing the card mode" and add the link

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the source accordingly, thanks!

@dpopsuev
Copy link

dpopsuev commented Apr 8, 2025

Good docs Ronan, LGTM

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 8, 2025

@rohennes: This pull request references TELCODOCS-2099 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

TELCODOCS-2099: Support for dual-port ordinary clock in PTP

Version(s):
4.19+

Issue:
https://issues.redhat.com/browse/TELCODOCS-2099

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@rohennes
Copy link
Contributor Author

rohennes commented Apr 8, 2025

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Apr 8, 2025
@dfitzmau dfitzmau added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Apr 8, 2025
Copy link
Contributor

@dfitzmau dfitzmau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HI @rohennes .

Nice work! Thanks for the neat PR to review. I added comments inline.

* Install the OpenShift CLI (`oc`).
* Log in as a user with `cluster-admin` privileges.
* Install the PTP Operator.
* The node uses an x86 architecture with a dual-port NIC.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The node uses an x86 architecture with a dual-port NIC.
* The node uses an x86_64 architecture with a dual-port NIC.

If correct in the given context: https://redhat-documentation.github.io/supplementary-style-guide/#x86_64

# Default Data Set
#
slaveOnly 1 <3>
#...
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#...
# ...

[id="ptp-dual-ports-oc_{context}"]
= Using dual-port NICs to improve redundancy for PTP ordinary clocks

{product-title} supports single and dual-port networking interface cards (NIC) as ordinary clocks for PTP timing. To improve redundancy, you can configure a dual-port NIC with one port as active and the other as standby.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
{product-title} supports single and dual-port networking interface cards (NIC) as ordinary clocks for PTP timing. To improve redundancy, you can configure a dual-port NIC with one port as active and the other as standby.
{product-title} supports single and dual-port networking interface cards (NICs) as ordinary clocks for PTP timing. To improve redundancy, you can configure a dual-port NIC with one port as active and the other as standby.

* If the active port fails, the standby port transitions to active to ensure continued PTP timing synchronization.
If both ports become faulty, the clock state moves to the `HOLDOVER` state, then the `FREERUN` state when the holdover timeout expires, before resyncing to a leader clock.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If both ports become faulty, the clock state moves to the `HOLDOVER` state, then the `FREERUN` state when the holdover timeout expires, before resyncing to a leader clock.
* If both ports become faulty before resyncing to a leader clock, the clock state moves to the `HOLDOVER` state, and then to the `FREERUN` state when the holdover timeout expires.

Copy link
Contributor Author

@rohennes rohennes Apr 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think not technically accurate, but I did move this to a bullet point.

@dfitzmau dfitzmau added peer-review-done Signifies that the peer review team has reviewed this PR branch/enterprise-4.19 and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Apr 8, 2025
@rohennes
Copy link
Contributor Author

rohennes commented Apr 9, 2025

HI @rohennes .

Nice work! Thanks for the neat PR to review. I added comments inline.

Thanks @dfitzmau , great review as always.

@rohennes
Copy link
Contributor Author

rohennes commented Apr 9, 2025

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 9, 2025
@openshift-ci
Copy link

openshift-ci bot commented Apr 9, 2025

@rohennes: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@xenolinux xenolinux added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Apr 9, 2025
@xenolinux xenolinux added this to the Planned for 4.19 GA milestone Apr 9, 2025
Copy link
Contributor

@xenolinux xenolinux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm merging

@xenolinux xenolinux removed the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Apr 9, 2025
@xenolinux xenolinux merged commit 8264910 into openshift:main Apr 9, 2025
2 checks passed
@xenolinux
Copy link
Contributor

/cherrypick enterprise-4.19

@openshift-cherrypick-robot

@xenolinux: new pull request created: #91907

Details

In response to this:

/cherrypick enterprise-4.19

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.19 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants