Skip to main content

CEDARS server storage strategy & future growth management

Discuss our approach to managing CET run storage and planning for future growth.

Key points to consider:

  • Current approach: All CET runs (inputs and outputs) are currently stored indefinitely.

  • Problem: This leads to increasing storage demands.


Discussion points:

  1. Should we remove test runs after a certain period?

  2. Partial deletion:

    • Should we keep inputs only and delete outputs after a period?

    • Note: CET versions change, which may make old inputs unusable for reruns or audits.

    • Should we apply retention policies only to community users while keeping full data for PAs?

  3. Position on file storage:

    • Reinforce that users are expected to track and store files internally.

    • CET is not intended to act as a long-term file repository.

This request was merged into another request

No comments yet

Be the first to share your thoughts.