This change adds the missing region setting in service_credentials. In a
shared keystone multi region setup, this setting is mandatory in order
for ceilometer to properly find the services it relies upon from the
same region it resides in. Without this setting, the ceilometer-upgrade
action will fail (along with any other calls made to ceilometer) if the
first endpoint returned by keystone is from a different region.
Change-Id: Ie14df0f5fc7ee18072091dbdb3ada817615a6670
Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
This reverts commit 6ed691807d.
The meter_sink is actually required in pipeline.yaml and not in
event_pipline.yaml, and this is something that needs to be enabled
for newton and above as the ceilometer-collector is not the
dependancy for this.
Change-Id: Ie40a99281f1f60de7a409e1e3a2025a850a8a446
This configuration for pipeline.yaml is still valid for mitaka and
above, so adding this in.
The ceilometer-collector package is not available in newer openstack
releases, so basing this on QUEENS_SERVICES.
This should solve the custom requirement of pipeline moving forward.
Other fixes:
* Update test-requirements.txt for cffi and related pins.
* Update focal-xena bundle to fix memcached series bionic requirement.
Closes-Bug: 1938807
Change-Id: I1946b6f172cdae6f444d07999d5e54d4e11a450e
If the user wants to add a meter-sink to the pipeline.yaml
at the moment this cannot be done. Previously, pipeline-yaml
config option was allowed and could replace the whole config.
This will now allow to also add meter-sink as an option to
the event_pipeline.yaml, and allow a new source of collecting
all meters, and pushing to the value of meter-sink URLs.
Closes-Bug: 1938807
Change-Id: If6cd82e4153b29c1d8fdb6df150d0d4bb11d4e49
Restarts were configured only when the ceilometer agent endpoint
had changed and only alarm services were triggered to be restarted.
This change adds a check for the gnocchi service having changed
too and restarts all services to be on the safe side.
Closes-Bug: #1867924
Change-Id: I48e2f079e2db640d485bc74bfc2cedfd7e82ac84
Samples collected can be batched together,
consequently increasing or reducing the
amount of API calls and body data
sent to the configured publisher.
This config is available since Rocky,
adding the config option to allow its
tuning.
Change-Id: I0e3f756aa0305d3a96e21c7498d6a56208c51007
Closes-bug: #1885190
This exception handling code was still calling for
'e.message' which is only present in Python 2 and
not supported anymore. Also fixed unit tests where were
skipping over this.
Closes-bug: #1886874
Change-Id: Ia541e7b8994fae56e04771333009321cd6ac164e
This patch adds debug option to ceilometer-upgrade to be more
explanatory in case of failure. Furthermore, it adds the option of a
sane number of retries because in case of failure at the current
master branch the ceilometer-upgrade action hangs forever.
Change-Id: Ib992eea42c4b085387b19b92798bc88ef0e1589e
Signed-off-by: Stamatis Katsaounis <katsaouniss@gmail.com>
The previous attempt at addressing Bug#1811108 was a bit naive.
It was not HA aware and it failed to handle upgrade-charm.
This change moves from kv to leader-set as only the leader needs to run
the action and then inform the other nodes.
Note: on upgrade-charm we must assume the deployment has run
ceilometer-upgrade as there is no mechanism to determine this
independently. If we do not do this, the charm is in blocked state after
charm-upgrade. A warning is logged that this assumption has occurred.
Partial-Bug: #1811108
Change-Id: Idcc26df53542e78f0671942c99edfcbf61eccf6c
The charm currently configures events to be published to
rabbit on both the config.event_topic (event.sample queue)
and alarm topic but as of Queens Ceilometer no longer
consumes event.sample. This patch makes the event_sink
publishers configurable and defaults to publishing to
aodh to retain backwards compatibility.
Change-Id: I5b55f31adcf2b069ff51e387a416f9f1ac4099f8
Partial-Bug: #1676586
Currently it is unclear that ceilometer is not actually ready when it
is related to gnocchi until the ceilometer-upgrade action has run. The
status will show active Unit is ready when it is not.
When gnocchi is related, check that the ceilometer-upgrade action has
been run. If not set workload status to prompt the administator to run
the action.
Please merge the charm-helpers change first:
https://github.com/juju/charm-helpers/pull/270
Partial-Bug: #1811108
Change-Id: Id778ed3f59e4bcde9c6586aad46be2b5b9ccb531
This change adds polling.yaml to the list of managed config files, for
Queens and above. Two new config items are added alongside the
template, to take into account a choice between the two polling.yaml
files supplied with the Ceilometer source, one which has a small list of
pollsters and the other which has all pollsters. Additionally the
change adds the option to set the polling interval.
Change-Id: Ifff72870cf79bea23dbd21586857dd832c9e1405
Closes-Bug: 1785933
Closes-Bug: 1652848
On charm upgrade the charm may switch to py3 packages. If so, ensure
the old py2 packages are purged. If the purge occurs then restart
services.
Change-Id: I23812e518d5d0ba64dff33ac8d704b8b0f829b7e
Closes-Bug: 1803451
This change adds the ability to listen for events across multiple
rabbit queues. Nova cells v2 has a message broker per cell and
the charms already support having a separate message broker for
neutron, in both these topologies ceilometer needs the ability to
listen to multiple brokers.
To achieve this a new relation 'amqp-listener' has been introduced.
The existing 'amqp' relation should be used for the broker that
ceilometer listens to and publishes to. 'amqp-listener' should be
used for additional brokers that ceilometer just listens on.
Update functional tests to satisfy relation with
nova-cloud-controller.
Change-Id: Ifdade3f7814620f4cd4a1d35a584cbc099bb6d88
The configuration file /etc/ceilometer/pipeline.yaml will be managed by
juju, currently it is not. On every change of this file
ceilometer-collector daemon is restarted.
Change-Id: Ie18a5284812f4f698b929b9e17b34289e7732bf7
Closes-Bug: 1715672
Switch package install to Python 3 for OpenStack Rocky or later.
When upgrading, remove any python-* packages that where explicitly
installated and then autoremove --purge any dependencies that are
no longer required.
Change-Id: I120ed44988f9e86a27f464dc879acdc1b8926dd8
A bug was causing the events yaml from being rendered on quuens+
deploys. This change adds it to the quuens+ configs.
Closes-Bug: 1773355
Change-Id: I309107da609e186638332d3a9bca00a86ccd6010
The ceilometer charm was assuming grizzly before the ceilometer-common
package was installed to determine the OS release. On queens deploys
this breaks due packages not being installed.
If ceilomter-common is not installed return empty configs.
Change-Id: Ib8bc1b7be3595bd8e64a25d0444dd768b80de881
Closes-Bug: #1759301
There is a use-case to forward events received by ceilometer from
OpenStack services to an external system via http/udp. It comes
from the fact that aodh does not include all information about an
event alarm into POSTed data. Raw event data can be published by
ceilometer via http/udp to an external system without giving a
user direct access to rabbitmq.
This patch adds a context generator, associated templates, and
configuration entry for configuring multiple event-sinks in
/etc/ceilometer/event_pipeline.yaml. This also modifies the
ceilometer.conf templates to reflect the correct naming of the
same file to align with upstream Ceilometer.
Also adds support for a future Panko charm event consumer using
the event-service interface in the above context with associated
metadata and hook symlinks.
This change will only effect Mitaka and later clouds.
Closes Bug: 1763321
Change-Id: I931438c720272bd9a3d2b958ebabcd3584790bd0
The ceilometer-upgrade command needs to be run to update back end
ceilometer data stores. When attempting to run this command during
deploy time due to the number of required relations many inherent
race conditions exist leading to Bug#1749280.
This change allows the ceilometer-upgrade command to be run as an action
post-deploy.
Change-Id: I64a56d9a38532476b8a01df6227231a1276c708f
Closes-Bug: #1749280
When there are multiple mongodb peers but replset has not yet been set
on the relation, do not complete the MongoDBContext. This causes the
template to be rendered incorrectly and leads to the following error:
ERROR ceilometer ValueError: Port must be an integer between 0 and
65535:
Closes-Bug: #1750639
Change-Id: Ifb9424ac5e175d788fa21de0ee332c0a13e61a9f
Ceilometer-upgrade is in a race with the keystone catalog for the
metric entry. The function already has a retry on error loop. Bump up
the delay between retries to mitigate the race with keystone.
Change-Id: I7fdf36a1cf480607744dcfed9628f0bf9e6daac0
Align ceilometer charm with worker-multiplier usage as found
across the majority of OpenStack Charms. Worker configuration
values are set for API, Notification and Collector services
as needed for each release. Note that for Ocata or later, API
services are executed as WSGI apps under Apache which was
already plugged into the standard worker calculation logic
in charm helpers.
This includes dropping of the existing api-worker configuration
option in preference to a calculated approach.
Change-Id: Idba7c3012d9d24b7ae6ef8eade4a5261ef1cbddc
Closes-Bug: #1745189
Sync charm-helpers to pick up the updated InternalEndpointsContext
which removes the need to provide a package.
This essentially reverts commit f76d0755 in favor of an alternative
approach to selecting the volume catalog endpoint information.
Change-Id: I4a985fe1b8885b14aefdfeda9a8c2c4914c5fc93
Related-Bug: #1733566
Update charm to support Ceilometer@Queens; specifically:
- Removal of Ceilometer API service
- Removal of ceilometer-collector service
Most of this change is related to dropping of these
services; In addition its now possible to complete a
ceilometer-upgrade without mongodb being configured.
As this charm no longer provides any endpoints to
keystone, for Queens the identity-credentials relation
is required instead of the identity-service relation.
Change-Id: I3cefc24ffc9a0e60f446fbbdff603dfad37f7baa
Ensure that the os_release cache is cleared during the openstack
upgrade process, ensuring that package list and configuration
options are correctly set for the new OpenStack version.
Change-Id: Ie685854952527f59ee344bfda8e49250c248150a
Closes-Bug: 1715624
Add support for use of internal endpoints for inter-service
API calls from ceilometer.
Change-Id: Id702de85fb2236f21773ee7f2fb3698012b5f16c
Closes-Bug: 1713923
Add new metric-service interface to support use of
Gnocchi as a storage backend for resource and metric
data.
Configure ceilometer to use the gnocchi dispatcher
in the event that ceilometer is related to gnocchi.
This has the side effect of disabling the ceilometer
API - Aodh and Gnocchi API's should be used directly
in this deployment topology.
Note that Gnocchi is only supported in OpenStack
Mitaka or later; 'metrics-service' is added to the
required interfaces configuration as an alternative
to 'mongodb' for >= Mitaka.
Change-Id: Ia31dfefd5efa3fb5ec2ba5d132ee865c567bd8df
- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
- fix tests which assumed mocks would just work on os_release()
Change-Id: I3d142f04bedc7dde12f3c079534cd43841fa8401
Related-Bug: #1659575
For large integer values, Juju can choose to return the number
in scientific notation. This causes the python code loading the
config data to return a floating point number instead of an
integer. Floating point values in ceilometer's configuration file
will prevent ceilometer from starting.
This change forces the type to an integer, allowing users to
specify large ttl values.
Change-Id: I8e29e6868b4c4a4ae20ad87ab585508fd321261c
Closes-Bug: #1651645
Since Liberty ceilometer-agent-central has been replaced with
ceilometer-polling. There is some confusion there as the package
is still named ceilometer-agent-central.
For OpenStack releases >= Liberty stop checking for the
ceilometer-agent-central service to be running.
TODO for post release: remove the OCF management of the service(s).
Change-Id: I5064ce130da1ec302245aaff5dbe93d9dab63b38
Partial-bug: #1664898
This change aligns with the Ocata ceilometer package, which has
moved the ceilometer-api to run under mod_wsgi with apache2.
Change-Id: I0f13f3bcb346182541376843a65d07f570f89442
With the release of 4.2.0 of keystonemiddleware using the
in-process token cache is no longer recommended. It is recommended
that a memcache backend to store tokens is used instead,
This installs and configures memcache and configures neutron-server
to use memcache for token caching.
http://docs.openstack.org/releasenotes/keystonemiddleware/mitaka.html#id2
Change-Id: I1f7764afb24b511508432fa758596cc9ab40aba8
If the charm enables https then apache is used to terminate ssl. As
part of this Apache listens on the port that the ceilometer API port
was listening on and the API service shuffles down to a lower port. If
the services are restarted one at a time and Apache goes first then
Apache will try and bind to the port the API service is listening on
because the API service has not yet been restarted to pick up its
new port.
Change-Id: Ied3224660948a9775c8000369cba0c287944cde5
Closes-Bug: 1632287
Ceilometer switched to using wsgi_script to generate the
ceilometer-api binary; this resulted in a few packaging changes,
including one which means the listen port for Ceilometer API is
set via the systemd unit, rather than the ceilometer.conf
configuration file.
Add systemd override file handling for ceilometer-api, including a
small workaround which ensures that the systemd daemon loads the
override configuration file when it changes (only possible during
config-changed with enabling SSL support).
This charm should switch to using Apache + mod_wsgi next cycle, at
which point all of that can just be dropped.
Change-Id: Ic8b359d0b91fda144925f5c75044f919e73aadd9
Closes-Bug: 1629796
Juju 2.0 provides support for display of the version of
an application deployed by a charm in juju status.
Insert the os_application_version_set function into the
existing assess_status function - this gets called after
all hook executions, and periodically after that, so any
changes in package versions due to normal system updates
will also be reflected in the status output.
This review also includes a resync of charm-helpers to
pickup hookenv and contrib.openstack support for this
feature.
Change-Id: I4cf3c3389def2a0dc9d0cd286aa8190cbfa59f9a
ceilometer.conf template >= Kilo does not contain metering-time-to-live
and event-time-to-live parameters. Add these options so we can control
ceilometer database growth.
Change-Id: Id5831280daeb582586bfa615268309c4abec5d63
Closes-Bug: 1561220
All contributions to this charm where made under Canonical
copyright; switch to Apache-2.0 license as agreed so we
can move forward with official project status.
Change-Id: I15bca9b973b61e408e25c113035702a596c45268
Adds improved pause and resume unit to the charm such tha the
charm stays paused during maintenance operations. Updates the
basic_deployment.py to use the the new version of
python-ceilometerclient (that's available in xenial, but works
back to icehouse/precise.
Change-Id: I869e467d0e4d9fecd661a6f946d45e31535ea11e
Rework ceilometer.conf to remove use of deprecated groups and options.
Don't install aodh alarming services for Mitaka; this will be handled in
a new aodh charm.
Rework upgrade tests from precise-havana -> trusty-kilo.
Change-Id: I74112fd6206665bbb7a20eaa5be15ac85116ae03
Gabriel Adrian Samfira