INTO-CPS-Association / INTO-CPS-Association/workspace
[FEATURE] Mount S3 compatible storage on the workspace filesystem
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the feature
We want to store persistent data for the workspaces in a S3 compliant store. At the same time, our users want to be able to access this data as part of their workspace in a seamless manner, i.e. as if it was in one or more directories in their filesystem.
Therefore I want there to be a service in the workspaces that syncs their internal filesystems with one or more external object stores.
### Describe the problems your feature request solves
With this feature a bridge is established between any S3 compliant object store and the persistent directories inside the workspace.
This builds upon the work in issue #33 and the work done by [Hussein Marah](https://github.com/husseinmarah) in their [fork of the main repo](https://github.com/husseinmarah/workspace).
### Describe the solution you'd like
The folders `/workspace` and `/workspace/common` are each mapable and syncable with a respective bucket in some S3 compatible object store.
### Describe alternatives you've considered
Issue #33 has been exploring a service based on the MinIO client, while Hussein Marah's fork is based on s3fs-fuse
### Success Criterion
Checklist:
- [ ] A syncing service is present in the workspace
- [ ] All current Docker compositions support persistent storage through this feature
- [ ] Additional composistions based on the simple composition (´compose.yml`) and the full composition (`compose.traefik.secure.tls.yml) exist which sets up and integrates an S3 compliant object store.
- [ ] Documentation Updated
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.