[lustre-devel] HSM phase 2 HLD / Roadmap?
andreas.dilger at intel.com
Tue Jun 16 09:15:09 PDT 2015
On 2015/06/16, 9:28 AM, "Patrick Farrell" <paf at cray.com> wrote:
>Could you expound on "Better integration with DNE"? I'm not immediately
>clear on what that might mean.
I was thinking that the current DNE support is still using a single RBH
database fed by multiple ChangeLogs (one from each MDT), which doesn't
scale very well. That said, I guess it would be possible to have a single
parallel MySQL database that scales horizontally, so the scaling would be
independent of the number of MDTs.
Maybe this one should be dropped from the list, or just be considered part
of the "optimize RBH database".
>On 06/16/2015 10:21 AM, Dilger, Andreas wrote:
>> I think there are a few features that would be of interest for HSM
>> * optimization of RobinHood database/POSIX copytool
>> * better integration with DNE
>> * partial file restore using composite files
>> * change HSM to use LOV EA layout instead of dedicated xattr
>> * allowing a larger HSM archive ID (e.g. 128-bit UUID) so it can be
>> used as the primary archive identifier instead of Lustre FID
>> * archive/restore of directory trees from the MDT as tarballs
>> * allow release/restore of space from the MDT
>> * would be needed for handling Data-on-MDT files
>> Note that we don't have any plans to work on this, just listing some
>> percolating in my brain.
>> Cheers, Andreas
>lustre-devel mailing list
>lustre-devel at lists.lustre.org
Lustre Software Architect
Intel High Performance Data Division
More information about the lustre-devel