Juju Charm - Ceilometer
Go to file
Alex Kavanagh 9ea1a00bca Updates for caracal testing support
These updates, on the master branch, are to support testing the caracal
packages and support of the charms for caracal.  They do NOT lock the charms
down, and don't change the testing branches to stable branches.

Change-Id: I41641bebf78705ca3f5a3e09b8ac918a44a863aa
2024-02-24 19:53:10 +00:00
actions Sync libraries & common files prior to freeze 2020-09-27 15:27:11 +01:00
charmhelpers Updates for caracal testing support 2024-02-24 19:53:10 +00:00
files Sync charm/ceph helpers, tox, and requirements 2019-09-30 22:41:27 -05:00
hooks Fix restart when endpoint notification is received 2020-08-20 09:17:58 +00:00
lib Add missing region setting in service_credentials 2024-01-05 17:59:18 +02:00
templates Add missing region setting in service_credentials 2024-01-05 17:59:18 +02:00
tests Updates for caracal testing support 2024-02-24 19:53:10 +00:00
unit_tests Add missing region setting in service_credentials 2024-01-05 17:59:18 +02:00
.coveragerc Add unit tests, tidylint 2013-10-20 12:32:35 -07:00
.gitignore Update to classic charms to build using charmcraft in CI 2022-02-17 12:30:02 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:35:44 +00:00
.stestr.conf Replace ostestr with stestr in testing framework. 2019-03-07 17:10:08 -05:00
.zuul.yaml Add Antelope support 2023-03-07 20:32:46 +00:00
LICENSE Re-license charm as Apache-2.0 2016-06-28 11:36:46 +01:00
Makefile Porting tests from Amulet to Zaza and support for Python 3.8 2020-03-05 12:08:25 +01:00
README.md [DOC] Update ceilometer-upgrade action note 2022-09-01 15:30:08 -03:00
actions.yaml Fix typo in actions.yaml 2023-08-08 11:18:20 -04:00
bindep.txt Add Kinetic and Zed support 2022-08-26 18:40:27 +00:00
charm-helpers-hooks.yaml charm-helpers-sync for release 2022-04-07 15:58:29 +01:00
charmcraft.yaml Updates for caracal testing support 2024-02-24 19:53:10 +00:00
config.yaml Support disabling apache wsgi socket rotation 2023-10-17 18:13:35 +08:00
copyright Drop use of openstack OCF resources 2017-09-25 13:10:23 +01:00
hardening.yaml Add hardening support 2016-03-24 11:12:40 +00:00
icon.svg Update charm icon 2017-08-02 17:47:21 +01:00
metadata.yaml Updates for caracal testing support 2024-02-24 19:53:10 +00:00
osci.yaml Add 2023.2 Bobcat support 2023-08-08 21:17:05 +00:00
rename.sh Update to classic charms to build using charmcraft in CI 2022-02-17 12:30:02 -05:00
requirements.txt Add Kinetic and Zed support 2022-08-26 18:40:27 +00:00
test-requirements.txt Add Antelope support 2023-03-07 20:32:46 +00:00
tox.ini Updates for caracal testing support 2024-02-24 19:53:10 +00:00



This charm provides the Ceilometer service for OpenStack.

Ceilometer is made up of 2 separate services: an API service, and a collector service. This charm allows them to be deployed in different combination, depending on user preference and requirements.


In order to deploy Ceilometer service (prior to Queens), the MongoDB service is required:

juju deploy mongodb
juju deploy ceilometer
juju add-relation ceilometer mongodb

For OpenStack Queens or later, Gnocchi should be used instead of MongoDB for resource, metrics and measure storage:

juju add-relation ceilometer gnocchi

Note: When ceilometer is related to gnocchi the ceilometer-upgrade action must be run post deployment in order to update its data store in gnocchi. It is not strictly necessary to re-run this action on every charm or OpenStack release upgrade. If re-running it, be aware that it may override any gnocchi resource-type adjustments that would have been made.

juju run-action ceilometer/0 ceilometer-upgrade

then Keystone and Rabbit relationships need to be established:

juju add-relation ceilometer:amqp rabbitmq
juju add-relation ceilometer keystone:identity-service
juju add-relation ceilometer keystone:identity-notifications

For OpenStack Queens, the identity-service relation must be replaced with the identity-credentials relation:

juju add-relation ceilometer keystone:identity-credentials

Ceilometer@Queens does not provide an API service.

In order to capture the calculations, a Ceilometer compute agent needs to be installed in each nova node, and be related with Ceilometer service:

juju deploy ceilometer-agent
juju add-relation ceilometer-agent nova-compute
juju add-relation ceilometer-agent:amqp rabbitmq-server:amqp
juju add-relation ceilometer:ceilometer-service ceilometer-agent:ceilometer-service

Ceilometer provides an API service that can be used to retrieve Openstack metrics.

If ceilometer needs to listen to multiple message queues then use the amqp interface to relate ceilometer to the message broker that it should publish to and use the amqp-listener interface for all message brokers ceilometer should monitor.

juju add-relation ceilometer:amqp rabbitmq-central
juju add-relation ceilometer:amqp-listener rabbitmq-neutron
juju add-relation ceilometer:amqp-listener rabbitmq-nova-cell2

High availability

When more than one unit is deployed with the hacluster application the charm will bring up an HA active/active cluster.

There are two mutually exclusive high availability options: using virtual IP(s) or DNS. In both cases the hacluster subordinate charm is used to provide the Corosync and Pacemaker backend HA functionality.

See OpenStack high availability in the OpenStack Charms Deployment Guide for details.

Network Space support

This charm supports the use of Juju Network Spaces, allowing the charm to be bound to network space configurations managed directly by Juju. This is only supported with Juju 2.0 and above.

API endpoints can be bound to distinct network spaces supporting the network separation of public, internal and admin endpoints.

To use this feature, use the --bind option when deploying the charm:

juju deploy ceilometer --bind "public=public-space internal=internal-space admin=admin-space"

alternatively these can also be provided as part of a juju native bundle configuration:

  charm: cs:ceilometer
    public: public-space
    admin: admin-space
    internal: internal-space

NOTE: Spaces must be configured in the underlying provider prior to attempting to use them.

NOTE: Existing deployments using os-*-network configuration options will continue to function; these options are preferred over any network space binding provided if set.