Story #3361
Updated by milan over 6 years ago
h2. Motivation
* an optional deployment style without requiring multiple @systemd@ services running (no worker processes)
* pulling less dependencies for restricted environments e.g running Pulp on one's laptop from a @venv@ instead of a VM
* simpler proofs of concept with a single service to e.g put in a container, esp. now that we support SQLite3
* functional testing of core--plug-in API with the ability to mock&assert selected codepaths, all being able to run from
within a test case
* functional testing of Pulp worker API in a similar fashion
* possibly avoid remote debugging of workers
h2. Solution
The Kombu library has an "in-memory transport":http://docs.celeryproject.org/projects/kombu/en/latest/reference/kombu.transport.memory.html that I hope we "could utilize":https://github.com/celery/kombu/issues/606 for this purpose.
This of course would still require some investigation work and probably couple of tweaks here and there to make it work properly.
h2. Scope
* pulp development installation utils
* pulp core in case issues are spotted once the pulp worker processes turn into threads
.