8342ff8968
stop telling people how to use deprecated/unmaintained stuff
- remove all db docs detailing mongo install/config
- cleanup get_started.rst
- remove note about future agents because i don't know what magic
it's hinting at.
- add note that collector is optional
- drop all notes about api service and notes about storage
- drop all stuff about configuring api with apache
- replace ceilometer+mongo config notes with ceilometer+gnocchi.
- remove keystone_authtoken config since no more api
- point all distro docs to gnocchi
- add a note to say api+storage is dead.
Change-Id: I494b4e7013ca146ffa640a356cacc4a1a5ee85e8
1.5 KiB
1.5 KiB
Install and configure for openSUSE and SUSE Linux Enterprise
This section describes how to install and configure the Telemetry service, code-named ceilometer, on the controller node.
This section assumes that you already have a working OpenStack environment with at least the following components installed: Compute, Image Service, Identity.
Prerequisites
Before you install and configure the Telemetry service, you must configure a target to send metering data to. The recommended endpoint is Gnocchi. To enable Gnocchi, please see its install guide.
Install and configure components
Install the packages:
# zypper install openstack-ceilometer-collector \ openstack-ceilometer-agent-notification \ openstack-ceilometer-agent-central python-ceilometerclient
Finalize installation
Start the Telemetry services and configure them to start when the system boots:
# systemctl enable openstack-ceilometer-agent-notification.service \ openstack-ceilometer-agent-central.service \ openstack-ceilometer-collector.service # systemctl start openstack-ceilometer-agent-notification.service \ openstack-ceilometer-agent-central.service \ openstack-ceilometer-collector.service