Install Ceilometer Enable Compute service meters for Red Hat Enterprise Linux an

admin

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

Install and configure components¶

• Install the packages:
  # yum install openstack-ceilometer-compute# yum install openstack-ceilometer-ipmi (optional)
  

• Edit the /etc/ceilometer/ceilometer.conf file and complete the following actions:
  
  
  
  , F$ f. e& P. d% @  f' j
  • In the [DEFAULT] section, configure RabbitMQ message queue access:
    [DEFAULT]...transport_url = rabbit://openstack:RABBIT_PASS@controller
    
    1 r0 h7 @: b( i7 ?; h! {9 o
    Replace RABBIT_PASS with the password you chose for the openstack account in RabbitMQ.
  • In the [service_credentials] section, configure service credentials:
    [service_credentials]...auth_url = http://controller:5000project_domain_id = defaultuser_domain_id = defaultauth_type = passwordusername = ceilometerproject_name = servicepassword = CEILOMETER_PASSinterface = internalURLregion_name = RegionOne
    
    # e* I- G- a( t& k! Z
    Replace CEILOMETER_PASS with the password you chose for the ceilometer user in the Identity service.
    
    
  
  $ p9 s& J+ k- e% r0 ~3 C, h! ]' u

% e" [$ f! x# o! f# U7 DConfigure Compute to use Telemetry¶

, D( n& T) Q6 m5 J8 M
• Edit the /etc/nova/nova.conf file and configure notifications in the [DEFAULT] section:
  [DEFAULT]...instance_usage_audit = Trueinstance_usage_audit_period = hournotify_on_state_change = vm_and_task_state[oslo_messaging_notifications]...driver = messagingv2
  

3 H5 j& g  }- wConfigure Compute to poll IPMI meters¶

4 q- i0 g- i3 l8 H! KNote

To enable IPMI meters, ensure IPMITool is installed and the host supports Intel Node Manager.

