[OSDOCS-13045] (Story) SDN to OVN Migration for ROSA Classic by mletalie · Pull Request #86794 · openshift/openshift-docs

mletalie · 2025-01-07T22:36:01Z

Version(s):

4.17+
Issue:

https://issues.redhat.com/browse/OSDOCS-13045
QE Review ticket: https://issues.redhat.com/browse/OSDOCS-13168
Link to docs preview:

QE review:

QE has approved this change.

https://86794--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.html
https://86794--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/about-managed-networking.html

Additional information:

ocpdocs-previewbot · 2025-01-07T22:52:54Z

🤖 Wed Feb 12 20:30:21 - Prow CI generated the docs preview:

https://86794--ocpdocs-pr.netlify.app/openshift-dedicated/latest/networking/about-managed-networking.html
https://86794--ocpdocs-pr.netlify.app/openshift-rosa-hcp/latest/rosa_release_notes/rosa-release-notes.html
https://86794--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/about-managed-networking.html
https://86794--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.html
https://86794--ocpdocs-pr.netlify.app/openshift-rosa/latest/rosa_release_notes/rosa-release-notes.html

ocpdocs-vale-bot · 2025-01-10T18:41:27Z

 == Additional resources

-* link:https://access.redhat.com/articles/7065170[{OCP-short} SDN CNI removal in OCP 4.17]
+* link:https://access.redhat.com/articles/7065170[{OCP-short} SDN CNI removal in OCP 4.17]


🤖 [error] RedHat.CaseSensitiveTerms: Use 'Red Hat OpenShift Container Platform' rather than 'OCP'. For more information, see RedHat.CaseSensitiveTerms.

ocpdocs-vale-bot · 2025-01-10T19:12:25Z

@@ -0,0 +1,23 @@
+


🤖 [error] OpenShiftAsciiDoc.ModuleContainsContentType: Module is missing the '_mod-docs-content-type' variable.

bchandra-ocp · 2025-01-14T18:15:05Z

+
+toc::[]
+
+Before upgrading to version 4.17, {product-title} clusters that are configured with the OpenShift SDN network plugin must migrate to the OVN-Kubernetes network plugin. You can perform the migration and check the migration status using the ROSA CLI.


This statement is repeating. Perhaps we leave out "You can perform the migration and check the migration status using the ROSA CLI." here?

Cluster must be in 4.15.z. It's worthwhile to mention both in the introduction section and where the CLI command is provided.

Other operations such as Cluster upgrade will not be allowed during the plugin migration.

Mention that the migration can not be interrupted. Migrating back to SDN is not possible.

Note that the cluster nodes will be rebooted during the migration. There will not be impact to workloads that are resilient to node disruptions.

Migration can take several minutes or hours depending upon the cluster size, and workload configurations.

Very helpful, thanks!

Thank for this info, @bchandra-ocp. Just so I am clear, for point #1, cluster must be version 4.15.z or above, correct? User could also do this for 4.16.z as well?

4.15.22 and above ; or 4.16.24 and above

mletalie · 2025-01-14T20:55:41Z

Currently published doc that uses similar bulleted item format.

ocpdocs-vale-bot · 2025-01-14T21:36:57Z

+As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin as well as verify the migration status using the ROSA CLI.
+
+// Before upgrading to version 4.17, you must migrate {rosa-classic-first} clusters that are configured with the OpenShift SDN network plugin to the OVN-Kubernetes network plugin. You can perform the migration and check the migration status using the ROSA CLI.
+Some considerations prior to starting migration initiation are:


🤖 [error] RedHat.TermsErrors: Use 'before' rather than 'prior to'. For more information, see RedHat.TermsErrors.

Agree with the bot!

Suggested change

Some considerations prior to starting migration initiation are:

Some considerations before starting migration initiation are:

Bot wins! :)

AedinC · 2025-01-16T12:19:21Z

/label peer-review-in-progress

AedinC · 2025-01-16T12:24:49Z

+  --subnet-configuration <configuration> <2>
+----
+<1> Replace `<cluster_id>` with the ID of the cluster you want to migrate to the OVN-Kubernetes network plugin.
+<2> Replace `<configuration>` with the subnet configuration you want to use for your newly migrated OVN-Kubernetes cluster.


An output example might be helpful here.

Agreed. That should be (will be) added to docs once the developers decide the verbiage of the output.

AedinC

Looks great Mark - just a few very minor suggestions and thoughts!
/remove-label peer-review-in-progress
/label peer-review-done
/label lgtm

AedinC · 2025-01-16T12:29:05Z

+To check the status of the migration, run the following command:
+[source,terminal]
+----
+rosa describe cluster -c <cluster_id> <1>


