Bug 2385960
| Summary: | QOS config not supported on nfs orch create | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Bipin Kunal <bkunal> |
| Component: | Cephadm | Assignee: | Shweta Bhosale <shbhosal> |
| Status: | CLOSED ERRATA | QA Contact: | Manish Singh <manising> |
| Severity: | medium | Docs Contact: | Rivka Pollack <rpollack> |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | adking, akane, ben.kern, bkunal, cephqe-warriors, deepatil, jcaratza, kkeithle, mobisht, msaini, nchillar, radhika.chirra, rpollack, shbhosal, tserlin |
| Target Milestone: | --- | ||
| Target Release: | 9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-20.1.0-14 | Doc Type: | Enhancement |
| Doc Text: |
Feature: Enable NFS QoS while NFS cluster creation
Reason: Earlier user can configure QoS only once nfs cluster is create. NOw user can enable it while creating NFS cluster
Result:
To configure QOS while NFS cluster creation, Spec file will have cluster_qos_config field with value dict. The cluster_qos_config block will look like the following
service_type: nfs
service_id: mynfs1
placement:
count: 3
spec:
cluster_qos_config:
enable_qos: bool
enable_bw_control: bool
combined_rw_bw_control: bool
qos_type: str (PerShare|PerClient|PerShare_PerClient)
max_export_read_bw: str
max_export_write_bw: str
max_client_write_bw: str
max_client_read_bw: str
max_export_combined_bw: str
max_client_combined_bw: str
enable_iops_control: bool
max_export_iops: int
max_client_iops: int
1. If enable_bw_control or enable_iops_control is disabled, the associated QoS configuration will not be applied, and any related parameters will be ignored.
2. This spec implementation follows same validation as qos enable command, which are as follows. If any other parameter is passed then service will not come up.
For bandwidth control:
1. If combined bandwith control is disabled
a. If qos_type is pershare, then max_export_write_bw and max_export_read_bw parameters are compulsory
b. If qos_type is perclient, then max_client_write_bw and max_client_read_bw parameters are compulsory
c. If qos_type is pershare_perclient then max_export_write_bw, max_export_read_bw, max_client_write_bw and max_client_read_bw are compulsory parameters
2. If combined bandwidth control is enabled
a. If qos_type is pershare, then max_export_combined_bw parameter is compulsory
b. If qos_type is perclient, then max_client_combined_bw parameter is compulsory
c. If qos_type is pershare_perclient, then max_export_combined_bw and max_client_combined_bw parameters are compulsory
For IOPS control:
a. If qos_type is pershare, then max_export_iops is compulsory
b. If qos_type is perclient, then max_client_iops is compulsory
c. If qos_type is pershare_perclient then both max_export_iops and max_client_iops are compulsory parameters
Along with spec file, 'nfs cluster create' command will also able to set qos. Currently the command accept input yaml with KMIP fields, so along with that you can provide 'cluster_qos_config' field in yaml.
|
Story Points: | --- |
| Clone Of: | 2380040 | Environment: | |
| Last Closed: | 2026-01-29 06:56:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2380040, 2388233 | ||
|
Description
Bipin Kunal
2025-08-01 15:04:22 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Ceph Storage 9.0 Security and Enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2026:1536 |