The only thing I can think of for the actual charm in this bug would be sane defaults or "required config" with no default.
Unfortunately, this specific client's use-case is very odd, but the ultimate issue is that given the size of the build (9 hosts, 3 replicas, 20 disks each) it should have never had a partition-power of 8.
not sure if you could set that to auto and require population of num_machines and num_disks or some other way to safeguard against not thinking about this setting that's only able to be set once for a given swift installation.
Maybe make it something set by an action like "initialize rings" that takes in non-defaulted arguments only?
james-page:
The only thing I can think of for the actual charm in this bug would be sane defaults or "required config" with no default.
Unfortunately, this specific client's use-case is very odd, but the ultimate issue is that given the size of the build (9 hosts, 3 replicas, 20 disks each) it should have never had a partition-power of 8.
not sure if you could set that to auto and require population of num_machines and num_disks or some other way to safeguard against not thinking about this setting that's only able to be set once for a given swift installation.
Maybe make it something set by an action like "initialize rings" that takes in non-defaulted arguments only?