Red Hat Bugzilla – Bug 980150
The agent configuration file doesn't allow the user to specify a separate host than the pulp server for the messaging broker
Last modified: 2014-08-09 02:56:18 EDT
In consumer.conf, there is not a way to configure a separate host for the messaging broker than the Pulp server. This will make scaling difficult, if not impossible.
There are a few ways to solve this problem:
1) We could simply add the ability to specify the hostname in the [messaging] section. This is the easiest solution.
2) We could do something really slick, and have the agent ask the Pulp server's API for the details it needs to connect to the Pulp Server. This way, it doesn't need to be configured. The SSL certificates could also be passed to it over the API, if configured.
[root@ibm-x3550m3-08 ~]# rpm -qa pulp-server
# Agent messaging.
# The broker URL scheme (tcp|ssl)
# The broker host (default: host defined in [server]).
# The broker port number.
# The AMQP transport name.
# The (optional) CA certificate (PEM) to verify the server.
# The client (PEM) key & certificate used to connect to the broker.
# Uses the id_cert_dir and id_cert_filename when not defined here.
scheme = tcp
port = 5672
transport = qpid
This has been fixed in Pulp 2.4.0-1.