Ceilometer has several daemons. The basic are: polling agent running either on the Nova compute node(s) or polling agent running on the central management node(s), collector and notification agent running 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.
Note
In fact, previously ceilometer had separated compute and central agents, and their support is implemented in devstack right now, not one agent variant. For now we do have deprecated cmd scripts emulating old compute/central behavior using namespaces option passed to polling agent, which will be maintained for a transitional period.
Download devstack.
Create a local.conf file as input to devstack.
Ceilometer makes extensive use of the messaging bus, but has not yet been tested with ZeroMQ. We recommend using Rabbit for now. By default, RabbitMQ will be used by devstack.
The ceilometer services are not enabled by default, so they must be enabled in local.conf before running stack.sh.
This example local.conf file shows all of the settings required for ceilometer:
[[local|localrc]]
# Enable the Ceilometer devstack plugin
enable_plugin ceilometer https://git.openstack.org/openstack/ceilometer.git
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 and restart the service.
Cinder does not generate notifications by default. To enable these auditing events, set the following in the cinder configuration file and restart the service:
notification_driver=messagingv2