Skip to content

Commit 68b5119

Browse files
author
Steven Smith
committed
Updates rollback to SDN procedure to add live migration
1 parent 8734e9f commit 68b5119

File tree

4 files changed

+57
-51
lines changed

4 files changed

+57
-51
lines changed

‎modules/nw-network-plugin-migration-process.adoc‎

Lines changed: 0 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -48,51 +48,6 @@ Cluster:: As nodes reboot, the cluster assigns IP addresses to pods on the {sdn}
4848

4949
|===
5050

51-
ifeval::["{context}" == "migrate-from-openshift-sdn"]
52-
If a rollback to OpenShift SDN is required, the following table describes the process.
53-
54-
[IMPORTANT]
55-
====
56-
You must wait until the migration process from OpenShift SDN to OVN-Kubernetes network plugin is successful before initiating a rollback.
57-
====
58-
59-
.Performing a rollback to OpenShift SDN
60-
[cols="1,1a",options="header"]
61-
|===
62-
63-
|User-initiated steps|Migration activity
64-
65-
|Suspend the MCO to ensure that it does not interrupt the migration.
66-
|The MCO stops.
67-
68-
|
69-
Set the `migration` field of the `Network.operator.openshift.io` custom resource (CR) named `cluster` to `OpenShiftSDN`. Make sure the `migration` field is `null` before setting it to a value.
70-
|
71-
CNO:: Updates the status of the `Network.config.openshift.io` CR named `cluster` accordingly.
72-
73-
|Update the `networkType` field.
74-
|
75-
CNO:: Performs the following actions:
76-
+
77-
--
78-
* Destroys the OVN-Kubernetes control plane pods.
79-
* Deploys the OpenShift SDN control plane pods.
80-
* Updates the Multus objects to reflect the new network plugin.
81-
--
82-
83-
|
84-
Reboot each node in the cluster.
85-
|
86-
Cluster:: As nodes reboot, the cluster assigns IP addresses to pods on the OpenShift-SDN network.
87-
88-
|
89-
Enable the MCO after all nodes in the cluster reboot.
90-
|
91-
MCO:: Rolls out an update to the systemd configuration necessary for OpenShift SDN; the MCO updates a single machine per pool at a time by default, so the total time the migration takes increases with the size of the cluster.
92-
93-
|===
94-
endif::[]
95-
9651
ifdef::sdn[]
9752
:!sdn:
9853
endif::[]

‎modules/nw-ovn-kubernetes-rollback-live.adoc‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc
4+
// * networking/openshift_sdn/rollback-to-ovn-kubernetes.adoc
5+
6+
:_mod-docs-content-type: PROCEDURE
7+
[id="nw-ovn-kubernetes-rollback-live_{context}"]
8+
= Using the live migration method to migrate to the OVN-Kubernetes network plugin
9+
10+
As a cluster administrator, you can rollback to the OpenShift SDN Container Network Interface (CNI) network plugin by using the live migration method. During the migration with this method, nodes are automatically rebooted and service to the cluster is not interrupted.
11+
12+
[IMPORTANT]
13+
====
14+
You must wait until the migration process from OpenShift SDN to OVN-Kubernetes network plugin is successful before initiating a rollback.
15+
====

‎modules/nw-ovn-kubernetes-rollback.adoc‎

Lines changed: 40 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,17 +6,52 @@
66
// This procedure applies to both a roll back and a migration
77
:_mod-docs-content-type: PROCEDURE
88
[id="nw-ovn-kubernetes-rollback_{context}"]
9-
= Migrating to the OpenShift SDN network plugin
9+
= Using the offline migration method to roll back to the OpenShift SDN network plugin
1010

11-
As a cluster administrator, you can migrate to the OpenShift SDN Container Network Interface (CNI) network plugin.
12-
During the migration you must reboot every node in your cluster.
11+
As a cluster administrator, you can rollback to the OpenShift SDN Container Network Interface (CNI) network plugin by using the offline migration method. During the migration you must reboot every node in your cluster. With the offline migration method, there is some downtime, during which your cluster is unreachable.
1312

14-
ifeval::["{context}" == "rollback-to-openshift-sdn"]
1513
[IMPORTANT]
1614
====
1715
You must wait until the migration process from OpenShift SDN to OVN-Kubernetes network plugin is successful before initiating a rollback.
1816
====
19-
endif::[]
17+
18+
If a rollback to OpenShift SDN is required, the following table describes the process.
19+
20+
.Performing a rollback to OpenShift SDN
21+
[cols="1,1a",options="header"]
22+
|===
23+
24+
|User-initiated steps|Migration activity
25+
26+
|Suspend the MCO to ensure that it does not interrupt the migration.
27+
|The MCO stops.
28+
29+
|
30+
Set the `migration` field of the `Network.operator.openshift.io` custom resource (CR) named `cluster` to `OpenShiftSDN`. Make sure the `migration` field is `null` before setting it to a value.
31+
|
32+
CNO:: Updates the status of the `Network.config.openshift.io` CR named `cluster` accordingly.
33+
34+
|Update the `networkType` field.
35+
|
36+
CNO:: Performs the following actions:
37+
+
38+
--
39+
* Destroys the OVN-Kubernetes control plane pods.
40+
* Deploys the OpenShift SDN control plane pods.
41+
* Updates the Multus objects to reflect the new network plugin.
42+
--
43+
44+
|
45+
Reboot each node in the cluster.
46+
|
47+
Cluster:: As nodes reboot, the cluster assigns IP addresses to pods on the OpenShift-SDN network.
48+
49+
|
50+
Enable the MCO after all nodes in the cluster reboot.
51+
|
52+
MCO:: Rolls out an update to the systemd configuration necessary for OpenShift SDN; the MCO updates a single machine per pool at a time by default, so the total time the migration takes increases with the size of the cluster.
53+
54+
|===
2055

2156
.Prerequisites
2257

‎networking/ovn_kubernetes_network_provider/rollback-to-openshift-sdn.adoc‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,9 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9-
As a cluster administrator, you can rollback to the OpenShift SDN from the OVN-Kubernetes network plugin only after the migration to the OVN-Kubernetes network plugin is completed and successful.
9+
As a cluster administrator, you can rollback to the OpenShift SDN from the OVN-Kubernetes network plugin using either the _offline_ migration method, or the _live_ migration method. This can only be done after the migration to the OVN-Kubernetes network plugin has successfully completed.
1010

1111
include::snippets/sdn-deprecation-statement.adoc[]
1212

1313
include::modules/nw-ovn-kubernetes-rollback.adoc[leveloffset=+1]
14+
include::modules/nw-ovn-kubernetes-rollback-live.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)