Bug 2394369

Description of problem:

During testing of RGW rate limits in Ceph v8.0 and v8.1, it was observed that RGW only supports user-scope and bucket-scope rate limits. The radosgw-admin ratelimit set command requires either --uid (user) or --bucket.

By contrast, account-level quotas are supported, but equivalent account-level rate limits are missing. 


As per the discussion in the Slack thread https://ibm-systems-storage.slack.com/archives/C04S5K7H0F2/p1757342657579499?thread_ts=1755276251.608929&cid=C04S5K7H0F2

Introduce Account-scope rate limits, aligned with existing account quotas, with clear attribution rules.

The enhancement aims to bring account-scope rate limits into RGW, aligning them with the existing account quota model and ensuring consistency for administrators. The idea is to establish clear attribution rules so that rate limits are not only enforceable but also flexible enough to cover diverse real-world scenarios.

- The default behavior would be to attribute rate limits to the account that owns the role.

- Owning Account: By default, the account that owns the role would absorb the rate limits.

- Caller’s Account: In cross-account scenarios, it should be possible to charge usage to the calling account instead.

- Role itself: Rate limits could be applied directly at the role level, enabling finer granularity.

- Stable Session Tag (e.g., ExternalId): Rate limits could also be grouped and attributed based on session identifiers for consistency across assumptions.

- Requester Pays buckets: In cases where Requester Pays is enabled, rate limits should follow the requester’s account.

This approach would give administrators the control to apply limits in a way that matches their organizational policies while maintaining alignment with the quota framework.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: