On 07/08/2010 09:33 AM, Jason Dobies wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1Yes it does. If we stick with only synchronous requests to that agent and leave asynchronous stuff to the pulp Task engine, temporary (non-durable) queues will be a good approach to pruning dead queues.This is probably a stupid question, but if we're only doing synchronous requests
To be clear, I was suggesting synchronous request/response. Asynchronous request (no response) is a different matter because it does not introduce complexity.
and they only go to one agent (or rather, each agent has its
own queue), why are we using a message bus in the first place?I always viewed it as the benefits of message buses were that they offered a pub/sub model and were really conducive to asynchronous operations.
Fair question.We will be using (I think) qpid for more then request/response. I expect we'll want the agent to broadcast (pub/sub) heartbeat messages. Also, on the server-side, we expect to broadcast (pub/sub) events intended for system integration. For example, integration between pulp and candlepin.
Also, message brokers provide queueing, reliable delivery and content based messaging routing (just to name a few).
Maybe asking some other questions will shed some light on whether we need asynchronous request/response (callback) for agent operations.
When asking a large collection of agents to perform an operation: Is this one async task or a task per consumer (agent)? Do we need to provide status of this operation for each agent?
- -- Jason Dobies RHCE# 805008743336126 Freenode: jdob -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJMNeGfAAoJEOMmcTqOSQHCqrAIAJ0SoSFvyULPcLiLX42MZGNF cBlMO0Lxc812A0I6Kjgifzg7/q89C/vQp99ltOpCV1wkd9mUW/e14FDlu7VX+2ty 3GQV86Vu3pEsAVTNUmSdQnJckxfPRXzV9kBVDmpiJfdmiRFc4eJcE5IRfMq8Mc2c GWDGCAy2zFK0q1S7x1xjmJ/DR/EfSEE9DzX3fyDov0mhV9SzLetbBXtfoUOJJcpS WZ6Dl2kXqflxeDPJYP4nSJvOStqFW6Kd2DfH7lwnzBchgQ3iL6UZsnNz7C53xzKl isYMQcwKM23X4l3cY5WNhYx8CdWpVPJi+sR8xhJd6R2MCtUpiV2ympFBIHWhnaY= =bbJV -----END PGP SIGNATURE----- _______________________________________________ Pulp-list mailing list Pulp-list redhat com https://www.redhat.com/mailman/listinfo/pulp-list
Description: S/MIME Cryptographic Signature