TELCODOCS#2100: New holdover feature for

[lcavalle]

Version(s):
4.20

Issue:
TELCODOCS-2100

Link to docs preview:
https://100372--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/advanced_networking/ptp/configuring-ptp.html

QE review:

• QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Fri Oct 17 10:33:23 - Prow CI generated the docs preview:

https://100372--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/advanced_networking/ptp/configuring-ptp.html

[rohennes]

Good start Lluis, some further clarity needed in a few places. This review is outside of the question of how the user gets the customized PTP rpm

[DanyPops]

This segment

Procedure

1. Configure the triple port T-BC NIC. See the example below where the PtpConfig resource contains two profiles, one for time transmitter ports (00-tbc-tt) and one to configure all the hardware, the TR port, and ts2phc and phc2sysbprocesses:

to

Procedure

1. The PtpConfig resource below configures a triple-port T-BC NIC using two distinct profiles. The first profile, 00-tbc-tt, applies to the time transmitter ports. The second, 01-tbc-tr, configures the time receiver port, which includes settings for the hardware as well as the ts2phc and phc2sys processes.

@vitus133 Is the TT / T-BC configuration profile same as the boundary clock configuration, has any changes for this feature? If no, maybe we can note that? "The time receiver configuration is same as a boundary clock configuration"?

[vitus133]

This segment

Procedure

1. Configure the triple port T-BC NIC. See the example below where the PtpConfig resource contains two profiles, one for time transmitter ports (00-tbc-tt) and one to configure all the hardware, the TR port, and ts2phc and phc2sysbprocesses:

to

Procedure

1. The PtpConfig resource below configures a triple-port T-BC NIC using two distinct profiles. The first profile, 00-tbc-tt, applies to the time transmitter ports. The second, 01-tbc-tr, configures the time receiver port, which includes settings for the hardware as well as the ts2phc and phc2sys processes.

@vitus133 Is the TT / T-BC configuration profile same as the boundary clock configuration, has any changes for this feature? If no, maybe we can note that? "The time receiver configuration is same as a boundary clock configuration"?

I heard we don't usually reference other topics / config / text in the docs. Although technically correct, we should not say "it is same as that other thing"

[lcavalle]

This segment

Procedure

1. Configure the triple port T-BC NIC. See the example below where the PtpConfig resource contains two profiles, one for time transmitter ports (00-tbc-tt) and one to configure all the hardware, the TR port, and ts2phc and phc2sysbprocesses:

to

Procedure

1. The PtpConfig resource below configures a triple-port T-BC NIC using two distinct profiles. The first profile, 00-tbc-tt, applies to the time transmitter ports. The second, 01-tbc-tr, configures the time receiver port, which includes settings for the hardware as well as the ts2phc and phc2sys processes.

@vitus133 Is the TT / T-BC configuration profile same as the boundary clock configuration, has any changes for this feature? If no, maybe we can note that? "The time receiver configuration is same as a boundary clock configuration"?

I heard we don't usually reference other topics / config / text in the docs. Although technically correct, we should not say "it is same as that other thing"

Hey @DanyPops given Vitaly's clarification, is that ok to move on? Thanks!

[dpopsuev]

@lcavalle LGTM!

[rohennes]

Good work Lluis, a few small comments. The main comment is is step 2 repetition of what you just did in step 1?

[rohennes]

Capitalization - grandmaster clock

[lcavalle]

Fixed

[openshift-ci]

@lcavalle: all tests passed!

Full PR test history. Your PR dashboard.

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.

[slovern]

/cherrypick enterprise-4.20

[openshift-cherrypick-robot]

@slovern: new pull request created: #100721

In response to this:

/cherrypick enterprise-4.20

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.