NDSA:Cloud Presentations: Difference between revisions

From DLF Wiki
← Older edit
Trow (talk | contribs)
298 edits
→‎Responses to questions: link to MetaArchive page
Nowviskie (talk | contribs)
Administrators, Bots, Bureaucrats, Check users, nuke, Administrators
365 edits
adding logo
 
(33 intermediate revisions by 10 users not shown)
Line 1: Line 1:
[[File:NDSA Logo.png|thumb]]
In each case we would want to identify who would present, who will contact them. Then when they will present.  
In each case we would want to identify who would present, who will contact them. Then when they will present.  


Line 25: Line 26:
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice
# What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice
==Questions for Member Institution Implementations of Large Scale Storage Architectures==
#What is the particular preservation goal or challenge you need to accomplish? (for example, re-use, public access, internal access, legal mandate, etc.)
#What large scale storage or cloud technologies are you using to meet that challenge? Further, which service providers or tools did you consider and how did you make your choice?
#Specifically, what kind of materials are you preserving (text, data sets, images, moving images, web pages, etc.)
#How big is your collection? (In terms of number of objects and storage space required)
#What are your performance requirements?
#What storage media have you elected to use? (Disk, Tape, etc)
#What do you think the key advantages of the system you use?
#What do you think are the key problems or disadvantages your system present?
#What important principles informed your decision about the particular tool or service you chose to use?
#How frequently do you migrate from one system to another?
# What characteristics of the storage system(s) you use do you feel are particularly well-suited to long-term digital preservation? (High levels of redundancy/resiliency, internal checksumming capabilities, automated tape refresh, etc)
# What functionality or processes have you developed to augment your storage systems in order to meet preservation goals? (Periodic checksum validation, limited human access or novel use of permissions schemes)
# Are there tough requirements for digital preservation, e.g. TRAC certification, that you wish were more readily handled by your storage system?


===Responses to questions===
===Responses to questions===
====iRODS====
====[[NDSA:iRODS]] direct responses====
# ...


