Skip to content

Conversation

@jherrman
Copy link
Contributor

@jherrman jherrman commented Aug 7, 2025

Version(s):
4.15 - 4.18

Issue:
https://issues.redhat.com/browse/CNV-44070

Link to docs preview:
https://97319--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html#virt-creating-localnet-nad-cli_virt-connecting-vm-to-ovn-secondary-network

QE review:

  • QE has approved this change.

Additional information:
This aims to be a replacement for #96699 , because the related changes likely are not relevant for 4.19 and later.

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 7, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Aug 7, 2025

@ctomasko
Copy link

@jherrman The SME provided LGTM in the Jira ticket. This PR can now be merged. Thanks

@jherrman
Copy link
Contributor Author

/label merge-review-required

@openshift-ci
Copy link

openshift-ci bot commented Aug 20, 2025

@jherrman: The label(s) /label merge-review-required cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, ok-to-test, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label merge-review-required

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.

@jherrman
Copy link
Contributor Author

/label sme-review-done

@openshift-ci openshift-ci bot added the sme-review-done Service Delivery issues that have been reviewed by SRE, PMs, Engineering, QE, etc. label Aug 20, 2025
@jherrman
Copy link
Contributor Author

/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 Aug 20, 2025
<4> The topological configuration for the network. The required value is `localnet`.
<5> Optional: The maximum transmission unit (MTU) value. If you do not set a value, the Cluster Network Operator (CNO) sets a default MTU value by calculating the difference among the underlay MTU of the primary network interface, the overlay MTU of the pod network, and byte capacity of any enabled features, such as IPsec.
<6> The value of the `namespace` and `name` fields in the `metadata` stanza of the `NetworkAttachmentDefinition` object.
<6> Optionally, for more fine-grained network management, you can configure a virtual LAN (VLAN) ID for the NAD. Pods that use this NAD will have have an interface whose traffic will be able to communicate only with other devices that use the same VLAN ID (`200` in this example).

Choose a reason for hiding this comment

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

"Pods that use this NAD will have have an interface..."

  1. My English grammar expertise is limited, so I might be wrong here, but I think that "have have" is wrong (should be "have to have"?).
  2. This is a bit confusing. Although this sentence is true, the context of this doc is VMs, not pods. Maybe it should say something like "Pods/VMs that use this NAD...".

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@yossisegev , no, you're absolutely right, "have have" is a typo here. I will also rewrite the second sentence to speak about VMs.

Thank you for the quick review!

@jherrman jherrman force-pushed the vlan-ID-for-local-topo-4.18_CNV-44070 branch from 6ab0262 to 7e57de6 Compare August 21, 2025 08:23
<4> The topological configuration for the network. The required value is `localnet`.
<5> Optional: The maximum transmission unit (MTU) value. If you do not set a value, the Cluster Network Operator (CNO) sets a default MTU value by calculating the difference among the underlay MTU of the primary network interface, the overlay MTU of the pod network, and byte capacity of any enabled features, such as IPsec.
<6> The value of the `namespace` and `name` fields in the `metadata` stanza of the `NetworkAttachmentDefinition` object.
<6> Optionally, for more fine-grained network management, you can configure a virtual LAN (VLAN) ID for the NAD. VMs that use this NAD will have an interface whose traffic will be able to communicate only with other devices that use the same VLAN ID (`200` in this example).
Copy link
Contributor

Choose a reason for hiding this comment

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

VMs that use this NAD will have an interface whose traffic will be able to communicate only with other devices that use the same VLAN ID (200 in this example).

Avoid using future tense. This sentence is also quite long, and with the current CQA assessments checking for sentence length, it would be flagged.

Maybe something along the lines of:

VMs with this NAD can only communicate with other devices using the same VLAN ID (200 in this example).

Copy link
Contributor Author

@jherrman jherrman Aug 21, 2025

Choose a reason for hiding this comment

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

This exact wording might be somewhat misleading, I think, and AFAIK we should avoid the ambiguous gerund form in favour of "that does XY". Still, you're right that the meaning can be expressed accurately enough without the future tense, and without quite as many words.

Copy link

@yossisegev yossisegev left a comment

Choose a reason for hiding this comment

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

Thank you!

@jherrman jherrman force-pushed the vlan-ID-for-local-topo-4.18_CNV-44070 branch from b331237 to 4661987 Compare August 21, 2025 11:29
@openshift-ci
Copy link

openshift-ci bot commented Aug 21, 2025

@jherrman: 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.

@MirzWeiss MirzWeiss merged commit 6473ab3 into openshift:enterprise-4.18 Aug 21, 2025
2 checks passed
@MirzWeiss
Copy link
Contributor

/cherrypick enterprise-4.15

@MirzWeiss
Copy link
Contributor

/cherrypick enterprise-4.16
/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@MirzWeiss: new pull request created: #97904

Details

In response to this:

/cherrypick enterprise-4.15

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.

@openshift-cherrypick-robot

@MirzWeiss: new pull request created: #97905

Details

In response to this:

/cherrypick enterprise-4.16
/cherrypick enterprise-4.17

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.

@openshift-cherrypick-robot

@MirzWeiss: new pull request created: #97906

Details

In response to this:

/cherrypick enterprise-4.16
/cherrypick enterprise-4.17

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.

@MirzWeiss
Copy link
Contributor

/label CNV

@openshift-ci openshift-ci bot added the CNV Label for all CNV PRs label Aug 21, 2025
@MirzWeiss
Copy link
Contributor

/label branch/enterprise-4.15
/label branch/enterprise-4.16
/label branch/enterprise-4.17
/label branch/enterprise-4.18

@openshift-ci
Copy link

openshift-ci bot commented Aug 21, 2025

@MirzWeiss: The label(s) /label branch/enterprise-4.15 , /label branch/enterprise-4.16 , /label branch/enterprise-4.17 , /label branch/enterprise-4.18 cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, ok-to-test, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label branch/enterprise-4.15
/label branch/enterprise-4.16
/label branch/enterprise-4.17
/label branch/enterprise-4.18

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.

@MirzWeiss
Copy link
Contributor

/remove-label merge-review-needed

@openshift-ci openshift-ci bot removed the merge-review-needed Signifies that the merge review team needs to review this PR label Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 CNV Label for all CNV PRs size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. sme-review-done Service Delivery issues that have been reviewed by SRE, PMs, Engineering, QE, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants