the docs are a bit wordy in some places. our docs are confusing enough: - remove notification > polling in architecture page - remove redundant Events filtering from event_types - move shuffle/batch options to customisation page - add http publisher - remove db choices from architecture page, point to dbreco page - remove db background referencing single database route - remove warnings to say db might change, use api (obvious) - remove stuff about Ceilometer is part Openstack but not tied to it - move hbase configuration under common hbase section in install - remove tox compatibility comments since it's > 2 years - remove random non-devstack/historical text from devstack page - remove default cinder/nova configurations from devstack page Change-Id: Ifdbeee358cfcb5d3736608e39067ff2859cc0ed6
2.0 KiB
Installing development sandbox
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.
Configuring devstack
double: installing; devstack
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 runningstack.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
By default, all ceilometer services except for ceilometer-ipmi agent will be enabled