Bug 1313368

Summary: keystone wsgi default worker number threads vs. processes
Product: Red Hat OpenStack Reporter: Attila Fazekas <afazekas>
Component: openstack-puppet-modulesAssignee: Emilien Macchi <emacchi>
Status: CLOSED WONTFIX QA Contact: yeylon <yeylon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: srevivo, yeylon
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-01 17:40:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Attila Fazekas 2016-03-01 13:30:32 UTC 
Description of problem:

Puppet keystone default the number of python threads to the number of processors,
instead of setting processes to nr_cpu and leave the threads to 1.


Version-Release number of selected component (if applicable):
openstack-puppet-modules-7.0.6-2.el7ost.noarch
puppet-3.6.2-2.el7.noarch
openstack-packstack-puppet-7.0.0-0.12.dev1699.g8f54936.el7ost.noarch


Actual results:
$ cat /etc/httpd/conf.d/10-keystone_wsgi_admin.conf |grep thread
WSGIDaemonProcess keystone_admin display-name=keystone-admin group=keystone processes=1 threads=4 user=keystone

Expected results:
WSGIDaemonProcess keystone_admin display-name=keystone-admin group=keystone processes=4 threads=1 user=keystone

Additional info:
cat /proc/cpuinfo |grep process | wc -l
4

It will lead to little more memory usage,
but you will be able utilize the cpu.

If the DB in LAN range, you should not try to increase the number of threads by default.
Comment 2 Emilien Macchi 2016-03-01 17:40:20 UTC 
Attila, thanks for your bug report.
Since we're using Launchpad to track bugs in upstream projects, it would be very nice to report this bug in https://bugs.launchpad.net/puppet-keystone

Also, if you think that's a bug in OSP Director, you might want to create a bug for TripleO Heat Templates to change the values.

Thanks.