oslo.limit
Limit enforcement library to assist with quota calculation.
Decision gist · record as of 2026-08-14
Yes, if you are building or extending OpenStack services that need quota enforcement. The library is actively maintained, has no known vulnerabilities, and integrates cleanly with standard OpenStack components. Not applicable outside OpenStack deployments.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.11 or later.
- Designed for OpenStack deployments; requires keystoneauth1 session and OpenStack service configuration.
- Low install friction with a pure Python wheel.
License · maintenance · safety
Apache-2.0 (permissive) — Apache 2.0 permissive license allows use in commercial and proprietary projects with minimal restrictions.
last release 2026-07-10 (35 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 94,343 downloads/mo, #13,332 on PyPI
Alternatives
Verify before relying
pip install oslo.limit
from oslo_limit import limit
from keystoneauth1 import session
# Enforce quota using configured limits
limit.enforce_quota(resource_name, usage, session)- Specific quota enforcement API surface and configuration options beyond the description excerpt
- Whether oslo.limit can be used standalone or requires a full OpenStack deployment
- Performance characteristics under high-concurrency quota checks
What it is and what it does
oslo.limit is an OpenStack library that handles quota and rate-limit enforcement across OpenStack services. It provides the calculation and validation logic needed to ensure that resource consumption stays within configured quotas, helping operators prevent resource exhaustion and enforce fair usage policies.
The library integrates with OpenStack's authentication (keystoneauth1) and configuration (oslo.config) systems, making it a standard component in OpenStack deployments. It depends on oslo.i18n for internationalization and oslo.log for logging, plus openstacksdk for broader OpenStack integration. It requires Python 3.11 or later and is actively maintained.
Use it for
- Enforce API rate limits and quota checks in OpenStack services to prevent resource exhaustion
- Calculate and validate tenant resource usage against configured quotas in multi-tenant deployments
- Implement fair-use policies across OpenStack compute, storage, and network resources
- Integrate quota enforcement into custom OpenStack service extensions or middleware
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building or extending OpenStack services that need quota enforcement.
The library is actively maintained, has no known vulnerabilities, and integrates cleanly with standard OpenStack components. Not applicable outside OpenStack deployments.
Install
oslo-limit on PyPI
Before you install
Low install friction with a pure Python wheel. Active maintenance with a recent release. Depends on five oslo and OpenStack libraries (keystoneauth1, oslo.config, oslo.i18n, oslo.log, openstacksdk), all standard OpenStack components.
Requires Python 3.11 or later. Designed for OpenStack deployments; requires keystoneauth1 session and OpenStack service configuration.
License in practice
Apache 2.0 permissive license allows use in commercial and proprietary projects with minimal restrictions.
Quickstart
pip install oslo.limit
from oslo_limit import limit
from keystoneauth1 import session
# Enforce quota using configured limits
limit.enforce_quota(resource_name, usage, session)Verify before relying
- Specific quota enforcement API surface and configuration options beyond the description excerpt
- Whether oslo.limit can be used standalone or requires a full OpenStack deployment
- Performance characteristics under high-concurrency quota checks
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=3.11 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 5 packageskeystoneauth1oslo.configoslo.i18noslo.logopenstacksdk |
| Maintenance | Actively maintained 35 days since the last release |
| First released | |
| Downloads | 94,343 / month, #13,332 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Environment :: OpenStackIntended Audience :: Information TechnologyIntended Audience :: System AdministratorsOperating System :: POSIX :: LinuxProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3 :: OnlyProgramming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Programming Language :: Python :: Implementation :: CPythonTyping :: Typed |
Evidence: oslo_limit-2.12.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “openstack quota enforcement”
- oslo.limitoslo.limit enforces quota and rate limits across OpenStack services…
- oslo.policyoslo.policy enforces role-based access control (RBAC) policies across…
- ratelimitA function decorator that enforces rate limits on API calls, raising…
Give your agent the search over MCP, or paste the wish link into any chat.
More Distributed Computing packages
gRPC Python is an HTTP/2-based RPC framework that enables you to define and call remote procedures across network boundaries using protocol buffers for serialization.
Install it if you need RPC communication in a distributed system or are integrating with existing gRPC services.
execnet lets you spawn and communicate with Python interpreters across local processes, remote hosts, and different platforms, using a simple API for task distribution and inter-process messaging.
However, the aging maintenance status (275 days since last release) means you should verify it meets your concurrency and performance needs before committing to a…
Cloudpickle extends Python's standard pickle module to serialize lambda functions, interactively-defined functions and classes, and other constructs that the default pickle cannot handle, making it suitable for cluster computing and remote code execution.
Install it if you need to serialize lambda functions, interactively-defined code, or non-standard Python constructs for cluster computing or distributed execution.
Provides a unified, open()-compatible Python API for streaming large files from remote storage (S3, GCS, Azure, HDFS, SFTP, HTTP) and local filesystems, with transparent compression support.
Install it if you work with large files on cloud storage or remote systems and want to avoid writing boilerplate around multiple SDKs.
Portalocker provides cross-platform file locking with support for exclusive and shared locks, plus Redis-based distributed locks and process-aware PID file locking.
Install it if you need file or process coordination; the optional extras (pywin32, redis) are only required for specific lock types.
Ray is a distributed computing framework that scales Python applications from a single machine to multi-node clusters, providing abstractions for parallel tasks, stateful actors, and shared objects.
See also oslo.policy · oslo.middleware · oslo.vmware · oslo.privsep · oslo.log · oslo.config · oslo.db · oslo.metrics · oslo.messaging · oslo.utils