Roadmap

This page recapitulates our plan for the future of Phobos, in order of implementation:

Project	Description	Status

| Device fair share | implement a mechanism for equal partitioning of requests between devices | ongoing |

| early locate with compatibility check | check at locate if a host has compatible devices for the media the object is on | done |

| deprecated stats | retrieve information about the number of deprecated objects on a medium | ongoing | | extent migration | migrate extents from one medium to another | ongoing | | repack/cleanup | complete deletion of an object and its extent from the system and media | ongoing | | TLC | | ongoing | | multi-library support | support multiple libraries in a single Phobos instance | ongoing | | Erasure Coding | implementation of an Erasure Coding storage layout | | | grouped put | group multiple put requests into a single one and optimize medium usage | | | auto tags | have a pool of untagged tapes that can be selected and tagged when the number of tapes of a given tag drops to 0 | | | mandatory tagging | define a set of tags that must be specified at put (manage communities of users) | | | internal HSM management | manage HSM requests from one storage tier to another | | | disaster recovery | recovering the database and information about objects and such after a failure | | | RAO implementation | take into account the Recommended Access Order on tapes | | | Server-client | allow remote commands to be executed on a Phobos node | |