Bug 1330980
| Summary: | Undercloud deployed with 1 keystone worker and cpu_count for threads | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alex Krzos <akrzos> | |
| Component: | puppet-keystone | Assignee: | RHOS Maint <rhos-maint> | |
| Status: | CLOSED ERRATA | QA Contact: | nlevinki <nlevinki> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 8.0 (Liberty) | CC: | akrzos, ayoung, hbrock, jcoufal, jjoyce, jschluet, jslagle, kbasil, mburns, nkinder, rduartes, rhel-osp-director-maint, sclewis, slinaber, srevivo, tvignaud | |
| Target Milestone: | Upstream M3 | Keywords: | Triaged | |
| Target Release: | 11.0 (Ocata) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | puppet-keystone-9.4.0-0.20161102012005.dfd9690.el7ost | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1435472 (view as bug list) | Environment: | ||
| Last Closed: | 2017-05-17 19:29: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: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1435472 | |||
|
Description
Alex Krzos
2016-04-27 11:49:51 UTC
puppet-keystone already provides the interface to change threads/workers parameters, so this is a bug for undercloud. The values for keystone start with the yaml file here http://git.openstack.org/cgit/openstack/instack-undercloud/tree/elements/puppet-stack-config/puppet-stack-config.yaml.template#n173 This ends up on the undercloud reified as /etc/puppet/hieradata/puppet-stack-config.yaml Quickstart adds a follow on file that overrides values /etc/puppet/hieradata/quickstart-hieradata-overrides.yaml Please put any overrides you need into a comparable file. Perhaps try using 4-8 workers with 1 thread per worker, as Python/WSGI does not make effective use of threading. The parameters should be something like keystone::wsgi::apache::workers Does this work for you? This logic here is a safer approach: https://review.openstack.org/#/c/375146/ And is what the puppet-keystone and other WSGI modules are going to use. (In reply to Adam Young from comment #4) > This logic here is a safer approach: > > https://review.openstack.org/#/c/375146/ > > And is what the puppet-keystone and other WSGI modules are going to use. Are there changes proposed already for puppet-keystone to make use of this? If so, what versions are we going to pull those changes into? Does this bug need to be filed against a different component (like o-p-m)? https://review.openstack.org/#/c/297342/ Has been updated to use the new fact. This has merged upstream in the master branch of puppet-keystone. verified for openstack-keystone-11.0.0-0.20170127043446.cefbc3c.el7ost.noarch - conf files in httpd now have a max between '(<# processors> / 4)' and '2' with a cap of 8. In the testing environment, each controller has 4 processors: # cat 10-keystone_wsgi_main.conf | grep WSGIDaemonProcess WSGIDaemonProcess keystone_main display-name=keystone-main group=keystone processes=2 threads=1 user=keystone # cat 10-keystone_wsgi_admin.conf | grep WSGIDaemonProcess WSGIDaemonProcess keystone_admin display-name=keystone-admin group=keystone processes=2 threads=1 user=keystone 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. https://access.redhat.com/errata/RHEA-2017:1245 |