Configure the Object Storage service for Telemetry
Install the python-ceilometerclient
package on your Object Storage proxy server:
# apt-get install python-ceilometerclient
# yum install python-ceilometerclient
# zypper install python-ceilometerclient
To retrieve object store statistics, the Telemetry service
needs access to Object Storage with the
ResellerAdmin role. Give this role to
your os_username user for the
os_tenant_name tenant:
$ keystone role-create --name ResellerAdmin
+----------+----------------------------------+
| Property | Value |
+----------+----------------------------------+
| id | 462fa46c13fd4798a95a3bfbe27b5e54 |
| name | ResellerAdmin |
+----------+----------------------------------+
$ keystone user-role-add --tenant service --user ceilometer \
--role 462fa46c13fd4798a95a3bfbe27b5e54
You must also add the Telemetry middleware to Object
Storage to handle incoming and outgoing traffic. Add
these lines to the
/etc/swift/proxy-server.conf
file:
[filter:ceilometer]
use = egg:ceilometer#swift
Add ceilometer to the
pipeline parameter of that same file:
[pipeline:main]
pipeline = healthcheck cache authtoken keystoneauth ceilometer proxy-server
Add the system user swift to the system group
ceilometer to give Object Storage access to the
ceilometer.conf file.
# usermod -a -G ceilometer swift
Add ResellerAdmin to the
operator_roles parameter of that same file:
operator_roles = Member,admin,swiftoperator,_member_,ResellerAdmin
Restart the service with its new settings:
# service swift-proxy restart
# systemctl restart openstack-swift-proxy.service
On SLES:
# service openstack-swift-proxy restart
On openSUSE:
# systemctl restart openstack-swift-proxy.service