-
Notifications
You must be signed in to change notification settings - Fork 476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add enhancement proposal for SDN live migration #1064
Conversation
/cc @trozet @cgwalters @squeed PTAL. |
/cc @russellb |
223d158
to
fadbcfe
Compare
fb265d5
to
650b339
Compare
Inactive enhancement proposals go stale after 28d of inactivity. See https://github.com/openshift/enhancements#life-cycle for details. Mark the proposal as fresh by commenting If this proposal is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Inactive enhancement proposals go stale after 28d of inactivity. See https://github.com/openshift/enhancements#life-cycle for details. Mark the proposal as fresh by commenting If this proposal is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
5ccc533
to
6627327
Compare
6627327
to
318dfb5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved on behalf of SD Architecture as of 318dfb5
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, trozet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
/hold @pliurh in case you need more feedback. Feel free to unhold |
1400 for OVN Kubernetes and 1450 for OpenShift SDN. During the migration, this | ||
MTU mismatch would break some cross-CNI traffic. | ||
|
||
To avoid this issue, before starting the migration, users need to decrease the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is MTU migration automated or not?
This sentence suggests that it is not but there is also this one:
CNO will check the current hardware MTU and the cluster MTU to see if there is enough free space for OVN-K overlay overhead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MTU migration will be part of the live migration, so it will be automated. Let me make the sentences more clear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a clarification: it is only automated in the scope of this procedure because it doesn't contemplate the need to update the physical network MTU. This probably worth adding as well.
Signed-off-by: Peng Liu <[email protected]>
318dfb5
to
7c8bfe3
Compare
/lgtm |
/unhold |
@pliurh: 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/test-infra repository. I understand the commands that are listed here. |
For details of the CNI migration feature see the feature enhancement PR [1]. Within o/origin, there is a suite for live migration. The suite accepts one environment variable. The value of this environment variable controls which CNI we are migrating to and optionally, if we want to trigger rollback. Rollback will only start once live migration to the target CNI is complete. If the environemnt variables value is blank, live migration test will be skipped. For more info, see the o/origin live migration PR [2]. Note: enabling of eip feature tests depends on fixing a bug [3]. A bug to track this enabling has also been created [4]. [1] openshift/enhancements#1064 [2] openshift/origin#28462 [3] https://issues.redhat.com/browse/OCPBUGS-26196 [4] https://issues.redhat.com/browse/NP-884 Signed-off-by: Martin Kennelly <[email protected]>
For details of the CNI migration feature see the feature enhancement PR [1]. Within o/origin, there is a suite for live migration. The suite accepts one environment variable. The value of this environment variable controls which CNI we are migrating to and optionally, if we want to trigger rollback. Rollback will only start once live migration to the target CNI is complete. If the environemnt variables value is blank, live migration test will be skipped. For more info, see the o/origin live migration PR [2]. Note: enabling of eip feature tests depends on fixing a bug [3]. A bug to track this enabling has also been created [4]. [1] openshift/enhancements#1064 [2] openshift/origin#28462 [3] https://issues.redhat.com/browse/OCPBUGS-26196 [4] https://issues.redhat.com/browse/NP-884 Signed-off-by: Martin Kennelly <[email protected]>
For details of the CNI migration feature see the feature enhancement PR [1]. Within o/origin, there is a suite for live migration. The suite accepts one environment variable. The value of this environment variable controls which CNI we are migrating to and optionally, if we want to trigger rollback. Rollback will only start once live migration to the target CNI is complete. If the environemnt variables value is blank, live migration test will be skipped. For more info, see the o/origin live migration PR [2]. Note: enabling of eip feature tests depends on fixing a bug [3]. A bug to track this enabling has also been created [4]. [1] openshift/enhancements#1064 [2] openshift/origin#28462 [3] https://issues.redhat.com/browse/OCPBUGS-26196 [4] https://issues.redhat.com/browse/NP-884 Signed-off-by: Martin Kennelly <[email protected]>
For details of the CNI migration feature see the feature enhancement PR [1]. Within o/origin, there is a suite for live migration. The suite accepts one environment variable. The value of this environment variable controls which CNI we are migrating to and optionally, if we want to trigger rollback. Rollback will only start once live migration to the target CNI is complete. If the environemnt variables value is blank, live migration test will be skipped. For more info, see the o/origin live migration PR [2]. Note: enabling of eip feature tests depends on fixing a bug [3]. A bug to track this enabling has also been created [4]. [1] openshift/enhancements#1064 [2] openshift/origin#28462 [3] https://issues.redhat.com/browse/OCPBUGS-26196 [4] https://issues.redhat.com/browse/NP-884 Signed-off-by: Martin Kennelly <[email protected]>
Signed-off-by: Peng Liu [email protected]