Skip to content

fix docs for VM live migration network#72586

Closed
johnsimcall wants to merge 1 commit intoopenshift:mainfrom
johnsimcall:patch-2
Closed

fix docs for VM live migration network#72586
johnsimcall wants to merge 1 commit intoopenshift:mainfrom
johnsimcall:patch-2

Conversation

@johnsimcall
Copy link
Copy Markdown

@johnsimcall johnsimcall commented Mar 5, 2024

Avoid using the number-2 callout/identifier multiple times. Instruct users to create the net-attach-def in a particular namespace. Avoid using NAD abbreviation when the short form of NetworkAttachmentDefinition is net-attach-def

Version(s):
Applies to all versions of OpenShift documentation

Issue:
No issue exists. Do I need to create a Jira / Bugzilla for a minor change like this?

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Avoid using the openshift#2 callout/identifier multiple times.
Instruct users to create the net-attach-def in a particular namespace.
Avoid using NAD abbreviation when the short form of NetworkAttachmentDefinition is net-attach-def
@openshift-ci openshift-ci Bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 5, 2024
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 5, 2024

Hi @johnsimcall. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

@johnsimcall
Copy link
Copy Markdown
Author

@openshift/team-documentation - would you please review this minor change that improves the documentation for creating a dedicated live migration network for KubeVirt / OpenShift Virtualization?

@kalexand-rh kalexand-rh requested a review from ousleyp March 8, 2024 18:59
@kalexand-rh
Copy link
Copy Markdown
Contributor

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 8, 2024
@ocpdocs-previewbot
Copy link
Copy Markdown

🤖 Fri Mar 08 19:05:31 - Prow CI generated the docs preview:
https://72586--ocpdocs-pr.netlify.app

@ousleyp
Copy link
Copy Markdown
Member

ousleyp commented Mar 11, 2024

@sjhala-ccs, can you please review this networking-related change? Thanks. :)

Copy link
Copy Markdown
Contributor

@sjhala-ccs sjhala-ccs left a comment

Choose a reason for hiding this comment

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

@johnsimcall Thank you for catching this doc issue. The call out numbering and description seems fine for 4.13 and earlier versions. The changes were likely introduced during the network docs reorganization applied to 4.14+.

<4> Specify an IP address range for the secondary network. This range must not overlap the IP addresses of the main network.
<2> The `NetworkAttachmentDefinition` object must be created in the {CNVNamespace} namespace.
<3> Specify the name of the NIC to be used for live migrations.
<4> Specify the name of the CNI plugin that provides the network for the `NetworkAttachmentDefinition`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
<4> Specify the name of the CNI plugin that provides the network for the `NetworkAttachmentDefinition`.
<4> Specify the name of the CNI plugin that provides the network for the network attachment definition.

<2> Specify the name of the NIC to be used for live migration.
<3> Specify the name of the CNI plugin that provides the network for the NAD.
<4> Specify an IP address range for the secondary network. This range must not overlap the IP addresses of the main network.
<2> The `NetworkAttachmentDefinition` object must be created in the {CNVNamespace} namespace.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
<2> The `NetworkAttachmentDefinition` object must be created in the {CNVNamespace} namespace.
<2> Specify the namespace where the `NetworkAttachmentDefinition` object resides. This must be `{CNVNamespace}`.

@sjhala-ccs sjhala-ccs added the peer-review-done Signifies that the peer review team has reviewed this PR label Mar 11, 2024
@ousleyp ousleyp removed their request for review April 1, 2024 21:37
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 12, 2024

@johnsimcall: 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/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2024
@bergerhoffer
Copy link
Copy Markdown
Contributor

The branch/enterprise-4.18 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.17. And any PR going into main must also target the latest version branch (enterprise-4.18).

If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

@openshift-bot
Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 14, 2024
@openshift-bot
Copy link
Copy Markdown

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Dec 15, 2024
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Dec 15, 2024

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 CNV Label for all CNV PRs lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants