worker-multiplier option does not allow floating point values

Bug #1602444 reported by Billy Olsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Charm Helpers
Fix Released
Undecided
Billy Olsen
cinder (Juju Charms Collection)
Fix Released
Medium
Billy Olsen
glance (Juju Charms Collection)
Fix Released
Medium
Billy Olsen
keystone (Juju Charms Collection)
Fix Released
Medium
Billy Olsen
neutron-api (Juju Charms Collection)
Fix Released
Medium
Billy Olsen
nova-cloud-controller (Juju Charms Collection)
Fix Released
Medium
Billy Olsen
swift-storage (Juju Charms Collection)
Fix Released
Medium
Billy Olsen

Bug Description

The worker-multiplier option is a convenience option that lets the users not worry about the number of CPUs specifically. However, in deployments where there are many containers running api services on the hosts, this results in way too many processes leading to high load.

Unfortunately, the worker-multiplier option is specified as an integer value which does not allow a user to reduce this below the number of CPUs detected.

A work around is to further spread the load to multiple baremetal machines and do not place all API services on the same machines.

Tags: sts

Related branches

no longer affects: swift-proxy (Juju Charms Collection)
Changed in cinder (Juju Charms Collection):
status: New → Triaged
Changed in glance (Juju Charms Collection):
status: New → Triaged
Changed in neutron-api (Juju Charms Collection):
status: New → Triaged
Changed in nova-cloud-controller (Juju Charms Collection):
status: New → Triaged
Changed in cinder (Juju Charms Collection):
importance: Undecided → Medium
Changed in glance (Juju Charms Collection):
importance: Undecided → Medium
Changed in neutron-api (Juju Charms Collection):
importance: Undecided → Medium
Changed in nova-cloud-controller (Juju Charms Collection):
importance: Undecided → Medium
Changed in cinder (Juju Charms Collection):
assignee: nobody → Billy Olsen (billy-olsen)
Changed in glance (Juju Charms Collection):
assignee: nobody → Billy Olsen (billy-olsen)
Changed in neutron-api (Juju Charms Collection):
assignee: nobody → Billy Olsen (billy-olsen)
Changed in nova-cloud-controller (Juju Charms Collection):
assignee: nobody → Billy Olsen (billy-olsen)
Changed in swift-storage (Juju Charms Collection):
assignee: nobody → Billy Olsen (billy-olsen)
Changed in cinder (Juju Charms Collection):
milestone: none → 16.07
Changed in glance (Juju Charms Collection):
milestone: none → 16.07
Changed in neutron-api (Juju Charms Collection):
milestone: none → 16.07
Changed in nova-cloud-controller (Juju Charms Collection):
milestone: none → 16.07
Changed in swift-storage (Juju Charms Collection):
milestone: none → 16.07
status: New → Triaged
Changed in swift-storage (Juju Charms Collection):
importance: Undecided → Medium
Changed in charm-helpers:
status: New → In Progress
assignee: nobody → Billy Olsen (billy-olsen)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-keystone (master)

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

Changed in keystone (Juju Charms Collection):
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-neutron-api (master)

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

Changed in neutron-api (Juju Charms Collection):
status: Triaged → In Progress
Changed in nova-cloud-controller (Juju Charms Collection):
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-nova-cloud-controller (master)

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

Changed in swift-storage (Juju Charms Collection):
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-swift-storage (master)

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

Changed in glance (Juju Charms Collection):
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-glance (master)

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

Changed in cinder (Juju Charms Collection):
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-cinder (master)

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

Changed in charm-helpers:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-swift-storage (master)

Reviewed: https://review.openstack.org/341232
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=97180d7100041fdab5ecd974d10d0aa6cabb6ec4
Submitter: Jenkins
Branch: master

commit 97180d7100041fdab5ecd974d10d0aa6cabb6ec4
Author: Billy Olsen <email address hidden>
Date: Tue Jul 12 17:06:05 2016 -0700

    Change worker-multiplier to float

    Change the worker-multiplier to a floating point config option type
    instead of integer. This allows users to specify workers to be less
    than the number of CPUs, which is useful in deployments with multiple
    services deployed into containers on top of bare metal.

    The fix is to simply change the config option type and to sync in
    the necessary update from lp:charm-helpers.

    Partial-Bug: #1602444

    Change-Id: I31d7652e7ad5db0185b78e2c4c2c1d2ddba05be2
    Signed-off-by: Billy Olsen <email address hidden>

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

Reviewed: https://review.openstack.org/341235
Committed: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=8858d1973106c74d8f7985725e7fa8fe78e79339
Submitter: Jenkins
Branch: master

commit 8858d1973106c74d8f7985725e7fa8fe78e79339
Author: Billy Olsen <email address hidden>
Date: Tue Jul 12 17:09:47 2016 -0700

    Change worker-multiplier to float

    Change the worker-multiplier to a floating point config option type
    instead of integer. This allows users to specify workers to be less
    than the number of CPUs, which is useful in deployments with multiple
    services deployed into containers on top of bare metal.

    The fix is to simply change the config option type and to sync in
    the necessary update from lp:charm-helpers.

    Partial-Bug: #1602444

    Change-Id: Iaf9aaa3cf1a87e2ed63cbd32df6c328e89c5814e
    Signed-off-by: Billy Olsen <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-nova-cloud-controller (master)

