[Lustre-devel] Lustre HSM HLD draft
aurelien.degremont at cea.fr
Thu Feb 21 07:26:07 PST 2008
I've got several wondering about some specific point in HSM
implementation and I would like your opinion about them.
This element will manage migration externally (HSM) and internally of
Lustre (space balancing?). Is the current API acceptable (specific calls
for external migration, and other ones for internal migration)? The best
way could have been to have generic call for migration, but we must also
have generic objects to describe the migration sources and destinations
and those are not simples. We finally conclude with the API presented in
the HLD document. Tell me if this is *really* a bad idea or if only
adjustments are needed.
We presented two modes of migration, explicit and implicit migrations.
The first one result of an administrative request, the second one was
triggered automatically (cache miss by example). Is that ok? (See the
doc for all details).
It seems, to support Lustre internal migration, you have planned to
implement specific Agents which will reside on OST. HSM will need
specific agent on clients. Do those two kinds of agent are acceptable ?
The current API only describe HSM-based agent. Maybe we should think of
a generic agent framework and add specialized implementations for
More information about the lustre-devel