* u# r5 A) G- E! P6 W" ]
• Edit the /etc/sudoers file and include:
  .. code-block:: ini
  ' Z% r6 n0 p$ K1 e( ~' }
  6 e( x+ S8 `0 z8 l: E4 @$ O+ ]

  ceilometer ALL = (root) NOPASSWD: /usr/bin/ceilometer-rootwrap /etc/ceilometer/rootwrap.conf *

  
  

• Edit the /etc/ceilometer/polling.yaml to include the required meters, for example:
  .. code-block:: yaml
  ) x) u5 h! {& I' \$ R
  

  
  

  
  . V  Q. t1 A. |
  • name: ipmi interval: 300 meters:

    
    1 M. x7 L- T2 y- l1 I9 L

    
    0 _4 v; n1 u/ A0 q/ B: H1 H+ Z
    • hardware.ipmi.temperature
      

    
    

    
    

  
  . n% Q) F% |) U9 [, I9 @

  
  

Finalize installation¶

• Start the agent and configure it to start when the system boots:
  # systemctl enable openstack-ceilometer-compute.service# systemctl start openstack-ceilometer-compute.service# systemctl enable openstack-ceilometer-ipmi.service (optional)# systemctl start openstack-ceilometer-ipmi.service (optional)
• Restart the Compute service:
  # systemctl restart openstack-nova-compute.service
  9 V& x# i( J& ^9 q( `& L9 j7 e

9 Y" F+ {3 O$ I6 H

9 p: |# B& Y7 ^8 P/ ?

This section describes how to install and configure the Telemetry service, code-named ceilometer, on the controller node.

Prerequisites¶

Before you install and configure the Telemetry service, you must configure a target to send metering data to. The recommended endpoint is Gnocchi.

$ G! w5 t% K- ?6 m. Q+ C5 q# j
• Source the admin credentials to gain access to admin-only CLI commands:
  $ . admin-openrc
• To create the service credentials, complete these steps:
  
  
  
  7 Z6 r2 u" m# H7 `4 z: g
  • Create the ceilometer user:
    $ openstack user create --domain default --password-prompt ceilometerUser Password:Repeat User Password:+-----------+----------------------------------+| Field     | Value                            |+-----------+----------------------------------+| domain_id | e0353a670a9e496da891347c589539e9 || enabled   | True                             || id        | c859c96f57bd4989a8ea1a0b1d8ff7cd || name      | ceilometer                       |+-----------+----------------------------------+
  • Add the admin role to the ceilometer user.
    $ openstack role add --project service --user ceilometer admin
    6 J+ B( }/ p  g/ p& M7 I
    
    
    8 B) o* L9 \# q( Z( qNote
    , i( i' |( N: ]- s; w
    This command provides no output.
    
    ! ^1 K8 i; p6 _( Z; ]- q4 w
• Register Gnocchi service in Keystone:
  
  
  
  , V- B. v! u2 \4 D6 Z
  • Create the gnocchi user:
    $ openstack user create --domain default --password-prompt gnocchiUser Password:Repeat User Password:+-----------+----------------------------------+| Field     | Value                            |+-----------+----------------------------------+| domain_id | e0353a670a9e496da891347c589539e9 || enabled   | True                             || id        | 8bacd064f6434ef2b6bbfbedb79b0318 || name      | gnocchi                          |+-----------+----------------------------------+
  • Create the gnocchi service entity:
    $ openstack service create --name gnocchi \  --description "Metric Service" metric+-------------+----------------------------------+| Field       | Value                            |+-------------+----------------------------------+| description | Metric Service                   || enabled     | True                             || id          | 205978b411674e5a9990428f81d69384 || name        | gnocchi                          || type        | metric                           |+-------------+----------------------------------+
  • Add the admin role to the gnocchi user.
    $ openstack role add --project service --user gnocchi admin
    3 i$ _! j4 p/ N
    , y6 B; v$ x2 p
    
    Note
    
    This command provides no output.
  • Create the Metric service API endpoints:
    $ openstack endpoint create --region RegionOne \  metric public http://controller:8041+--------------+----------------------------------+| Field        | Value                            |+--------------+----------------------------------+| enabled      | True                             || id           | b808b67b848d443e9eaaa5e5d796970c || interface    | public                           || region       | RegionOne                        || region_id    | RegionOne                        || service_id   | 205978b411674e5a9990428f81d69384 || service_name | gnocchi                          || service_type | metric                           || url          | http://controller:8041           |+--------------+----------------------------------+$ openstack endpoint create --region RegionOne \  metric internal http://controller:8041+--------------+----------------------------------+| Field        | Value                            |+--------------+----------------------------------+| enabled      | True                             || id           | c7009b1c2ee54b71b771fa3d0ae4f948 || interface    | internal                         || region       | RegionOne                        || region_id    | RegionOne                        || service_id   | 205978b411674e5a9990428f81d69384 || service_name | gnocchi                          || service_type | metric                           || url          | http://controller:8041           |+--------------+----------------------------------+$ openstack endpoint create --region RegionOne \  metric admin http://controller:8041+--------------+----------------------------------+| Field        | Value                            |+--------------+----------------------------------+| enabled      | True                             || id           | b2c00566d0604551b5fe1540c699db3d || interface    | admin                            || region       | RegionOne                        || region_id    | RegionOne                        || service_id   | 205978b411674e5a9990428f81d69384 || service_name | gnocchi                          || service_type | metric                           || url          | http://controller:8041           |+--------------+----------------------------------+
      s+ ~8 X: F# V/ V9 y- X& s
  
  . V2 o* b) _9 [( N/ J

Install Gnocchi¶

! D4 y6 \3 A. o" M
• Install the Gnocchi packages. Alternatively, Gnocchi can be install using pip:
  # yum install openstack-gnocchi-api openstack-gnocchi-metricd \  python-gnocchiclient
  
  
  ) K- K4 [- f, F2 \, o8 y
  1 ^& l  B4 Q6 o; H- wNote
  
  Depending on your environment size, consider installing Gnocchi separately as it makes extensive use of the cpu.
  
  

• Create the database for Gnocchi’s indexer:
  
  
  
  3 U5 R! E7 B# r1 ?3 o5 n8 t4 ^
  • Use the database access client to connect to the database server as the root user:
    $ mysql -u root -p
  • Create the gnocchi database:
    CREATE DATABASE gnocchi;
  • Grant proper access to the gnocchi database:
    GRANT ALL PRIVILEGES ON gnocchi.* TO 'gnocchi'@'localhost' \  IDENTIFIED BY 'GNOCCHI_DBPASS';GRANT ALL PRIVILEGES ON gnocchi.* TO 'gnocchi'@'%' \  IDENTIFIED BY 'GNOCCHI_DBPASS';
    5 w* _' z5 V* i, ?
    
    Replace GNOCCHI_DBPASS with a suitable password.
  • Exit the database access client.
    
    
• Edit the /etc/gnocchi/gnocchi.conf file and add Keystone options:
  
  
  
  % a8 b' m4 D* y: b# t. \
  • In the [api] section, configure gnocchi to use keystone:
    [api]auth_mode = keystone
  • In the [keystone_authtoken] section, configure keystone authentication:
    [keystone_authtoken]...auth_type = passwordauth_url = http://controller:5000/v3project_domain_name = Defaultuser_domain_name = Defaultproject_name = serviceusername = gnocchipassword = GNOCCHI_PASSinterface = internalURLregion_name = RegionOne
    
    + L" D' ?5 `- x
    Replace GNOCCHI_PASS with the password you chose for the gnocchi user in the Identity service.
  • In the [indexer] section, configure database access:
    [indexer]url = mysql+pymysql://gnocchi:GNOCCHI_DBPASS@controller/gnocchi
    
    
    Replace GNOCCHI_DBPASS with the password you chose for Gnocchi’s indexer database.
  • In the [storage] section, configure location to store metric data. In this case, we will store it to the local file system. See Gnocchi documenation for a list of more durable and performant drivers:
    [storage]# coordination_url is not required but specifying one will improve# performance with better workload division across workers.coordination_url = redis://controller:6379file_basepath = /var/lib/gnocchidriver = file
    % p7 ?" L  @. i* n7 l7 `
• Initialize Gnocchi:
  gnocchi-upgrade
  ' K# }" J8 G3 D; j. d0 y2 t

Finalize Gnocchi installation¶

• Start the Gnocchi services and configure them to start when the system boots:
  # systemctl enable openstack-gnocchi-api.service \  openstack-gnocchi-metricd.service# systemctl start openstack-gnocchi-api.service \  openstack-gnocchi-metricd.service
  

Install and configure components¶

! O8 o- C- ?+ {0 I% V' p  @
• Install the Ceilometer packages:
  # yum install openstack-ceilometer-notification \  openstack-ceilometer-central
  & i) _/ Z& @: F- q$ k* ]

, i5 K! d3 l8 A2 X& D9 o% y
• Edit the /etc/ceilometer/pipeline.yaml file and complete the following section:
  
  
  
  ) d9 {& F/ F2 v* p: Y( U
  • Configure Gnocchi connection:
    publishers:    # set address of Gnocchi    # + filter out Gnocchi-related activity meters (Swift driver)    # + set default archive policy    - gnocchi://?filter_project=service&archive_policy=low
    9 y/ @( c7 ^: V# }% r& T
• Edit the /etc/ceilometer/ceilometer.conf file and complete the following actions:
  
  
  
  ' r3 O& s3 n5 u7 h+ c- k: L9 G/ a# z
  • In the [DEFAULT] section, configure RabbitMQ message queue access:
    [DEFAULT]...transport_url = rabbit://openstack:RABBIT_PASS@controller
    
    
    Replace RABBIT_PASS with the password you chose for the openstack account in RabbitMQ.
  • In the [service_credentials] section, configure service credentials:
    [service_credentials]...auth_type = passwordauth_url = http://controller:5000/v3project_domain_id = defaultuser_domain_id = defaultproject_name = serviceusername = ceilometerpassword = CEILOMETER_PASSinterface = internalURLregion_name = RegionOne
    
    
    Replace CEILOMETER_PASS with the password you chose for the ceilometer user in the Identity service.
    
      y2 p- ]) D/ d
• Create Ceilometer resources in Gnocchi. Gnocchi should be running by this stage:
  # ceilometer-upgrade
  3 }) v& A$ [" a7 j5 u

Finalize installation¶

• Start the Telemetry services and configure them to start when the system boots:
  # systemctl enable openstack-ceilometer-notification.service \  openstack-ceilometer-central.service# systemctl start openstack-ceilometer-notification.service \  openstack-ceilometer-central.service
  7 u- @" o' Q( h* l/ ^

9 O0 s/ ]& E  z. q! H9 ^3 k5 s

