Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Devise strategy for upgrading to compatibility breaking Synapse version(s) #6443

Closed
ulope opened this issue Aug 5, 2020 · 2 comments · Fixed by raiden-network/raiden-service-bundle#187
Closed

Devise strategy for upgrading to compatibility breaking Synapse version(s) #6443

ulope opened this issue Aug 5, 2020 · 2 comments · Fixed by raiden-network/raiden-service-bundle#187
Labels
Component / Transport Transport related issues Severity / Medium State / Investigating For issues that are currently being looked into before labeling further Type / Enhancement

Comments

@ulope
Copy link
Collaborator

ulope commented Aug 5, 2020 •
edited
Loading

Abstract

In the RSB bundle and locally as a test requirement we currently still provide Synapse 1.10.1.
From the next version after that (1.11.0) onwards a backwards incompatible change of room alias semantics (MSC2432 was implemented.

#6442 upgrades to Synapse 1.18.0 and makes Raiden compatible with this change, however since we have a backwards compatibility policy for our Mainnet deployment we need a solution that doesn't cut off the existing Alderaan Raiden clients after that PR is merged.

Motivation

We need to remain backwards compatible with existing Alderaan Raiden clients.

Solution proposal

  • Upgrade most RSB Synapse servers to the new version (1.18.0)
  • Keep a couple (at least two) of RSB Synapse servers on the old version (1.10.1)
  • Maintain federation between both sets of servers
  • Change known servers list for new Raiden client releases to only contain the servers with the new version.
  • Define a cutoff point after which the old version will no longer be supported.

Backwards Compatibility

That's the point of this issue
@ulope ulope added Severity / Medium Type / Enhancement Component / Transport Transport related issues State / Investigating For issues that are currently being looked into before labeling further labels Aug 5, 2020
@ulope ulope mentioned this issue Aug 5, 2020
Merged
@ulope
Copy link
Collaborator Author

ulope commented Aug 10, 2020

See also raiden-network/raiden-service-bundle#180

ulope added a commit to ulope/raiden that referenced this issue Aug 31, 2020
@ulope
Split known servers
d047229 
Depends-on: raiden-network/raiden-service-bundle#186
Related: raiden-network#6443, raiden-network#6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.
ulope added a commit to ulope/raiden that referenced this issue Sep 18, 2020
@ulope
Split known servers
791e9aa 
Depends-on: raiden-network/raiden-service-bundle#186
Related: raiden-network#6443, raiden-network#6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.
@ulope
Copy link
Collaborator Author

ulope commented Sep 18, 2020

Will be fixed by

@ulope ulope mentioned this issue Sep 18, 2020
Merged
ulope added a commit to ulope/raiden that referenced this issue Sep 18, 2020
@ulope
Split known servers
f8120e3 
Depends-on: raiden-network/raiden-service-bundle#186
Related: raiden-network#6443, raiden-network#6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.
ulope added a commit to ulope/raiden that referenced this issue Sep 18, 2020
@ulope
Split known servers
5aab480 
Depends-on: raiden-network/raiden-service-bundle#186
Related: raiden-network#6443, raiden-network#6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.
ulope added a commit that referenced this issue Sep 21, 2020
@ulope
Split known servers
920f782 
Depends-on: raiden-network/raiden-service-bundle#186
Related: #6443, #6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.
ulope added a commit to ulope/raiden that referenced this issue Oct 12, 2020
@ulope
Split known servers
26e202b 
Depends-on: raiden-network/raiden-service-bundle#186
Related: raiden-network#6443, raiden-network#6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.

(cherry picked from commit 920f782)
ulope added a commit that referenced this issue Oct 13, 2020
@ulope
Split known servers
4427043 
Depends-on: raiden-network/raiden-service-bundle#186
Related: #6443, #6212

This splits the known servers list into an 'active' and 'all' part.

The 'active' part is read by the Raiden client and used to select a
server to use.

The 'all' part is used by the RSB as the federation whitelist.

The purpose of this is to allow new servers to be added without making
the Raiden client immediately try to use them while they are not yet
ready.

(cherry picked from commit 920f782)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component / Transport Transport related issues Severity / Medium State / Investigating For issues that are currently being looked into before labeling further Type / Enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upgrade Synapse to 1.19.1 raiden-network/raiden-service-bundle
1 participant
@ulope