NDSA:Cloud Presentations: Difference between revisions

Revision as of 16:22, 18 March 2011

In each case we would want to identify who would present, who will contact them. Then when they will present.

From there we can include specific questions we would like them to respond to.

Once we start scheduling presenters we will keep a list of the talks here.

Feb 1, Tues, 1:00 EST call with iRods Reagan Moore (presentation)
Feb 14, Monday, 11:00 EST call with Duracloud
Feb 17, Thurs, 11:00 EST call with MetaArchive/GDDP Katherine Skinner, Matt Schultz and Martin Halbert

DuraCloud/Duraspace (Leslie to contact)
Chronopolis (Mike Smorul will contact)
Open questions from the Educopia Guide to Distributed Digital Preservation http://www.metaarchive.org/GDDP (Martin will contact)
Irods: Reagan Moore, 2/1/2011 see slides: NIAID.ppt
Commercial providers? (Who specifically would we want here? Please add them.)
- Azure (Leslie to contact)
- Amazon (Who will contact?)

Here we are working on a set of general questions for presenters to develop talks around.

What sort of use cases is your system designed to support? What doesn't this support?
What preservation strategies would your system support?
What preservation standards would your system support?
What resources are required to support a solution implemented in your environment
What infrastructure do you rely on?
How can the cloud environment impact digital preservation activities?
If we put data in your system today what systems and processes are in place so that we can get it back 50 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)

Other general notes:

[Snavely] The need for each storage target to support a specific set of operations, and consistently with other storage targets, seems like a risk that comes along with the elegant abstraction that iRODS provides. Clear specifications help mitigate this risk.

Other general notes:

[Snavely] Treatment of cloud provider is generally as a black box, without a strong sense of actual reliability of underlying storage systems. Cloud providers tend to promise checksum validation of contents, but recourse if validation fails was unknown (right?). Additional checksum validation has been augmented on top of service by Duracloud.

Other general notes:

[Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.

Name	Offered as Service	Deployed Locally	Opensource	Authentication Scheme	Ingest Mechanism	Export Mechanism	Integrity/Validation Mechanism	Replication Mechanism	Administration Model (Federated, etc.)	Tiering Support
iRODS
DuraCloud
MetaArchive/GDDP
Chronopolis
Microsoft Azure
Amazon S3/EC2

@@ Line 46: / Line 46: @@
 ====MetaArchive/GDDP====
 # ...
+Other general notes:
+* [Snavely] Built on LOCKSS, so data integrity assurances are provided by robust networked software model augmented to commodity hardware and storage. Federated nature provides integrity assurance but also a lack of central control in that the accidental loss of multiple caches is unlikely but e.g. scheduled maintenance or upgrades could coincidentally collide.
 ====Chronopolis====
 # ...