Reviewed: https://review.openstack.org/341231
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=8d35070586fd0d4a3c9cac04f32e987b4d0ea352
Submitter: Jenkins
Branch: master

commit 8d35070586fd0d4a3c9cac04f32e987b4d0ea352
Author: Billy Olsen <email address hidden>
Date: Tue Jul 12 17:05:20 2016 -0700

    Change worker-multiplier to float

    Change the worker-multiplier to a floating point config option type
    instead of integer. This allows users to specify workers to be less
    than the number of CPUs, which is useful in deployments with multiple
    services deployed into containers on top of bare metal.

    The fix is to simply change the config option type and to sync in
    the necessary update from lp:charm-helpers.

    Partial-Bug: #1602444

    Change-Id: I2c846832d24f709a3d019b766f5f23c28c4371f4
    Signed-off-by: Billy Olsen <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-neutron-api (master)

Reviewed: https://review.openstack.org/341229
Committed: https://git.openstack.org/cgit/openstack/charm-neutron-api/commit/?id=7ef79162e695801945e1ff88cf847fdfdcbfff89
Submitter: Jenkins
Branch: master

commit 7ef79162e695801945e1ff88cf847fdfdcbfff89
Author: Billy Olsen <email address hidden>
Date: Tue Jul 12 17:02:14 2016 -0700

    Change worker-multiplier to float

    Change the worker-multiplier to a floating point config option type
    instead of integer. This allows users to specify workers to be less
    than the number of CPUs, which is useful in deployments with multiple
    services deployed into containers on top of bare metal.

    The fix is to simply change the config option type and to sync in
    the necessary update from lp:charm-helpers.

    Partial-Bug: #1602444

    Change-Id: I40a7e272ee6c66adefbf1cbff98756108e631e0b
    Signed-off-by: Billy Olsen <email address hidden>

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

Reviewed: https://review.openstack.org/341234
Committed: https://git.openstack.org/cgit/openstack/charm-glance/commit/?id=b825bd4747006125562de7660d86f978764ec44b
Submitter: Jenkins
Branch: master

commit b825bd4747006125562de7660d86f978764ec44b
Author: Billy Olsen <email address hidden>
Date: Tue Jul 12 17:09:25 2016 -0700

    Change worker-multiplier to float

    Change the worker-multiplier to a floating point config option type
    instead of integer. This allows users to specify workers to be less
    than the number of CPUs, which is useful in deployments with multiple
    services deployed into containers on top of bare metal.

    The fix is to simply change the config option type and to sync in
    the necessary update from lp:charm-helpers.

    Partial-Bug: #1602444

    Change-Id: I5f7b24d53f35c4a7ec9e5de563afa5e232ca83af
    Signed-off-by: Billy Olsen <email address hidden>

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

Reviewed: https://review.openstack.org/341218
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=4ab385f62f0e002b478f47db1f6a06f9df07e03a
Submitter: Jenkins
Branch: master

commit 4ab385f62f0e002b478f47db1f6a06f9df07e03a
Author: Billy Olsen <email address hidden>
Date: Tue Jul 12 16:35:57 2016 -0700

    Change worker-multiplier to float

    Change the worker-multiplier to a floating point config option type
    instead of integer. This allows users to specify workers to be less
    than the number of CPUs, which is useful in deployments with multiple
    services deployed into containers on top of bare metal.

    The fix is to simply change the config option type and to sync in
    the necessary update from lp:charm-helpers.

    Partial-Bug: #1602444

    Change-Id: I534165aa2fc45a28f6b3f3bb2f708789daf5ba8c
    Signed-off-by: Billy Olsen <email address hidden>

Liam Young (gnuoy)
Changed in keystone (Juju Charms Collection):
milestone: 16.07 → 16.10
Changed in neutron-api (Juju Charms Collection):
milestone: 16.07 → 16.10
Changed in nova-cloud-controller (Juju Charms Collection):
milestone: 16.07 → 16.10
Changed in swift-storage (Juju Charms Collection):
milestone: 16.07 → 16.10
Changed in cinder (Juju Charms Collection):
milestone: 16.07 → 16.10
Changed in glance (Juju Charms Collection):
milestone: 16.07 → 16.10
James Page (james-page)
Changed in cinder (Juju Charms Collection):
status: In Progress → Fix Released
Changed in glance (Juju Charms Collection):
status: In Progress → Fix Released
Changed in keystone (Juju Charms Collection):
status: In Progress → Fix Released
Changed in neutron-api (Juju Charms Collection):
status: In Progress → Fix Released
Changed in nova-cloud-controller (Juju Charms Collection):
status: In Progress → Fix Released
Changed in swift-storage (Juju Charms Collection):
status: In Progress → Fix Released
Changed in cinder (Juju Charms Collection):
milestone: 16.10 → 16.07
Changed in glance (Juju Charms Collection):
milestone: 16.10 → 16.07
Changed in keystone (Juju Charms Collection):
milestone: 16.10 → 16.07
Changed in neutron-api (Juju Charms Collection):
milestone: 16.10 → 16.07
Changed in nova-cloud-controller (Juju Charms Collection):
milestone: 16.10 → 16.07
Changed in swift-storage (Juju Charms Collection):
milestone: 16.10 → 16.07
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.