[Pulp-dev] Pulp multinode testing

Michael Hrivnak mhrivnak at redhat.com
Mon Feb 6 19:11:15 UTC 2017

That could be a nice and simple way to start.

I would also consider 2 machines with all services running on both. This
would ensure that all the services work correctly with multiple instances
running on multiple machines. You may need a simple load-balancer for all
HTTP traffic to ensure you're getting a mix of both machines serving API
requests and content.


On Mon, Feb 6, 2017 at 2:01 PM, Jeremy Audet <jaudet at redhat.com> wrote:

> My question is, what is the environment we would like to test Pulp on a
>> multi machine environment? I remember someone mentioning about having 3
>> machines:
>> 1. Pulp server
>> 2. Pulp workers
>> 3. Pulp Smash
>> Do you think is that ok? Or should another architecture be considered?
> That seems fine to me. We could even run Pulp Smash on the Pulp server or
> on a Pulp worker, so long as Python 3.4+ is available.
> * Update Pulp Smash to manage workers services on a different machine than
>> the Pulp server if it is configured to do so.
> I think this is a good way to move forward. I'm confident that Pulp Smash
> can be updated so that it can handle multi-node testing in a graceful way.
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170206/a73ce041/attachment.htm>

More information about the Pulp-dev mailing list