-
Notifications
You must be signed in to change notification settings - Fork 14
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
add s3 service and resource plugin #40
Comments
Two things if you want to play with the S3 plugin...
Happy to leave this issue open as a feature request for the irods_demo itself. |
Right, 1) is easy but it could be made a part of the demo Compose file to minimize surprises and make it easy to follow a handful commands that don't fail. Appreciate the willingness to consider this as feature request. |
No problem. How did you find this project? You're the first one in the door... |
I've been working with parallel filesystems for a while, so I heard of iRODS a long time ago. |
Fair enough - thanks! Yes, NetApp is a consortium member, so please send us email directly if in-public isn't the right forum. |
Cool! That's probably some tech or product group, but I don't know who exactly. Anyway, I've added a MinIO container and S3 resource plugin (#42) - not sure if that's how it supposed to be done but it may save you some time. As I wrote in the comment, feel free to use whatever parts (or none at all) in own commit. Maybe it'd be nice to have the MinIO client for easy verification (
|
nice - thanks for the success copy/paste - great that it 'just worked'. yes, adding a minio container is the right answer. and we'll definitely consider if/where to install |
The MinIO service and S3 plugin have been added. Getting a resource set up automatically is not done yet, so I will leave this open. |
resource set up, and |
It's not yet available - I think the idea was to make un invasive changes for phase v1, and then decide whether and how to automate the creation of bucket and client-side S3 config. |
demobucket is now created by default in minio, and the s3 plugin is now configured to talk to that bucket. closing! |
Would it be possible to add to README.md advice on DIY for adding S3 resource plugin?
In the plugin's repo they say:
In this (containerized) scenario, would it be better to edit a Dockerfile (which one?) to deploy the plugin and which resource mode would be recommended?
I've tried building and installing inside a live container, but there's a lot of packages and deps that need to be taken care of. Perhaps editing a Dockerfile would be a better idea?
The text was updated successfully, but these errors were encountered: