oslo.messaging
Oslo Messaging API
Decision gist · record as of 2026-08-14
Yes, if you are building OpenStack services or distributed systems that require a standardized messaging abstraction. The active maintenance, low install friction, permissive license, and zero known vulnerabilities make it a solid choice. No, if you need a lightweight messaging client for simple use cases—the 17 dependencies and Python 3.11+ requirement add overhead. Yes-with-conditions if evaluating for non-OpenStack projects: verify that the oslo.* ecosystem and its dependency footprint align with your architecture.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires a message broker backend to be running and accessible; Python 3.11 or later.
- Low install friction with a pure-Python wheel.
- Active maintenance as of 35 days ago.
License · maintenance · safety
permissive license (permissive) — Licensed under Apache License, Version 2.0 (permissive). Safe for commercial and proprietary use with standard attribution requirements.
last release 2026-07-10 (35 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 502,247 downloads/mo, #6,310 on PyPI
Alternatives
Verify before relying
pip install oslo.messaging
from oslo_messaging import rpc
from oslo_messaging import transport
trans = transport.get_transport(transport_url)- Whether all 17 runtime dependencies are truly required for basic RPC/notification use or if some are optional.
- Performance characteristics and throughput limits for different transport backends.
- Whether the package supports async/await patterns or is callback-based only.
- Specific message broker versions and configurations supported.
What it is and what it does
Oslo Messaging is an OpenStack library that provides a standardized API for sending RPC calls and notifications across distributed systems. It abstracts the underlying message transport layer, allowing applications to work with different brokers without changing application code. The library handles serialization, routing, and delivery semantics, making it easier to build loosely coupled microservices and distributed components.
The package is designed for infrastructure and cloud applications that need reliable inter-process communication. It brings in 17 runtime dependencies including kombu, amqp, oslo.config, oslo.log, oslo.serialization, and others. It requires Python 3.11 or later and a running message broker backend to function.
Use it for
- Building OpenStack services that need to communicate via RPC calls across multiple nodes.
- Sending notifications from one service to many subscribers in a distributed system.
- Abstracting message transport details to allow switching between different brokers.
- Implementing request-reply patterns in microservices without direct broker coupling.
- Centralizing messaging configuration and serialization logic across multiple applications.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building OpenStack services or distributed systems that require a standardized messaging abstraction.
The active maintenance, low install friction, permissive license, and zero known vulnerabilities make it a solid choice. No, if you need a lightweight messaging client for simple use cases—the 17 dependencies and Python 3.11+ requirement add overhead. Yes-with-conditions if evaluating for non-OpenStack projects: verify that the oslo.* ecosystem and its dependency footprint align with your architecture.
Install
oslo-messaging on PyPI
Before you install
Low install friction with a pure-Python wheel. Active maintenance as of 35 days ago. Requires Python 3.11 or later and brings in 17 runtime dependencies including kombu, amqp, and several other oslo.* libraries, which is typical for OpenStack infrastructure components.
Requires a message broker backend to be running and accessible; Python 3.11 or later.
License in practice
Licensed under Apache License, Version 2.0 (permissive). Safe for commercial and proprietary use with standard attribution requirements.
Quickstart
pip install oslo.messaging
from oslo_messaging import rpc
from oslo_messaging import transport
trans = transport.get_transport(transport_url)Verify before relying
- Whether all 17 runtime dependencies are truly required for basic RPC/notification use or if some are optional.
- Performance characteristics and throughput limits for different transport backends.
- Whether the package supports async/await patterns or is callback-based only.
- Specific message broker versions and configurations supported.
Package facts
| License | permissive license permissive |
| Python support | Supports the current Python release >=3.11 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 17 packagespbrfuturistoslo.configoslo.contextoslo.logoslo.utilsoslo.serializationoslo.servicestevedoredebtcollectorcachetoolsWebObPyYAMLamqpkombuoslo.middlewareoslo.metrics |
| Maintenance | Actively maintained 35 days since the last release |
| First released | |
| Downloads | 502,247 / month, #6,310 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Environment :: OpenStackIntended Audience :: DevelopersIntended Audience :: Information TechnologyLicense :: OSI Approved :: Apache Software LicenseOperating System :: OS IndependentProgramming 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 :: CPython |
Evidence: oslo_messaging-18.2.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 › “RPC messaging library”
- oslo.messagingOslo Messaging provides a unified API for RPC and notification…
- autobahnAutobahn provides WebSocket and WAMP (Web Application Messaging…
- wslinkwslink provides bi-directional websocket communication between a…
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.versionedobjects · oslo.vmware · solace-pubsubplus · oslo.metrics · oslo.policy · oslo.cache · oslo.serialization · oslo.concurrency · oslo.db · Farama-Notifications