Description of problem:
Swift deployed by tripleo using OSPd deploys single swift-object-server, swift-container-server, and swift-account-server processes which can/will affect the scalability and performance of your Swift. General Swift tuning guide recommends a one to one ratio of physical cpu to process counts for these processes with a single concurrency for the background tasks with ther exception of the replicators 
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Deploy overcloud and review process counts of the swift services
Related bug https://bugzilla.redhat.com/show_bug.cgi?id=1411391
This may be covered by some WIP and doc changes coming, over to Swift to comment/triage.
It's possible to set the workers count using a template with the proposed patch for puppet-swift applied like this:
Also proposed a t-h-t patch to simplify this:
Merged after release - moving to 13.
Still waiting on newer puddle
Last one I managed to deploy today, none sufficient yet > 2018-02-14.1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.