We should show the user what the size of the device will be after lvm
creates a pv out of it. This way there isn't a discrepency between the
sizes that are reported to the user and what is actually created.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
This will give us the size lvm should report because it takes into
account the 1GB physical extent size we set.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
We know with a mixed type scenario the device used for data will be used
at 100% capacity. This means we do not need to be explict when asking
for the size of the data lvs, which avoids rounding errors with very
small device sizes.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
The self.use_large_block_db property was never getting set because
the block in compute was never called as block_db_size was reset in
validate if it was 0. We needed to set self.use_large_block_db in
validate instead of compute.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
This allows us to create larger lvs than the default of 4m
and is easier to reason about when sizing the lvs as everythign is
reported as GBs.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
In the batch command use extents instead of size when creating lvs. This
gives a more precise size and avoids rounding errors.
Signed-off-by: Andrew Schoen <aschoen@redhat.com>
totals where USED is space allocated for object keeping while RAW_USED
also includes space allocated/reserved for internal purposes, e.g.
DB/WAL or journal.
Signed-off-by: Igor Fedotv <ifedotov@suse.com>
Fixes: https://tracker.ceph.com/issues/22159
Fixes: https://tracker.ceph.com/issues/20870
This adds more parameters to estimate allocation granularity overhead and compression
effectiveness. RAW_USED column has been removed. USED column reflects
amount of space allocated for a pool at all replicas. Including
allocaction granularity overhead and taking ompression savings and
object content gaps into account.
Following columns were appended:
* STORED - approximation of bytes users've actually stored in a
pool, i.e netto data amount without compression, allocation and
other overheads (not applicable for 'rados df').
* USED COMPR - amount of bytes allocated to store compressed data, i.e.
compressed data plus allocation/replication overhead.
* UNDER COMPR - amount of data(icluding repicated one) passed through
compression and stored in that form.
Signed-off-by: Igor Fedotov <ifedotov@suse.com>
Notable changes:
* pool statistics collection has been changed to track actual allocated
store space instead of previous object logical sizes summation.
* 'ceph/rados df' report total space(over all replicas) allocated for a pool under "USED" column.
* "RAW USED" column removed from 'ceph df detail' report
Signed-off-by: Igor Fedotov <ifedotov@suse.com>
mgr/dashboard: add profiles to set cluster's rebuild performance
Reviewed-by: Tiago Melo <tmelo@suse.com>
Reviewed-by: Sebastian Krah <skrah@suse.com>
Reviewed-by: Patrick Nawracay <pnawracay@suse.com>
The validation fails to allow dots in pool names and as such, it wasn't
allowed to create or rename pools with dots in their names.
Fixes: https://tracker.ceph.com/issues/37534
Signed-off-by: Patrick Nawracay <pnawracay@suse.com>
