-
Bug
-
Resolution: Unresolved
-
Critical
-
odf-4.14
-
None
+++ This bug was initially created as a clone of Bug #2232384 +++
- Describe the issue:
We need to document the steps to modify the OSD pod resources persistently.
We have already documented the steps to change it for other pods like
mgr, mds, rgw in here:
- Describe the task you were trying to accomplish:
Increase/decrease OSD pod memory and CPU limits and requests
- Suggestions for improvement:
Include the steps for MON and OSDs from this KCS:
https://access.redhat.com/solutions/6959127
— Additional comment from Karun Josy on 2023-08-16 15:07:35 UTC —
For MONs, as I understand the steps are the same for the other daemons.
But for OSDs, the steps are a bit different.
For reference:
https://access.redhat.com/solutions/6959127
https://bugzilla.redhat.com/show_bug.cgi?id=2160294
We need to get ack from the Engineering team and get this QE tested.
— Additional comment from RHEL Program Management on 2023-08-16 15:07:44 UTC —
This bug having no release flag set previously, is now set with release flag 'odf‑4.14.0' to '?', and so is being proposed to be fixed at the ODF 4.14.0 release. Note that the 3 Acks (pm_ack, devel_ack, qa_ack), if any previously set while release flag was missing, have now been reset since the Acks are to be set against a release flag.
— Additional comment from Anjana Suparna Sriram on 2023-11-20 12:44:37 UTC —
@etamir@redhat.com @ebenahar@redhat.com @muagarwa@redhat.com – Kindly review this bug and let us know if the KCS article should be tested and included in the docs.
— Additional comment from Eran Tamir on 2024-01-08 11:16:55 UTC —
We currently have https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.14/html/troubleshooting_openshift_data_foundation/changing-resources-for-the-openshift-data-foundation-components_rhodf in the documents. IMHO, It would make sense to merge the KCS content into this section.
— Additional comment from Elad on 2024-01-08 13:17:34 UTC —
Agreed with Eran
— Additional comment from Manny on 2024-05-16 03:37:29 UTC —
Eran and Mudit, please see KCS #7069646, (https://access.redhat.com/solutions/7069646)
We really need better Docs for this
Best regards,
Manny
— Additional comment from Eran Tamir on 2024-05-16 05:19:51 UTC —
Updated the priority which wasn't urgent for some reason.
@asriram@redhat.com when can we get the OSD section https://access.redhat.com/solutions/6959127#:~:text=For%20osd%20pods%2C%20we%20need%20to%20edit%20resources%20on%20the%20storageDeviceSets%20section. into the docs sooner than later?
— Additional comment from Kusuma on 2024-05-20 06:51:21 UTC —
Hi @Karun and @eran.tamir
I have updated the doc as suggested. Can you please review?
Here is the preview link:
https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.13/html-single/troubleshooting_openshift_data_foundation/index?lb_target=preview#changing_the_cpu_and_memory_resources_for_osds
— Additional comment from Karun Josy on 2024-05-21 09:15:54 UTC —
Hi Kusuma,
It looks good, thanks!
— Additional comment from Eran Tamir on 2024-05-22 04:30:19 UTC —
LGTM, thanks!
- is blocked by
-
DFBUGS-71 [2282289] [GSS] [rook-ceph] Document how to change CPU/Memory for MON and OSD pods permanently
- New
-
DFBUGS-549 [2232384] [GSS] [rook-ceph] Document how to change CPU/Memory for MON and OSD pods permanently
- ON_QA