ubicloud/prog/minio
Jeremy Evans df6c9160fb Validate minio cluster information before use
This prevents setting up clusters where minio would fail to start
on a server because one of the per-server values was 0. For example:

```ruby
Prog::Minio::MinioClusterNexus.assemble(Config.minio_service_project_id,
    "test-minio", Location::HETZNER_FSN1_ID, "minioadmin", 80, 1, 2, 1, "standard-2")
```

Results in a broken server, because it tries to use 1 drive and 2
servers. That isn't 1 pool, 2 servers per pool, and 1 drive per server
(as I assumed), it is 1 pool, 2 servers total, and 1 drive total, and
as 1/2 is 0 in Ruby, this doesn't result in a working configuration.

This adds a validation to catch this issue. I think it would better
if assemble took the per-server information, since that's what it
actually needs, but as that changes the API, it isn't included in
this commit.
2025-09-27 02:10:40 +09:00
..
minio_cluster_nexus.rb Validate minio cluster information before use 2025-09-27 02:10:40 +09:00
minio_pool_nexus.rb Use create_with_id in progs and routes 2025-08-07 02:13:08 +09:00
minio_server_nexus.rb Work around bug in endpoint for single server minio clusters 2025-09-27 02:10:40 +09:00
setup_minio.rb Set MinIO parity properly and upgrade the version 2025-09-04 11:24:46 +02:00