Description of problem:
OpenStack Swift Proxy Server Daemon (swift-proxy-server) should be configured with more than one process/worker for performance and scalability.
Version-Release number of selected component (if applicable):
Always with default setup
Steps to Reproduce:
1. Deploy Red Hat OpenStack Platform
2. Review # of Swift proxy-server daemons running
The configured default is a single worker despite the puppet-swift installer (For Newton) showing it should configure more than a single worker (processor count) 
At a minimum, more than a single daemon per the Swift General Service Tuning 
Currently you can work around this by passing an additional yaml template into the openstack deploy command to expand the number of workers:
The actual General Service Tuning recommends 2 x physical cpu core count though it mentions further experiments might be necessary if the server shares other services running on it. (Such as our controllers)
Reviewing the configuration for the swift-proxy-server shows it is configured for a single worker by default by being tuned to:
workers = 0
Thus it suggests something is overriding the configuration by the puppet-swift installer.
In actually testing for scalability of Gnocchi processing metrics on instances with a swift storage backend, it has shown that a single swift-proxy worker will peg a single cpu core at 100 instances ( Technically three workers each pegging a cpu core across 3 controllers - ha deployment)
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
Fix merged upstream, setting this to POST.