1 / 17

P2N: Cloud Control

P2N: Cloud Control. David Tarrant davetaz@ecs.soton.ac.uk Ben O’Steen benjamin.osteen@ouls.ox.ac.uk. Problem. Everyone loves the cloud No one in this room would use it as their primary storage. Would anyone use it as a long term preservation storage solution?. More Questions.

kaethe
Download Presentation

P2N: Cloud Control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. P2N: Cloud Control David Tarrant davetaz@ecs.soton.ac.uk Ben O’Steen benjamin.osteen@ouls.ox.ac.uk

  2. Problem • Everyone loves the cloud • No one in this room would use it as their primary storage. • Would anyone use it as a long term preservation storage solution?

  3. More Questions • Does the cloud do backup/replication/multi-site replication? • Where are my files stored (geographically)? • What is the long term pricing strategy of the cloud?

  4. Influences • Simplistic Cloud API • High resilience and distribution of resources • Transparent Expansion • Low Barrier to Entry

  5. The API • Amazon S3 • PUT, GET, POST, HEAD, DELETE • HTTP has all the tools we need!

  6. High Resilience & Distribution • Erasing coding (Honeycomb & RAID) • More efficient than replication • Resilience of Bit Torrent • Nodes in the network are geographic aware

  7. Transparent Expansion • Nodes can be added to the network arbitrarily • Network re-distributes data for even spread

  8. Low Barrier to Entry • Provide a node • Full machine • Spare space on an existing machine

  9. The P2N N1 N2 N3 N4 N5 N6

  10. The P2N N N1 N2 N3 N4 N5 N6

  11. The P2N N N1 N2 N3 N4 N5 N6

  12. The P2N Single Point of Failure? N N N1 N2 N3 N4 N5 N6

  13. The P2N Single Point of Failure? N2 N1 N3 N4 N5 N6

  14. Institutional Distribution N4 N1 N5 N2 N6 N3

  15. Flexability • Object level granularity • Basic metadata support (through POST, HEAD) • Object reporting, available via HEAD (single object) or GET (network report) • Extensions to S3 API without breaking core functionality.

  16. Progress so far • Feasibility study has been done • Now re-modularising the core • P2N1 – Localised Network (Spare space) • P2N2 – Thumper Network (200Tb+)

  17. Thank-YouP2N: Cloud Control David Tarrant davetaz@ecs.soton.ac.uk Ben O’Steen benjamin.osteen@ouls.ox.ac.uk Preserv .org.uk Repository Preservation and Interoperability

More Related