openstack-manuals/doc/install-guide/source/ceilometer-nova.rst
Christian Berendt e708842d7b [install] cleanup list syntax
* replace 1., 2., .. with #. where possible
* replace a., b., .. with *
* flatten some lists

Change-Id: Icdae64a44fee7911022331081c07d717d797506e
Implements: blueprint installguide-liberty
2015-10-09 10:13:55 +02:00

5.4 KiB

Configure the Compute service

Telemetry uses a combination of notifications and an agent to collect Compute meters. Perform these steps on each compute node.

To install and configure the agent

obs

  1. Install the packages:

    # zypper install openstack-ceilometer-agent-compute

rdo

  1. Install the packages:

    # yum install openstack-ceilometer-compute python-ceilometerclient python-pecan

ubuntu

  1. Install the packages:

    # apt-get install ceilometer-agent-compute
  1. Edit the /etc/ceilometer/ceilometer.conf file and complete the following actions:
    • In the [publisher] section, configure the telemetry secret:

      [publisher]
      ...
      telemetry_secret = TELEMETRY_SECRET

      Replace TELEMETRY_SECRET with the telemetry secret you chose for the Telemetry module.

    • In the [DEFAULT] and [oslo_messaging_rabbit] sections, configure RabbitMQ message queue access:

      [DEFAULT]
      ...
      rpc_backend = rabbit
      
      [oslo_messaging_rabbit]
      ...
      rabbit_host = controller
      rabbit_userid = openstack
      rabbit_password = RABBIT_PASS

      Replace RABBIT_PASS with the password you chose for the openstack account in RabbitMQ.

    • In the [keystone_authtoken] section, configure Identity service access:

      [keystone_authtoken]
      ...
      auth_uri = http://controller:5000/v2.0
      identity_uri = http://controller:35357
      admin_tenant_name = service
      admin_user = ceilometer
      admin_password = CEILOMETER_PASS

      Replace CEILOMETER_PASS with the password you chose for the Telemetry module database.

      Note

      Comment out any auth_host, auth_port, and auth_protocol options because the identity_uri option replaces them.

    • In the [service_credentials] section, configure service credentials:

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

      Replace CEILOMETER_PASS with the password you chose for the ceilometer user in the Identity service.

    • (Optional) To assist with troubleshooting, enable verbose logging in the [DEFAULT] section:

      [DEFAULT]
      ...
      verbose = True

To configure notifications

Configure the Compute service to send notifications to the message bus.

Edit the /etc/nova/nova.conf file and configure notifications in the [DEFAULT] section:

[DEFAULT]
...
instance_usage_audit = True
instance_usage_audit_period = hour
notify_on_state_change = vm_and_task_state
notification_driver = messagingv2

The Nova notification_driver creates alerts and sends system state updates to administrators and users. The notification_driver sends this information to users in a manner as close to real-time as possible.

Notifications in real-time allow administrars to observe and resolve emergencies when the cloud environment experiences errors or faults.

Administrators can also restrict notification delivery to certain tenant groups. Users can view notifications through a web browser, without using a specific interface.

Messages arrive in a specific format which includes: Message ID, Publisher ID, Event type, Timestamp, Priority, and Payload. See the Notification System information <https://wiki.openstack.org/wiki/ NotificationSystem#General_Notification_Message_Format>__ for an example message format.

Notification messages are placed on the OpenStack messaging system, which recruits AMQP to send information when an event triggers alerts.

The nova.conf file uses the nova_notification driver by defualt.

Warning

While you can use a customised notification_driver, we recommend using the default settings. Using stable web hooks for events, such as creating new instances, and using custom notification drivers are not guaranteed to deliver notifications in real-time.

To finalize installation

obs

  1. Start the Telemetry agent and configure it to start when the system boots:

    # systemctl enable openstack-ceilometer-agent-compute.service
    # systemctl start openstack-ceilometer-agent-compute.service

rdo

  1. Start the Telemetry agent and configure it to start when the system boots:

    # systemctl enable openstack-ceilometer-compute.service
    # systemctl start openstack-ceilometer-compute.service

obs or rdo

  1. Restart the Compute service:

    # systemctl restart openstack-nova-compute.service

ubuntu

  1. Restart the agent:

    # service ceilometer-agent-compute restart
  2. Restart the Compute service:

    # service nova-compute restart