
Adding information about some daemons of Ceilometer. Change-Id: Ib31588f962d393cb2c1d9ee96e9d62b8898233cc Closes-Bug: 1368938
3.2 KiB
Installing and Running the Development Version
Ceilometer has several daemons. The basic are: compute agent
runs on the
Nova compute node(s) while the central agent
, collector
and notification agent
run on the cloud's management
node(s). In a development environment created by devstack, these services are
typically running on the same server. They do not have to be, though, so
some of the instructions below are duplicated. Skip the steps you have
already done.
Configuring Devstack
double: installing; devstack
Create a
local.conf
file as input to devstack.Note
local.conf
replaces the former configuration file calledlocalrc
. If you used localrc before, remove it to switch to using the new file. For further information see the localrc description page or devstack configuration.Ceilometer makes extensive use of the messaging bus, but has not yet been tested with ZeroMQ. We recommend using Rabbit or qpid for now.
Nova does not generate the periodic notifications for all known instances by default. To enable these auditing events, set
instance_usage_audit
to true in the nova configuration file.Cinder does not generate notifications by default. To enable these auditing events, set the following in the cinder configuration file:
notification_driver=cinder.openstack.common.notifier.rpc_notifier
The ceilometer services are not enabled by default, so they must be enabled in
local.conf
before runningstack.sh
.This example
local.conf
file shows all of the settings required for ceilometer:[[local|localrc]] # Enable the ceilometer metering services enable_service ceilometer-acompute ceilometer-acentral ceilometer-anotification ceilometer-collector # Enable the ceilometer alarming services enable_service ceilometer-alarm-evaluator,ceilometer-alarm-notifier # Enable the ceilometer api services enable_service ceilometer-api
The first group of daemons are necessary for core ceilometer functionality: polling, event listening, and data collection.
- If you use Data Processing (Sahara) service at your DevStack, it will generate notifications by default.