https://github.com/estnafinema0/sot-3
A Dockerized S3-compatible object storage system using MinIO with enforced disk quotas, automated data eviction, and stress-testing capabilities.
https://github.com/estnafinema0/sot-3
cloud-storage distributed-systems docker docker-compose minio object-storage s3-compatible storage-quota
Last synced: about 2 months ago
JSON representation
A Dockerized S3-compatible object storage system using MinIO with enforced disk quotas, automated data eviction, and stress-testing capabilities.
- Host: GitHub
- URL: https://github.com/estnafinema0/sot-3
- Owner: estnafinema0
- Created: 2024-12-25T02:57:09.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-12-25T11:55:42.000Z (over 1 year ago)
- Last Synced: 2025-02-15T15:48:59.529Z (over 1 year ago)
- Topics: cloud-storage, distributed-systems, docker, docker-compose, minio, object-storage, s3-compatible, storage-quota
- Language: Shell
- Homepage:
- Size: 2.46 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# S3-Compatible Object Storage with MiniO
This project demonstrates how to set up an S3-compatible object storage using MinIO, configure disk space limits, enable data eviction policies, and automatically upload test data until the storage limit is reached.
Project is realised as a part of the study of "Cloud technologies" special course at the CMC university.
## See work server and cliend in one terminal
### Build and run using Docker Compose:
It will start both containers in the background.
```bash
sudo docker-compose build
```
To run the conteiners
```bash
sudo docker compose up
```
The web setups will be run it the terminal.
After started downloads of given in the client folder image at the around 350-400 looped transfer will fail, because of the Bucked quota exceed.
### Access MinIO
Open your browser at http://localhost:9000.
Login with a setted credentials:
```
MINIO_ROOT_USER: Oblaka
MINIO_ROOT_PASSWORD: OblakaPass
```
There will be shown loaded in bucket files.
## See client work and fail in two terminals
In the server folder:
```bash
sudo docker compose run --rm web
```
In the client folder:
```bash
sudo docker compose run --rm client
```
Should fail on "big" data transfer and on around 350-400 looped transfer of images
## Removing containers
When you are done testing:
```bash
sudo docker compose down
```
You should down server before each new instances ("up"'s) of contaners.