In D8167#212470, @olasd wrote:

The origin extrinsic metadata indexer only runs on a single file at a time, so I don't think it needs to run alone on dedicated hosts.

ok, so i'll amend this so it's declared on all hosts.

Having journal clients in the swh::deploy::worker hierarchy is a bit confusing, we should probably properly split the manifests between celery workers and journal clients to unconfuse things.

Yes, agreed.

I previously did the minimal work to allow cleaning up the previous services and declare the new indexer journal client to be deployed.

Furthermore, we will probably want to deploy multiple instances of the same journal client on a given host (for parallelism), using parametric systemd units, so the way we deploy them will probably diverge even further

Makes sense indeed.