This repository was archived by the owner on Jan 20, 2025. It is now read-only.
barman/clients: Storj cloud walarchive proof of concept#1
Open
ifraixedes wants to merge 2 commits intomainfrom
Open
barman/clients: Storj cloud walarchive proof of concept#1ifraixedes wants to merge 2 commits intomainfrom
ifraixedes wants to merge 2 commits intomainfrom
Conversation
Create a proof of concept of creating a CloudInterface class for Storj decentralized object storage. The new class doesn't implement all the methods than the original CloudInterface only the ones used by the barman/client/cloud_walarlchive.py tool because this is a proof of concept to see how we could adapt the barman client tools just implementing a new CloudIterface class.
Create a new client cloud walarchive tool for using Storj network. This is a copy of the orignal barman/clients/cloud_walarchive.py file with the minimal modifications for using the StorjCloudInterface class and verify that the proof of concept works. In a proper implementation the tools should be the same and have some command line arguments to specify which cloud provider to use (Storj or S3).
Contributor
|
@ifraixedes Do we want to get this merged eventually? |
Member
Author
|
We could, it was a proof-of-concept to see what we have to change in Barman scripts for working with Storj as it works with S3. Nonetheless, I'm aware that our python-bindings were going to suffer a general overhaul, so it may not work anymore once that happens. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following
The new class doesn't implement all the methods than the original CloudInterface only the ones used by the barman/client/cloud_walarlchive.py tool because this is a proof of concept to see how we could adapt the barman client tools just implementing a new CloudIterface class.
This is a copy of the original barman/clients/cloud_walarchive.py file with the minimal modifications for using the StorjCloudInterface class and verify that the proof of concept works.
In a proper implementation, the tools should be the same and have some command-line arguments to specify which cloud provider to use (Storj or S3).
There is no manual test, but I tested in my local using a Tardigrade access and a WAL file generated by a PostgreSQL running in my local and the file was upload to it.