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.

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

Proposal: Sync notifications adapter #82

Open
Zetanova opened this issue Jan 7, 2025 · 3 comments
Open

Proposal: Sync notifications adapter #82

Zetanova opened this issue Jan 7, 2025 · 3 comments

Comments

@Zetanova
Copy link

Zetanova commented Jan 7, 2025

The current Simpleblob interface for the storage backend can be paired with an Simplenotify interface.

The new interface could abstract away the current S3 storage_poll_interval mechanism
and maybe extended later by a MQTT implementation.

This would make it possible that the producer would publish the URI of the new snapshot to mqtt
and the consuming nodes would use the URI (can be presigned) to get the new snapshot.

@kpfleming
Copy link

AWS S3 and MinIO support 'bucket event' notifications already, which can be delivered in a variety of ways. It might be better to leverage that instead of creating a mechanism that risks inconsistency with the actual storage.

@Zetanova
Copy link
Author

Zetanova commented Jan 7, 2025

Storj does not and even witht he bucket event feature from aws or minio, LS does not utilize it.

@Zetanova
Copy link
Author

Zetanova commented Jan 9, 2025

What a dedicated pub-sub call would enable is to use the FileStorage backend.

LN could use the FileStorage backend and to drop the snapshots without any changes to the current implementation into a directory and then generate an URL provided with with an simple template from the config.

The directory could be a public folder of a webserver like apache secured with basic-auth
and the url could include the auth args.
The receiver could then simple use it to directly download the snapshot over a http-get.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants