[Bug 1602444] Fix merged to charm-cinder (master)
OpenStack Infra
1602444 at bugs.launchpad.net
Thu Jul 14 09:34:21 UTC 2016
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 <billy.olsen at gmail.com>
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 <billy.olsen at gmail.com>
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
https://bugs.launchpad.net/bugs/1602444
Title:
worker-multiplier option does not allow floating point values
Status in Charm Helpers:
Fix Released
Status in cinder package in Juju Charms Collection:
In Progress
Status in glance package in Juju Charms Collection:
In Progress
Status in keystone package in Juju Charms Collection:
In Progress
Status in neutron-api package in Juju Charms Collection:
In Progress
Status in nova-cloud-controller package in Juju Charms Collection:
In Progress
Status in swift-storage package in Juju Charms Collection:
In Progress
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-helpers/+bug/1602444/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list