-
Notifications
You must be signed in to change notification settings - Fork 87
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 a resolver for source images stored in S3. #257
base: development
Are you sure you want to change the base?
Conversation
@ckassel I wonder if this is useful for the work you presented at DLF? Not sure if you're the right person to ask, but maybe you could pass it on? |
Thanks, will do! On Mon, Nov 21, 2016 at 9:54 AM, Jon Stroop notifications@github.com
Carol Kassel |
@ratliff Do you have metrics regarding serving files from "local" storage vs. s3 storage? We are interested in exploring this, but concerned about s3 performance. |
@jeremyf I don't have any numbers, but I did have our Art Museum run load tests against the configuration and they were (and still are) happy with the response times. |
@ratliff I notice there is a caching layer that you incorporated. What is your caching layer for the S3 objects? Do you store them on the app server? |
Yes. I cache images in Elastic File System (basically an NFS server). I have a CloudFormation template that you can use to launch the entire stack. Let me know if you want me to e-mail it to you. (Not sure that I ever checked it into a repo.) |
@ratliff I would love the CloudFormation template. My email is jfriesen@nd.edu |
@jeremyf The repo containing the Cloud Formation template is here https://github.com/loris-imageserver/loris-cloudformation |
@ratliff Thank you! I think I have what I need for now. Trying to get a little movement on IIIF locally. |
@ratliff We might have use for an S3 resolver at Wellcome soon, so we’d be interested in getting this merged. This needs some tests and cleanup before it’s ready to go – are you interested in finishing this off, or would you be happy for me to tidy it up and merge it? |
@alexchan we would be very happy if you were to tidy this up and merge it! At NYU we've been interested in having an S3 resolver, but I haven't had time to work on it yet. |
@alexwlchan I'm no longer actively involved. I handed what I had developed over to folks in the Princeton Univ Art Museum. So, I (and probably they) would be very happy if you would do what needs to be done to merge the code. Let me know if you need any info from me in order to accomplish that. |
@ratliff Thanks for the fast reply! I’ll see how I get on, and ask if I run into any issues. |
@alexwlchan s3 support is something harvardx is interested in too. |
I written this resolver for images stored in S3. It mimics the functionality of the SimpleHTTPResolver. Requires installation of Boto3 SDK. I bet others would find this useful.
Let me know if you have questions.
--- Mark