Other general notes:
Other general notes:
Line 49: Line 34:
* [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.
* [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.


====[[NDSA:DuraCloud]]====
====[[NDSA:DuraCloud]] direct responses====
# ...
 
Other general notes:
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 cloud storage service by Duracloud.
* [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 cloud storage service by Duracloud.


====[[NDSA:MetaArchive/GDDP]]====
====[[NDSA:MetaArchive/GDDP]] direct responses====
# ...
 
Other general notes:
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.
* [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====
# ...
====MicroSoft Azure====
# ...
====Amazon S3/EC2====
# ...
==General Concerns==
# confidential data
# encrypted data
# auditing
# preservation risks
# legal compliance
# ...


==Solution Models and Environments==
==Solution Models and Environments==
Line 93: Line 60:
|-
|-
|iRODS
|iRODS
|
|Offered as Service
|
|Deployed Locally
|
|Opensource
|
|Authentication Scheme
|
|Ingest Mechanism
|
|Export Mechanism
|
|Integrity/Validation Mechanism
|
|Replication Mechanism
|
|Content Administration Model (Federated, etc.)
|
|Tiering Support
|Certifications
|-
|-
|DuraCloud
|DuraCloud
|
|yes
|
|yes
|
|yes (Apache2)
|
|Basic Auth
|
|1:web-ui, 2:client-side utility, 3:REST-API
|
|1:web-ui, 2:client-side utility, 3:REST-API
|
|Checksum verified on ingest. On-demand checksum verification service.
|
|Built-in support for cross-cloud replication.
|
|Local
|
|No
|-
|-
|MetaArchive/GDDP
|MetaArchive/GDDP
|
|Mixed - PLN service layer on top of local LOCKSS nodes
|
|Mixed - PLN service layer on top of local LOCKSS nodes
|
|No
|
|IP-based
|
|LOCKSS harvesting plugins
|
|LOCKSS web proxy
|
|LOCKSS distributed integrity checking
|
|LOCKSS P2P
|
|Single superuser across all nodes
|
|No
|-
|-
|Chronopolis
|Chronopolis
|
|Yes
|
|No
|
|No
|
|SRB/Irods based
|
|SRB/Irods based
|
|SRB/Irods based
|
|Local checksums
|
|SRB/Irods
|
|Single superuser
|
|No
|-
|-
|Microsoft Azure
|Microsoft Azure
|
|Yes
|
|No
|
|No
|
|Multiple
|
| .Net/WIF
|
| Multiple APIs, .Net
|
|Not known/propietary
|
|Not known/propietary
|
|Single super user
|
|Not known/propietary
|-
|-
|Amazon S3/EC2
|Amazon S3/EC2
|
|Yes
|
|No
|
|Opensource
|
|Multiple, including certs; proprietary / limited delegation model
|
|Restful API's
|
|Restful API's
|
|Proprietary
|
|Proprietary
|
|Single superuser
|
|Yes
|-
|DVN/Safearchive
|Yes
|Yes
|Opensource
|Basic Auth/IP
|Proprietary UI/Batch UI/LOCKSS harvesting plugins
|OAI/Lockss harvesting/proprietary
|LOCKS distributed integrity checks with additional TRAC auditing layer
|LOCKS with additional TRAC-based provisioning layer
|Federated & distributed
|No
|-
|-
|}
|}

Latest revision as of 16:59, 29 November 2016

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.

Presentation Schedule and Slides

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

People/Projects to Contact

  • Chronopolis (Mike Smorul will contact)
  • Open questions from the Educopia Guide to Distributed Digital Preservation
  • Commercial providers? (Who specifically would we want here? Please add them.)
    • Azure (Leslie to contact)
    • Amazon (Who will contact?)

General Questions for Cloud Service Presenters

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

  1. What sort of use cases is your system designed to support? What doesn't this support?
  2. What preservation standards would your system support?
  3. What resources are required to support a solution implemented in your environment?
  4. What infrastructure do you rely on?
  5. How can your system impact digital preservation activities?
  6. If we put data in your system today what systems and processes are in place so that we can get it back 10 years from now? (Take for granted a sophisticated audience that knows about multiple copies etc.)
  7. What types of materials does your system handle? (documents, audio files, video file, stills, data sets, etc) And give examples of those types in practice

Responses to questions

NDSA:iRODS direct responses

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.

NDSA:DuraCloud direct responses

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 cloud storage service by Duracloud.

NDSA:MetaArchive/GDDP direct responses

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.


Solution Models and Environments

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 Offered as Service Deployed Locally Opensource Authentication Scheme Ingest Mechanism Export Mechanism Integrity/Validation Mechanism Replication Mechanism Content Administration Model (Federated, etc.) Tiering Support Certifications
DuraCloud yes yes yes (Apache2) Basic Auth 1:web-ui, 2:client-side utility, 3:REST-API 1:web-ui, 2:client-side utility, 3:REST-API Checksum verified on ingest. On-demand checksum verification service. Built-in support for cross-cloud replication. Local No
MetaArchive/GDDP Mixed - PLN service layer on top of local LOCKSS nodes Mixed - PLN service layer on top of local LOCKSS nodes No IP-based LOCKSS harvesting plugins LOCKSS web proxy LOCKSS distributed integrity checking LOCKSS P2P Single superuser across all nodes No
Chronopolis Yes No No SRB/Irods based SRB/Irods based SRB/Irods based Local checksums SRB/Irods Single superuser No
Microsoft Azure Yes No No Multiple .Net/WIF Multiple APIs, .Net Not known/propietary Not known/propietary Single super user Not known/propietary
Amazon S3/EC2 Yes No Opensource Multiple, including certs; proprietary / limited delegation model Restful API's Restful API's Proprietary Proprietary Single superuser Yes
DVN/Safearchive Yes Yes Opensource Basic Auth/IP Proprietary UI/Batch UI/LOCKSS harvesting plugins OAI/Lockss harvesting/proprietary LOCKS distributed integrity checks with additional TRAC auditing layer LOCKS with additional TRAC-based provisioning layer Federated & distributed No
Retrieved from "https://wiki.diglib.org/index.php?title=NDSA:Cloud_Presentations&oldid=7975"