Keep storage tiers » History » Version 2
Tom Clegg, 04/28/2017 12:46 AM
| 1 | 1 | Tom Clegg | h1. Keep storage tiers |
|---|---|---|---|
| 2 | |||
| 3 | 2 | Tom Clegg | Typically, an Arvados cluster has access to multiple storage devices with different cost/performance trade-offs. |
| 4 | 1 | Tom Clegg | |
| 5 | Examples: |
||
| 6 | * Local SSD |
||
| 7 | * Local HDD |
||
| 8 | * Object storage service provided by cloud vendor |
||
| 9 | * Slower or less reliable object storage service provided by same cloud vendor |
||
| 10 | 2 | Tom Clegg | |
| 11 | Users should be able to specify a minimum storage tier for each collection. Arvados should ensure that every data block referenced by a collection is stored at the specified tier _or better_. |
||
| 12 | |||
| 13 | The cluster administrator should be able to specify a default tier, and assign a tier number to each storage device. |
||
| 14 | |||
| 15 | It should be possible to configure multiple storage devices at the same tier: for example, this allows blocks to be distributed more or less uniformly across multiple cloud storage buckets for performance reasons. |