Changes Proposal

[iwanbk]

The s3-cas project was developed as a Proof of Concept using:

• sled.rs for metadata database
• s3-server for S3 API frontend
• Basic implementation without proper CI/CD

Proposed Changes

Transform the PoC into a production-ready product with modern dependencies and proper development practices.

Core Changes Required:

1. Database Migration

• Replace sled.rs with fjall.rs (existing metadata migration is not needed) assesment: replace Sled with fjall.rs #11 Change the metadata DB  #16
  • Design new metadata schema for fjall.rs
  • Add documentation for database operations
  • Implement proper error handling
  • Add a tool to inspect DB (keysize, metadata size),
    add oject retrieval and integrity check... TBD

2. S3 Frontend Modernization

• Replace s3-server with s3s (github.com/Nugine/s3s) feat(s3s): initial work to migrate to nugine/s3s #6 Migrate all others S3 functionalities from s3s-server to nugine/s3s with the integration test #9
  • Implement S3Service trait Migrate all others S3 functionalities from s3s-server to nugine/s3s with the integration test #9
  • Add support for all required S3 operations
  • Add comprehensive tests for S3 API compatibility Migrate all others S3 functionalities from s3s-server to nugine/s3s with the integration test #9

3. Stabilize Object RefCount

Righ now the refcount is defined as a feature, but in fact it would
need to be a default setting.

• Design comprehensive failure tests to make sure that refcounts
  are NEVER too low. (There can be some data leakage, but never data loss)
• Stabilize refcount

4. CI/CD Implementation

• Setup GitHub Actions workflows chore: initial github actions and small fixes #4 add clippy integration and fix the warnings #28
• Expose deliverables in proper versions chore: initial github actions and small fixes #4

cc @delandtj

[iwanbk]

Transform the PoC into a production-ready product with modern dependencies and proper development practices.

some notes:

• Finishing this issue doesn't mean the s3-cas become production ready, this issue is more like a prequisite to the production ready version
• More tasks could be added later