-
Notifications
You must be signed in to change notification settings - Fork 4
Roadmap
Yoann Valeri edited this page Mar 15, 2023
·
8 revisions
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 |
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 | design |
Extent migration | migrate extents from one medium to another | design |
Repack/cleanup | complete deletion of an object and its extent from the system and media | design |
Tape Library Controller | controller for interactions with a tape library | design |
Multi-library support | support multiple libraries in a single Phobos instance | not started |
Erasure Coding | implementation of an Erasure Coding storage layout | not started |
Grouped put | group multiple put requests into a single one and optimize medium usage | not started |
Auto tags | have a pool of untagged tapes that can be selected and tagged when the number of available/usable tapes of a given tag drops to 0 | not started |
Mandatory tagging | define a set of tags that must be specified at put (manage communities of users) | not started |
Internal HSM management | manage HSM requests from one storage tier to another | not started |
Disaster recovery | recovering the database and information about objects and such after a failure | not started |
RAO implementation | take into account the Recommended Access Order on tapes | not started |
Server-client | allow remote commands to be executed on a Phobos node | not started |