jaeger-objectstorage
goofys
| jaeger-objectstorage | goofys | |
|---|---|---|
| 1 | 18 | |
| 51 | 5,529 | |
| - | 0.0% | |
| 6.5 | 0.0 | |
| over 2 years ago | almost 2 years ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jaeger-objectstorage
goofys
- S3 Files and the changing face of S3
-
Streaming Data from Cloud Storage with Mountpoint for Amazon S3
# install goofys\ sudo curl -Lo \\ /usr/local/bin/goofys \\ https://github.com/kahing/goofys/releases/latest/download/goofys\ sudo chmod +x /usr/local/bin/goofys # install mount-s3\ wget \\ https://s3.amazonaws.com/mountpoint-s3-release/latest/x86_64/mount-s3.deb\ sudo dpkg -i mount-s3.deb\ sudo apt-get install -f -y
-
Is Posix Outdated?
The author needs to ask themselves: in this cloud technology stack, is there POSIX involved somewhere lower down, where I can't access it? The answer is, of course, "yes". The sort of cloud storage systems described all run on top of POSIX APIs. They provide convenience (cost efficiency is more debatable) compared to the POSIX alternative, but that's because they exist at an entirely different conceptual layer (hence the presence of POSIX anyway, just buried).
Your point about surfacing a POSIX that's actually there but hidden and thus visible to low-level Amazon employees building the S3 service which makes it invisible to S3 end customers is true but isn't the the point of the article. The author is saying there are motivations for a POSIX-like api visible also the end user.
So your explanation of stack looks like 2 layers: POSIX api <-- AWS S3 built on top of that
Author's essay is actually talking about 3 layers: POSIX <-- AWS S3 <-- POSIX
That's why the blog post has the following links to POSIX-on-top-of-S3-objects :
https://github.com/s3fs-fuse/s3fs-fuse
https://github.com/kahing/goofys
https://www.cuno.io/
-
AWS Announces Open Source Mountpoint for Amazon S3
How is this different than these other solutions?
https://github.com/kahing/goofys
https://github.com/s3fs-fuse/s3fs-fuse
-
Introducing Mountpoint for Amazon S3 - A file client that translates local file system API calls to S3 object API calls like GET and LIST.
But now I ask.. why not s3fs? Is it the GPL licensing? Or even goofys that also have Apache2 licensing and seems to hit similar goals (non fully POSIX compliant)? Why build your own?
- Merge my S3 with Mac Finder Folder
-
Migrating instance to AWS GovCloud
If your 20TB is in S3, use a staging box with goofys (https://github.com/kahing/goofys) to mount the commercial S3 bucket(s) into a folder, then use s3 sync to copy to your bucket(s) in GovCloud.
- How should I go about creating a program that holds various MP4 files?
- Raft Consensus Animated
-
How do you manage large training datasets?
So, we just need to change the dataloader function a bit to make this work then. Did you try just mounting S3 using https://github.com/kahing/goofys. In this case, we need not even change the dataloader code. Not sure of the performance though.
What are some alternatives?
objstore - Go module providing unified interface and efficient clients to work with various object storage providers until like GCS, S3, Azure, SWIFT, COS and more.
s3fs - S3 Filesystem
rill - The fastest business intelligence tool for humans and agents.
s3fs-fuse - FUSE-based file system backed by Amazon S3
fake-gcs-server - Google Cloud Storage emulator & testing library.
gcsfuse - A user-space file system for interacting with Google Cloud Storage