From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] HSM phase 2 HLD / Roadmap?
Date: Tue, 16 Jun 2015 15:21:58 +0000 [thread overview]
Message-ID: <D1A5987F.F7ACA%andreas.dilger@intel.com> (raw)
In-Reply-To: <55803C06.4080003@cea.fr>
I think there are a few features that would be of interest for HSM
improvement.
* optimization of RobinHood database/POSIX copytool
* better integration with DNE
* partial file restore using composite files
(http://wiki.opensfs.org/images/e/e4/LayoutEnhancementDesign_HighLevelDesig
n.pdf)
* 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 ideas
percolating in my brain.
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
On 2015/06/16, 9:08 AM, "DEGREMONT Aurelien" <aurelien.degremont@cea.fr>
wrote:
>Le 16/06/2015 17:02, Colin Faber a ?crit :
>
>
>Hi Folks,
>
>Does anyone recall if Lustre HSM phase 2 documentation or road map was
>ever produced / published anywhere?
>
>
>
>AFAICR there never was a real official content for HSM phase 2, just
>ideas/wish list. As a consequence, no road map was done.
>
>
>Aur?lien
next prev parent reply other threads:[~2015-06-16 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 15:02 [lustre-devel] HSM phase 2 HLD / Roadmap? Colin Faber
2015-06-16 15:08 ` DEGREMONT Aurelien
2015-06-16 15:10 ` Colin Faber
2015-06-16 15:21 ` Dilger, Andreas [this message]
2015-06-16 15:28 ` Patrick Farrell
2015-06-16 16:15 ` Dilger, Andreas
2015-06-17 8:08 ` LEIBOVICI Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D1A5987F.F7ACA%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.