Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Ability to configure the DAOS server via the yaml file to allow users to create tiered container.

  2. Populating directory and file content from backend tier on demand.

  3. Expose files backed by backend storage tier as read-only.

  4. Allow new files (not existing in backend storage tier) to be created in the same container. Those files won’t be written back to the backend tier.

  5. Proper error should be propagated back to the DAOS client if the backend tier is not accessible.

  6. ENOSPC should be returned to the application if the content of the backend tier could not be written into DAOS.the content of the backend tier could not be written into DAOS.

  7. The whole file is prefetched into DAOS upon access.

  8. (TBD, might be premature: Optimisations to prefetch a bunch of small files at once from backend tier).

...

Phase 1 aims at defining a baseline infrastructure that support the use case described above and provide an evolutive infrastructure to support more advance advanced use cases in subsequent phases.

...