An output example would definitely be helpful here, and if not too much trouble, an explanation of the different migration statuses.
Is there a status for 'failed migration' and if so, what can user do to correct this- run the migration command again perhaps?
Also, regarding the migration time - is there any way to tell how long it will be? I see the time can vary between minutes to hours, but just trying to help the user realize when there might be a problem- this might not be possible. Just a few thoughts!

All good points! Will dig around and see if I can find if devs have that info.

@AedinC Did some digging and found this...so going to assume that the state object will provide the info you mentioned...but will verify once OCM-11595 is completed.

AedinC · 2025-01-16T12:34:15Z

+
+toc::[]
+
+As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin as well as verify the migration status using the ROSA CLI.


Would it be helpful to mention that OpenShift SDN network plugin was deprecated in 4.14 and removed in 4.17 and link to OCP release note: https://docs.redhat.com/en/documentation/openshift_container_platform/4.14/html-single/release_notes/index#ocp-4-14-deprecation-sdn?

That info was listed here: https://86794--ocpdocs-pr.netlify.app/openshift-rosa/latest/networking/about-managed-networking but no link was created. I believe there was a reason I didn't duplicate that info in this location but now I need to remember why :(

AedinC · 2025-01-16T12:35:04Z

+As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin as well as verify the migration status using the ROSA CLI.
+
+// Before upgrading to version 4.17, you must migrate {rosa-classic-first} clusters that are configured with the OpenShift SDN network plugin to the OVN-Kubernetes network plugin. You can perform the migration and check the migration status using the ROSA CLI.
+Some considerations prior to starting migration initiation are:


Agree with the bot!

Suggested change

Some considerations prior to starting migration initiation are:

Some considerations before starting migration initiation are:

AedinC · 2025-01-16T12:37:43Z

+
+toc::[]
+
+As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin as well as verify the migration status using the ROSA CLI.


Suggested change

As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin as well as verify the migration status using the ROSA CLI.

As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin and verify the migration status using the ROSA CLI.

AedinC · 2025-01-16T12:38:45Z

+----
+rosa describe cluster -c <cluster_id> <1>
+----
+<1> Replace `<cluster_id>` with the ID of the cluster to check  migration status.


Suggested change

<1> Replace `<cluster_id>` with the ID of the cluster to check migration status.

<1> Replace `<cluster_id>` with the ID of the cluster to check the migration status.

hunterkepley

Two comments to change --migrate-network-type to --network-type - thanks Mark

hunterkepley · 2025-01-22T18:14:32Z

+[source,terminal]
+----
+$ rosa edit cluster -c <cluster_id> <1>
+  --migrate-network-type OVNKubernetes


--network-type

hunterkepley · 2025-01-22T18:17:21Z

+
+[IMPORTANT]
+====
+You cannot include the optional flag `--ovn-internal-subnets` in the command unless you define a value for the flag `--migrate-network-type`.


--network-type

Sorry for the confusion earlier, I was confused as well since it was requested to change this back and forth

hunterkepley

LGTM, one small change but that's it

hunterkepley · 2025-01-22T20:30:37Z

+  --ovn-internal-subnets <configuration> <2>
+----
+<1> Replace `<cluster_id>` with the ID of the cluster you want to migrate to the OVN-Kubernetes network plugin.
+<2> Optional: Users can create key-value pairs to configure internal subnets using any or all of the options `join, masquerade, transit` along with a single CIDR per option. For example, `--ovn-subnet-configuration="join=0.0.0.0/24,transit=0.0.0.0/24,masquerade=0.0.0.0/24"`.


--ovn-subnet-configuration -> --ovn-internal-subnets

jfrazierRH · 2025-01-22T20:37:57Z

+
+Some considerations before starting migration initiation are:
+
+* The cluster version must be 4.15.22 and above or 4.16.24 and above.


Cluster version 4.15 req has been removed and only 4.16.24+ is supported now.

jfrazierRH · 2025-01-22T21:28:46Z

/lgtm

openshift-ci · 2025-01-29T17:11:56Z

New changes are detected. LGTM label has been removed.

EricPonvelle

Small fix, but not worth blocking merge.

EricPonvelle · 2025-02-12T19:52:06Z

+To check the status of the migration, run the following command:
+[source,terminal]
+----
+rosa describe cluster -c <cluster_id> <1>


Suggested change

rosa describe cluster -c <cluster_id> <1>

$ rosa describe cluster -c <cluster_id> <1>

rosa_release_notes/rosa-release-notes.adoc

openshift-ci · 2025-02-12T20:31:20Z

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

EricPonvelle · 2025-02-12T20:34:29Z

/cherrypick enterprise-4.17

EricPonvelle · 2025-02-12T20:34:32Z

/cherrypick enterprise-4.18

openshift-cherrypick-robot · 2025-02-12T20:35:17Z

@EricPonvelle: new pull request created: #88512

Details

In response to this:

/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 · 2025-02-12T20:35:23Z

@EricPonvelle: new pull request created: #88513

