Hi,
I'm not sure I understand what your interpretation is.
If you have 30 OSDs each with 1TB you'll end up with 30TB available
(raw) space, no matter if those OSDs are spread across 3 or 10 hosts.
The crush rules you define determine how many replicas are going to be
distributed across your O
Ah, this sentence in the docs I've overlooked before:
When you deploy OSDs they are automatically placed within the CRUSH map
under a host node named with the hostname for the host they are running on.
This, combined with the default CRUSH failure domain, ensures that replicas
or erasure code shar
