-
Notifications
You must be signed in to change notification settings - Fork 185
Use msgrv2 always for all ODF modes(internal,external,provider) #2793
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
|
@@ -605,13 +605,11 @@ func getNetworkSpec(sc ocsv1.StorageCluster) rookCephv1.NetworkSpec { | |||
// respect both the old way and the new way for enabling HostNetwork | ||||
networkSpec.HostNetwork = networkSpec.HostNetwork || sc.Spec.HostNetwork | ||||
|
||||
// If it's not an external and not a provider cluster always require msgr2 | ||||
if !sc.Spec.AllowRemoteStorageConsumers && !sc.Spec.ExternalStorage.Enable { | ||||
if networkSpec.Connections == nil { | ||||
networkSpec.Connections = &rookCephv1.ConnectionsSpec{} | ||||
} | ||||
networkSpec.Connections.RequireMsgr2 = true | ||||
if networkSpec.Connections == nil { | ||||
networkSpec.Connections = &rookCephv1.ConnectionsSpec{} | ||||
} | ||||
// Always require msgr2 for all modes of ODF | ||||
networkSpec.Connections.RequireMsgr2 = true | ||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not sure we can blindly change that for provider mode. What happens to existing deployments? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For existing deployments the mons after the upgrade would have the v1 port still available, so there would be no problem for the existing volumes that are already mounted. For any new volumes that are created after the upgrade, the volume would use the v2 port. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @malayparida2000 I am not sure that will work out of the box, don't we need to inform the CSI running on the clients that we moved to v2? If so how do we do that in provider mode? the CSI is running on many different clusters There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. When the ODF version upgrade happens from 4.17 to 4.18 where this change will come in, The subscription channel would change for ocs-operator, which would trigger a change in the hash for the clients & would trigger a reconciliation for them based on this
When that happens the client would now get the new info from the provider cluster. That's my understanding. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||||
|
||||
return networkSpec | ||||
} | ||||
|
Uh oh!
There was an error while loading. Please reload this page.