Details

In response to this:

/cherrypick 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.

openshift-ci Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 7, 2025

mletalie force-pushed the OSDOCS-13045 branch from 70b4b9b to df42c95 Compare January 7, 2025 22:36

mletalie changed the title ~~Osdocs 13045~~ [OSDOCS-13045] (Story) SDN to OVN Migration for ROSA Classic Jan 8, 2025

mletalie force-pushed the OSDOCS-13045 branch from df42c95 to 027c339 Compare January 8, 2025 22:17

mletalie force-pushed the OSDOCS-13045 branch from 55f3bf2 to 2815dbe Compare January 10, 2025 18:21

ocpdocs-vale-bot reviewed Jan 10, 2025

View reviewed changes

mletalie force-pushed the OSDOCS-13045 branch 7 times, most recently from a744c04 to 5c06a83 Compare January 14, 2025 01:52

bchandra-ocp reviewed Jan 14, 2025

View reviewed changes

mletalie force-pushed the OSDOCS-13045 branch from ab3fc90 to e608920 Compare January 14, 2025 19:03

ocpdocs-vale-bot reviewed Jan 14, 2025

View reviewed changes

mletalie force-pushed the OSDOCS-13045 branch from a4a3035 to f65e766 Compare January 14, 2025 21:49

openshift-ci Bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Jan 16, 2025

AedinC reviewed Jan 16, 2025

View reviewed changes

openshift-ci Bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jan 16, 2025

mletalie force-pushed the OSDOCS-13045 branch from 83a530e to 3d17f64 Compare January 22, 2025 18:05

hunterkepley reviewed Jan 22, 2025

View reviewed changes

mletalie force-pushed the OSDOCS-13045 branch 2 times, most recently from e4f0b08 to fc6b40d Compare January 22, 2025 20:37

jfrazierRH reviewed Jan 22, 2025

View reviewed changes

mletalie force-pushed the OSDOCS-13045 branch from cc4288a to 694dd16 Compare January 22, 2025 20:43

openshift-ci Bot assigned jfrazierRH Jan 22, 2025

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jan 22, 2025

mletalie force-pushed the OSDOCS-13045 branch from c2540d3 to 4b168b8 Compare January 29, 2025 17:11

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 29, 2025

mletalie force-pushed the OSDOCS-13045 branch 2 times, most recently from 868472a to 054053c Compare January 29, 2025 18:23

mletalie force-pushed the OSDOCS-13045 branch from 054053c to e99c306 Compare February 6, 2025 17:45

EricPonvelle reviewed Feb 12, 2025

View reviewed changes

SDN Migration

400e443

rosa_release_notes/rosa-release-notes.adoc

mletalie force-pushed the OSDOCS-13045 branch from e99c306 to 400e443 Compare February 12, 2025 20:13

SDN OVN

d33c541

EricPonvelle added branch/enterprise-4.17 branch/enterprise-4.18 labels Feb 12, 2025

EricPonvelle merged commit 0784cf1 into openshift:main Feb 12, 2025

openshift-cherrypick-robot mentioned this pull request Feb 12, 2025

[enterprise-4.17] [OSDOCS-13045] (Story) SDN to OVN Migration for ROSA Classic #88512

Merged

openshift-cherrypick-robot mentioned this pull request Feb 12, 2025

[enterprise-4.18] [OSDOCS-13045] (Story) SDN to OVN Migration for ROSA Classic #88513

Merged


		toc::[]

		Before upgrading to version 4.17, {product-title} clusters that are configured with the OpenShift SDN network plugin must migrate to the OVN-Kubernetes network plugin. You can perform the migration and check the migration status using the ROSA CLI.

	Some considerations prior to starting migration initiation are:
	Some considerations before starting migration initiation are:


		toc::[]

		As a {rosa-classic-first} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin as well as verify the migration status using the ROSA CLI.

	<1> Replace `<cluster_id>` with the ID of the cluster to check migration status.
	<1> Replace `<cluster_id>` with the ID of the cluster to check the migration status.


		Some considerations before starting migration initiation are:

		* The cluster version must be 4.15.22 and above or 4.16.24 and above.

	rosa describe cluster -c <cluster_id> <1>
	$ rosa describe cluster -c <cluster_id> <1>

Conversation

mletalie commented Jan 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ocpdocs-previewbot commented Jan 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mletalie commented Jan 14, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AedinC commented Jan 16, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

AedinC left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hunterkepley left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hunterkepley left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jfrazierRH commented Jan 22, 2025

Uh oh!

openshift-ci Bot commented Jan 29, 2025

Uh oh!

EricPonvelle left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented Feb 12, 2025

Uh oh!

EricPonvelle commented Feb 12, 2025

mletalie commented Jan 7, 2025 •

edited

Loading

ocpdocs-previewbot commented Jan 7, 2025 •

edited

Loading