ocp4_workload_external_odf: document backingstore_pv_volumes for scaled clusters#75
Closed
prakhar1985 wants to merge 1 commit intomainfrom
Closed
ocp4_workload_external_odf: document backingstore_pv_volumes for scaled clusters#75prakhar1985 wants to merge 1 commit intomainfrom
prakhar1985 wants to merge 1 commit intomainfrom
Conversation
prakhar1985
requested review from
agonzalezrh,
fridim,
rut31337,
stencell and
wkulhanek
as code owners
prakhar1985
force-pushed
the
odf-backingstore-pv-volumes-doc
branch
5 times, most recently
from
7f96e8f to
d744274
Compare
Set ocp4_workload_external_odf_backingstore_pv_volumes to 1 (operator
default). Catalog items should override with worker node count in AgnosticV:
ocp4_workload_external_odf_backingstore_pv_volumes: "{{ worker_instance_count | int }}"
To also scale CPU/memory resources per BackingStore pod, additionally set:
ocp4_workload_external_odf_backingstore_custom_resources: true
prakhar1985
force-pushed
the
odf-backingstore-pv-volumes-doc
branch
from
d744274 to
5893156
Compare
Contributor
Author
|
Closing — changes need further discussion before proceeding. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Documents how to correctly scale ODF when clusters have more than 3 workers.
When scaling workers, both the pvPool volume count AND the per-pod BackingStore resource requests/limits need to be set. The variable `ocp4_workload_external_odf_backingstore_pv_volumes` already controls `numVolumes` (workload.yml line 133), and `ocp4_workload_external_odf_backingstore_custom_resources` triggers the resource patch (line 145). Neither are configured for scaled clusters by default.
Example usage in an AgnosticV catalog item
```yaml
ocp4_workload_external_odf_backingstore_pv_volumes: "{{ worker_instance_count | int }}"
ocp4_workload_external_odf_backingstore_custom_resources: true
ocp4_workload_external_odf_backingstore_cpu_limits: 1000m
ocp4_workload_external_odf_backingstore_cpu_requests: 800m
ocp4_workload_external_odf_backingstore_memory_limits: 4000Mi
ocp4_workload_external_odf_backingstore_memory_requests: 800Mi
ocp4_workload_external_odf_backingstore_storage_requests: 50Gi
```
Note
Tyrell's retry fix from #72 is included in this branch. No changes to workload.yml — this is documentation only.
@alberto-gonzalez — can you validate by testing with a catalog item that sets the above variables? Confirm Quay comes up healthy with the pvPool matching the worker count. Do not merge until tested.