09b10cfecb
Rate limits on the server-side are per-service, but the rate limit in the TaskManager is a single rate. Add support for a dict of rate limits, keyed by service-type. The primary user interface should be passing rate to the Connection constructor. That takes calls-per-second for both scalar and dict versions of its rate parameter. Depends-On: https://review.openstack.org/612168/ Change-Id: If0ff77b43adc1f6f0bb1e7c08908930a95508b31
9 lines
326 B
YAML
9 lines
326 B
YAML
---
|
|
features:
|
|
- |
|
|
Client-side rate limiting is now directly exposed via ``rate_limit``
|
|
and ``concurrency`` parameters. A single value can be given that applies
|
|
to all services, or a dict of service-type and value if different
|
|
client-side rate or concurrency limits should be used for different
|
|
services.
|