The ceilometer.openstack.common.rpc.matchmaker_redis Module

The MatchMaker classes should accept a Topic or Fanout exchange key and return keys for direct exchanges, per (approximate) AMQP parlance.

class ceilometer.openstack.common.rpc.matchmaker_redis.MatchMakerRedis[source]

Bases: ceilometer.openstack.common.rpc.matchmaker.HeartbeatMatchMakerBase

MatchMaker registering and looking-up hosts with a Redis server.

ack_alive(key, host)[source]
backend_register(key, key_host)[source]
backend_unregister(key, key_host)[source]
expire(topic, host)[source]
is_alive(topic, host)[source]
class ceilometer.openstack.common.rpc.matchmaker_redis.RedisExchange(matchmaker)[source]

Bases: ceilometer.openstack.common.rpc.matchmaker.Exchange

class ceilometer.openstack.common.rpc.matchmaker_redis.RedisFanoutExchange(matchmaker)[source]

Bases: ceilometer.openstack.common.rpc.matchmaker_redis.RedisExchange

Return a list of all hosts.

run(topic)[source]
class ceilometer.openstack.common.rpc.matchmaker_redis.RedisTopicExchange(matchmaker)[source]

Bases: ceilometer.openstack.common.rpc.matchmaker_redis.RedisExchange

Exchange where all topic keys are split, sending to second half. i.e. “compute.host” sends a message to “compute” running on “host”

run(topic)[source]

Previous topic

The ceilometer.openstack.common.rpc.matchmaker Module

Next topic

The ceilometer.openstack.common.rpc.proxy Module

This Page