The charm can now set osd_memory_target, but it's not per device class
or type by the nature of how the charm works. Resetting
osd_memory_target always when osd_memory_target is not passed over the
relation is a bit risky behavior since operators may have set
osd_memory_target by hand with `ceph config` command out side of the
charm. Let's be less disruptive on the charm upgrade.
Reviewed: https:/ /review. opendev. org/c/openstack /charm- ceph-mon/ +/886254 /opendev. org/openstack/ charm-ceph- mon/commit/ b31de1f027b32fa 2ebe8ab62756819 de466bbbf2
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit b31de1f027b32fa 2ebe8ab62756819 de466bbbf2
Author: Nobuto Murata <email address hidden>
Date: Fri Jun 16 21:21:39 2023 +0900
Don't clear osd_memory_target unconditionally
The charm can now set osd_memory_target, but it's not per device class memory_ target always when osd_memory_target is not passed over the memory_ target by hand with `ceph config` command out side of the
or type by the nature of how the charm works. Resetting
osd_
relation is a bit risky behavior since operators may have set
osd_
charm. Let's be less disruptive on the charm upgrade.
Closes-Bug: #1934143 ebdbc9571d153aa 6206c85a067
Change-Id: I34dd33e54193a9