A couple of quick questions for Fedora admins using Amazon Web Services
(AWS):
1. What are the real memory requirements of Fedora, excluding ingest? How do
these change when Fedora is ingesting new materials? (Bonus question: If
ingest is the memory hog, any way to launch a special "ingest" Fedora
instance that would process new materials, place the ingested materials in
appropriate location(s), pass on metadata, write log, and uninstantiate?
That would let us take advantage of AWS for ingest without needing a massive
server instance running Fedora the rest of the time
2. Apparently Fedora currently only works with Amazon's EBS for storing
objects right now. This is an issue, since EBS is not considered "permanent"
storage (Amazon notes a failure rate between 1/100 and 1/1000 and highly
recommends storing a backup of the instance on S3) What to do?
3. For ingesting large amounts of data, one can use Amazon's import/export
service. We would send Amazon a hard disk with our data and they upload the
data to the S3 bucket of our choice. Right. S3, again. Anyone have any
experience with this? Duracloud folks, what are y'all doing?
Thanks,
Ari
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
