wsgi processes ratio is set to favour admin processes over public processes

[Gábor Mészáros]

In our deployment keystone have way more public connections then admin ones, but the charm currently supports more admin process to be handled then public. This parameter would be best to be configurable, depending on the actual environment.

https://github.com/openstack/charm-keystone/blob/74bc2e2abfafbe860a428133917913f7ba427c70/charmhelpers/contrib/openstack/context.py#L1243

[James Page (james-page)]

Feels like that's the wrong way around to me.

[Gábor Mészáros (gabor.meszaros)]

yes, it seems to be the other way around before
https://github.com/openstack/charm-keystone/blob/stable/16.04/hooks/keystone_context.py#L287

[Alex Kavanagh (ajkavanagh)]

I'd tend to agree. Gabor has it at .5 / .5 at the moment (patched charm), but I'd go with .75 / .25 or higher to public / admin processes.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/460031

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/460031
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=21a4e5beb1c833ce7380f239de25e03ef1936503
Submitter: Jenkins
Branch: master

commit 21a4e5beb1c833ce7380f239de25e03ef1936503
Author: James Page <email address hidden>
Date: Wed Apr 26 10:54:15 2017 +0100

    Cap workers in containers, fix admin/pubic skew

    Resync charm-helpers to pickup the latest code for calculation
    of worker process configuration, creating better default
    worker configuration when deploying in LXD containers.

    Switch the skew between public and admin processes to favour
    public 0.75/0.25 as the public API endpoints of a service will
    typically get a larger number of hits.

    Fixup unit test for minor behavioural change in charm-helpers.

    Change-Id: I4ab1d28f907ce29d5602b48ba7a438fc3690277c
    Closes-Bug: 1665270
    Closes-Bug: 1686049