deb-ceilometer/doc/source/install.rst
Julien Danjou 8229941dcf Add nova_notifier notification driver for nova
This adds a new notification driver to be used by nova in order to intercept
instance deletion message before the instance is deleted. With this, we are
able to poll an instance about to be deleted before it disappers and
therefore not miss any meter.

This fixes bug #1005944

Change-Id: Ie039681e8e440cb9be2f30e3d72d9a2bc4ddf5ba
Signed-off-by: Julien Danjou <julien@danjou.info>
2012-09-18 00:31:08 +02:00

2.5 KiB

Installing and Running the Development Version

Ceilometer has four daemons. The compute agent runs on the Nova compute node(s) while the central agent and collector run on the cloud's management node(s). In a development environment created by devstack, these two are typically 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

  1. Create a localrc file as input to devstack.
  2. Ceilometer makes extensive use of the messaging bus, but has not yet been tested with ZeroMQ. We recommend using Rabbit or qpid for now.
  3. 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.
  4. The ceilometer services are not enabled by default, so they must be enabled in localrc before running stack.sh.

This example localrc file shows all of the settings required for ceilometer:

# Configure the notifier to talk to the message queue
# and turn on usage audit events
EXTRA_OPTS=(notification_driver=nova.openstack.common.notifier.rabbit_notifier,ceilometer.compute.nova_notifier)

# Enable the ceilometer services
enable_service ceilometer-acompute,ceilometer-acentral,ceilometer-collector

Running the API Server

double: installing; API

$ ceilometer-api

Note

The development version of the API server logs to stderr, so you may want to run this step using a screen session or other tool for maintaining a long-running program in the background.