Install the Telemetry module

Telemetry provides an API service that provides a collector and a range of disparate agents. Before you can install these agents on nodes such as the compute node, you must use this procedure to install the core components on the controller node.

1. Install the Telemetry service on the controller node:

   # apt-get install ceilometer-api ceilometer-collector ceilometer-agent-central \
     ceilometer-agent-notification ceilometer-alarm-evaluator ceilometer-alarm-notifier python-ceilometerclient

2. Respond to the prompts for [keystone_authtoken] settings, RabbitMQ credentials and API endpoint registration.

3. The Telemetry service uses a database to store information. Specify the location of the database in the configuration file. The examples use a MongoDB database on the controller node:

   # apt-get install mongodb-server

   Note

   By default MongoDB is configured to create several 1 GB files in the /var/lib/mongodb/journal/ directory to support database journaling. If you need to minimize the space allocated to support database journaling then set the smallfiles configuration key to true in the /etc/mongodb.conf configuration file. This configuration reduces the size of each journaling file to 512 MB. As the files are created the first time the MongoDB service starts you must stop the service and remove the files for this change to take effect: # service mongodb stop # rm /var/lib/mongodb/journal/prealloc.* # service mongodb start For more information on the smallfiles configuration key refer to the MongoDB documentation at http://docs.mongodb.org/manual/reference/configuration-options/#smallfiles. For instructions detailing the steps to disable database journaling entirely refer to http://docs.mongodb.org/manual/tutorial/manage-journaling/.

4. Configure MongoDB to make it listen on the controller management IP address. Edit the /etc/mongodb.conf file and modify the bind_ip key:

   bind_ip = 10.0.0.11

5. Restart the MongoDB service to apply the configuration change:

   # service mongodb restart

6. Create the database and a ceilometer database user:

   # mongo --host controller --eval '
   db = db.getSiblingDB("ceilometer");
   db.addUser({user: "ceilometer",
               pwd: "CEILOMETER_DBPASS",
               roles: [ "readWrite", "dbAdmin" ]})'

7. Configure the Telemetry service to use the database:

   Edit the /etc/ceilometer/ceilometer.conf file and change the [database] section:

   [database]
   # The SQLAlchemy connection string used to connect to the
   # database (string value)
   connection = mongodb://ceilometer:CEILOMETER_DBPASS@controller:27017/ceilometer

8. You must define a secret key that is used as a shared secret among Telemetry service nodes. Use openssl to generate a random token and store it in the configuration file:

   # openssl rand -hex 10

   Edit the /etc/ceilometer/ceilometer.conf file and change the [publisher] section. Replace CEILOMETER_TOKEN with the results of the openssl command:

   [publisher]
   # Secret value for signing metering messages (string value)
   metering_secret = CEILOMETER_TOKEN

9. Add the credentials to the configuration files for the Telemetry service:

   Edit the /etc/ceilometer/ceilometer.conf file and change the [keystone_authtoken] section:

   [keystone_authtoken]
   auth_host = controller
   auth_port = 35357
   auth_protocol = http
   auth_uri = http://controller:5000
   admin_tenant_name = service
   admin_user = ceilometer
   admin_password = CEILOMETER_PASS

   Also set the [service_credentials] section:

   [service_credentials]
   os_auth_url = http://controller:5000/v2.0
   os_username = ceilometer
   os_tenant_name = service
   os_password = CEILOMETER_PASS

10. Restart the services with their new settings:

    # service ceilometer-agent-central restart
    # service ceilometer-agent-notification restart
    # service ceilometer-api restart
    # service ceilometer-collector restart
    # service ceilometer-alarm-evaluator restart
    # service ceilometer-alarm-notifier restart