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.
Michael On Mon, Feb 6, 2017 at 2:01 PM, Jeremy Audet <[email protected]> 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 > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
