Comment 1 for bug 1626126

Actually this might extend far beyond the glance api. Current hieradata is:

service_configs.yaml:glance::api::workers: 0
service_configs.yaml:glance::registry::workers: 0
service_configs.yaml:heat::api::workers: 0
service_configs.yaml:heat::api_cfn::workers: 0
service_configs.yaml:heat::api_cloudwatch::workers: 0
service_configs.yaml:heat::engine::num_engine_workers: 0
service_configs.yaml:keystone::wsgi::apache::workers: "%{::processorcount}"
service_configs.yaml:neutron::agents::metadata::metadata_workers: 0
service_configs.yaml:neutron::server::api_workers:
service_configs.yaml:neutron::server::rpc_workers:
service_configs.yaml:nova::api::metadata_workers: 0
service_configs.yaml:nova::api::osapi_compute_workers: 0
service_configs.yaml:nova::conductor::workers: 0

So unless the services where the worker count is 0 interpret it as something other than single process, this could suck.

On my 2 CPU controller node I have:

1 process for glance API
1 process for glance registry
1 process each for neutron agents (though I think that's what it should be)
1 process for neutron-ns-meta-data-proxy
1 process for nova scheduler
1 process for nova-consoleauth
1 process for nova-novncproxy
1 process for aodh listener, notifier and evaluator each.
1 process for cinder scheduler
1 process for ceilometer agent-scheduler, agent-notification, collect and polling each
1 process each for swift container-replicator, account-reaper, account-replicator, container-auditor, object-replicator, account-auditor, proxy-server, object-updater and container-updater
1 process for gnocchi-metricd

I'll check the puppet to see if any of these are processorcount and work my way backwards.