-
Notifications
You must be signed in to change notification settings - Fork 1.9k
TELCODOCS-2099: Support for dual-port ordinary clock in PTP #91166
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
Conversation
|
@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. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Wed Apr 09 10:45:36 - Prow CI generated the docs preview: https://91166--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ptp/about-ptp.html |
1ddd857 to
76c51cd
Compare
420bd84 to
aafa737
Compare
|
@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. 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 openshift-eng/jira-lifecycle-plugin repository. |
42a2c64 to
acbd9af
Compare
modules/ptp-dual-ports-oc.adoc
Outdated
| + | ||
| [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). |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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!
acbd9af to
b5931e0
Compare
|
Good docs Ronan, LGTM |
|
@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. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/label peer-review-needed |
dfitzmau
left a comment
There was a problem hiding this 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * 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> | ||
| #... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| #... | |
| # ... |
modules/ptp-dual-ports-oc.adoc
Outdated
| [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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| {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. |
modules/ptp-dual-ports-oc.adoc
Outdated
| * 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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. |
There was a problem hiding this comment.
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.
|
/label merge-review-needed |
|
@rohennes: 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. |
xenolinux
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm merging
|
/cherrypick enterprise-4.19 |
|
@xenolinux: new pull request created: #91907 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. |
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:
Additional information: