Barbican starts a single process only

Bug #1745631 reported by Mohammed Naser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Mohammed Naser

Bug Description

Barbican starts a single process without the ability to reconfigure the number of processes, this can cause issues at scale.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_barbican (master)

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

Changed in openstack-ansible:
assignee: nobody → Mohammed Naser (mnaser)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_barbican (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/538292

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_barbican (master)

Reviewed: https://review.openstack.org/538289
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_barbican/commit/?id=4b0da513d06ebffad24490b9b08eb2033ee6a181
Submitter: Zuul
Branch: master

commit 4b0da513d06ebffad24490b9b08eb2033ee6a181
Author: Mohammed Naser <email address hidden>
Date: Fri Jan 26 10:45:05 2018 -0500

    Allow ability to configure number of processes and threads

    Users can configure the number of worker threads however when it's
    not specified the calculated number of workers can get too large on
    hosts with a large number of CPUs.

    This also adds the setting of threads and processes to the UWSGI
    configuration.

    Change-Id: I003ab426488966cce46bd6fd297c79ada13c9668
    Closes-Bug: #1745631

Changed in openstack-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-os_barbican (stable/pike)

Reviewed: https://review.openstack.org/538292
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_barbican/commit/?id=4ca117c0474661bb4583c2d7d3b78700000900e2
Submitter: Zuul
Branch: stable/pike

commit 4ca117c0474661bb4583c2d7d3b78700000900e2
Author: Mohammed Naser <email address hidden>
Date: Fri Jan 26 10:45:05 2018 -0500

    Allow ability to configure number of processes and threads

    Users can configure the number of worker threads however when it's
    not specified the calculated number of workers can get too large on
    hosts with a large number of CPUs.

    This also adds the setting of threads and processes to the UWSGI
    configuration.

    Change-Id: I003ab426488966cce46bd6fd297c79ada13c9668
    Closes-Bug: #1745631
    (cherry picked from commit 4b0da513d06ebffad24490b9b08eb2033ee6a181)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_barbican 17.0.0.0rc1

This issue was fixed in the openstack/openstack-ansible-os_barbican 17.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/openstack-ansible-os_barbican 16.0.8

This issue was fixed in the openstack/openstack-ansible-os_barbican 16.0.8 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.