Stephan Müller c76926bcd2 mgr/dashboard: Use right size in pool form ... Currently the max size is determined by the number of OSDs, which is compared with the maximum of the current crush rule. The problem with that is, that this is wrong for every crush rule that doesn't have OSDs as failure domain and that don't have the root of the cluster set as root of the crush rule. Now the crush map will be used to determine how many failure domains are really available in the cluster and how many can really be used in the end. This number now defines the maximum size you can enter. The crush detail view will now the new attribute usable_size and hide the redundant information steps, ruleset, type and rule_name. Fixes: https://tracker.ceph.com/issues/44620 Signed-off-by: Stephan Müller <smueller@suse.com>		2020-06-02 10:38:06 +02:00
..
dashboard	mgr/dashboard: Use right size in pool form	2020-06-02 10:38:06 +02:00
__init__.py
mgr_test_case.py	qa/tasks/mgr: Don't disable cephadm module	2020-05-22 11:50:50 +00:00
test_crash.py
test_dashboard.py
test_failover.py
test_insights.py
test_module_selftest.py	qa/tasks/mgr: skip test_diskprediction_local on python>=3.8	2020-05-12 11:54:23 +08:00
test_orchestrator_cli.py
test_progress.py
test_prometheus.py