tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Auto-upgrade from Foolscap to HTTP storage protocol #4043

New issue
Closed
opened 2023-07-06 15:18:15 +00:00 by itamarst · 4 comments
itamarst commented 2023-07-06 15:18:15 +00:00
Owner
Copy link

Ideally, a client would not rely on an update from the introducer to give it the GBS NURL for the updated storage server. Therefore, when an updated client connects to a storage server using Foolscap, it should request the server's version information.

If this information indicates that GBS is supported then the client should cache this GBS information. On subsequent connection attempts, it should make use of this GBS information.

Ideally, a client would not rely on an update from the introducer to give it the GBS NURL for the updated storage server. Therefore, when an updated client connects to a storage server using Foolscap, it should request the server's version information. If this information indicates that GBS is supported then the client should cache this GBS information. On subsequent connection attempts, it should make use of this GBS information.
tahoe-lafs added the
unknown
normal
task
n/a
 labels 2023-07-06 15:18:15 +00:00
tahoe-lafs added this to the HTTP Storage Protocol milestone 2023-07-06 15:18:15 +00:00
itamarst commented 2023-07-06 16:06:45 +00:00
Author
Owner
Copy link

Implementation:

  • The server's version message gets the NURLs added.
  • Clients are OK with NURLs being missing.
  • If the NURL is there and the client is configured to support HTTP, it gets rid of Foolscap and switches to HTTP.
Implementation: * The server's version message gets the NURLs added. * Clients are OK with NURLs being missing. * If the NURL is there _and_ the client is configured to support HTTP, it gets rid of Foolscap and switches to HTTP.
itamarst commented 2023-07-07 15:18:10 +00:00
Author
Owner
Copy link

Initial implementation sketch has FoolscapStorageServer's remotely exposed get_version() return the NURLs if known. However... one can imagine the HTTP server's NURLs changing, and right now that is never communicated to the client and the client never knows.

With a little tweaking of the design, the same Foolscap to HTTP upgrade code can also change the NURLs in a HTTP-only client, so probably going to go down that route.

Initial implementation sketch has [FoolscapStorageServer](wiki/FoolscapStorageServer)'s remotely exposed `get_version()` return the NURLs if known. However... one can imagine the HTTP server's NURLs changing, and right now that is never communicated to the client and the client never knows. With a little tweaking of the design, the same Foolscap to HTTP upgrade code can also change the NURLs in a HTTP-only client, so probably going to go down that route.
itamarst commented 2023-07-07 15:48:45 +00:00
Author
Owner
Copy link

Fields that are in the announcement that get_version() probably doesn't need but might:

  1. The node nickname
  2. permutation-seed-base32
Fields that are in the announcement that `get_version()` _probably_ doesn't need but might: 1. The node `nickname` 2. `permutation-seed-base32`
itamarst commented 2023-07-19 16:36:42 +00:00
Author
Owner
Copy link

In the end we decided to abandon this, and just rely on introducer or situation-specific upgrade code.

In the end we decided to abandon this, and just rely on introducer or situation-specific upgrade code.
tahoe-lafs added the
wontfix
 label 2023-07-19 16:36:42 +00:00
itamarst closed this issue 2023-07-19 16:36:42 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
HTTP Storage Protocol
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#4043
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?