doc: clarify upmap balancer documentation

In https://github.com/ceph/ceph/pull/51499, some language was added
that refers to the upmap balancer as the "capacity" balancer,
but we don't want to insinuate that there is anything "new" that was
added or changed. It should be clear that this section refers to the
existing upmap balancer, which has existed for several releases.

Signed-off-by: Laura Flores <lflores@redhat.com>
(cherry picked from commit d378c06a93d4e69491eaad17273b36f69a895ba8)

diff --git a/doc/dev/balancer-design.rst b/doc/dev/balancer-design.rst
index f101185fef5c8ca155be89801c5a2ebf982fb2c1..684d163528f3ff6998664dec05eda4a18c992ef3 100644 (file)
--- a/doc/dev/balancer-design.rst
+++ b/doc/dev/balancer-design.rst
@@ -9,7 +9,7 @@ In distributed storage systems like Ceph, it is important to balance write and r
 and replication of data in a cluster, while read balancing ensures quick access and retrieval of data in a cluster. Both types of balancing are important
 in distributed systems for different reasons.
 
-Capacity (Upmap) Balancing
+Upmap Balancing
 ==========================
 
 Importance in a Cluster

diff --git a/doc/rados/operations/upmap.rst b/doc/rados/operations/upmap.rst
index bfa634954dfc5551e56a7ec62e537ffb1bda0ccf..8541680d87503f01c3c2f9aa160a5aa204c106a3 100644 (file)
--- a/doc/rados/operations/upmap.rst
+++ b/doc/rados/operations/upmap.rst
@@ -1,7 +1,7 @@
 .. _upmap:
 
 =======================================
-Operating the Capacity (Upmap) Balancer
+Using pg-upmap
 =======================================
 
 In Luminous v12.2.z and later releases, there is a *pg-upmap* exception table