Telemetry uses notifications to collect Block Storage service meters. Perform these steps on the controller and Block Storage nodes.

- w. g/ q3 H" G& i  J
- }& g- I$ F. Q% m7 SNote

Your environment must include the Block Storage service.

( I  }5 J# }$ {% I2 V1 MConfigure Cinder to use Telemetry¶

Edit the /etc/cinder/cinder.conf file and complete the following actions:

• In the [oslo_messaging_notifications] section, configure notifications:
  [oslo_messaging_notifications]...driver = messagingv2
  
  
  

• Enable periodic usage statistics relating to block storage. To use it, you must run this command in the following format:
  $ cinder-volume-usage-audit  --start_time='YYYY-MM-DD HH:MM:SS' \  --end_time='YYYY-MM-DD HH:MM:SS' --send_actions
  1 O$ u3 o: H/ P- c% f
  
  This script outputs what volumes or snapshots were created, deleted, or exists in a given period of time and some information about these volumes or snapshots.
  Using this script via cron you can get notifications periodically, for example, every 5 minutes:
  */5 * * * * /path/to/cinder-volume-usage-audit --send_actions
  , j2 }  D" e0 @
  * a, t- H2 Q! l" s2 r4 e  X
  - a) e4 H% F5 ~; t& z, w

Finalize installation¶

• Restart the Block Storage services on the controller node:
  # systemctl restart openstack-cinder-api.service openstack-cinder-scheduler.service
  $ Y; K" Y* O/ i: z/ ^" M9 h
  
• Restart the Block Storage services on the storage nodes:
  # systemctl restart openstack-cinder-volume.service
  
  
  - H) b) Y" I7 g0 J* y5 y+ P, \, a* |

" I% V, l0 M9 j. ~2 @/ O) U