Shared code between AMQP based openstack.common.rpc implementations.
The code in this module is shared between the rpc implemenations based on AMQP. Specifically, this includes impl_kombu and impl_qpid. impl_carrot also uses AMQP, but is deprecated and predates this code.
Bases: nova.openstack.common.rpc.amqp._ThreadPoolWithWait
Wraps a straight callback to allow it to be invoked in a green thread.
Bases: nova.openstack.common.rpc.common.Connection
The class that is actually returned to the caller of create_connection(). This is essentially a wrapper around Connection that supports ‘with’. It can also return a new Connection, or one from a pool. The function will also catch when an instance of this class is to be deleted. With that we can return Connections to the pool on exceptions and so forth without making the caller be responsible for catching them. If possible the function makes sure to return a connection to the pool.
Caller is done with this connection.
Bases: object
Bases: eventlet.pools.Pool
Class that implements a Pool of Connections.
Bases: nova.openstack.common.rpc.amqp._ThreadPoolWithWait
Calls methods on a proxy object based on method and args.
Bases: nova.openstack.common.rpc.amqp.ConnectionContext
Connection class for RPC replies / callbacks
Bases: nova.openstack.common.rpc.common.CommonRpcContext
Context that supports replying to a rpc.call
Sends a message on a topic and wait for a response.
Sends a message on a topic without waiting for a response.
Sends a message on a topic to a specific server.
Create a connection
Sends a message on a fanout exchange without waiting for a response.
Sends a message on a fanout exchange to a specific server.
Sends a reply or an error on the channel signified by msg_id.
Failure should be a sys.exc_info() tuple.
Make a call that returns multiple times.
Sends a notification event on a topic.
Pack context into msg.
Values for message keys need to be less than 255 chars, so we pull context out into a bunch of separate keys. If we want to support more arguments in rabbit messages, we may want to do the same for args at some point.
Unpack context from msg.