Jump to: navigation, search

Ceilometer/blueprints/configuration-management-in-ceilometer

< Ceilometer‎ | blueprints
Revision as of 06:36, 16 June 2015 by Izhilong (talk | contribs) (Created page with "Provide a visualizing, easy-to-use way to view, modify and customize pipeline configuration for Ceilometer, instead of manually modifying configuration files. == Problem desc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Provide a visualizing, easy-to-use way to view, modify and customize pipeline configuration for Ceilometer, instead of manually modifying configuration files.

Problem description

Currently, pipeline configuration files, which are separately stored across the OpenStack cluster, are used to define how data is collected and processed in Ceilometer.

Although flexible in functionality, this method is not convenient in practice. To adjust polling and sample storing mechanism towards certain instances, admin users have to pinpoint the corresponding compute nodes and then modify the configuration files remotely and manually. This method is also error-prone, considering the manual configuration file modification.

To resolve these problems, a visualizing easy-to-use pipeline configuration method via dashboard is needed by adding API level support.

Proposed change

New REST APIs will be added into Ceilometer to allow users to change pipeline configuration files conveniently. In addition, new web pages will be integrated into the dashboard.

Alternatives

Data model impact

REST API impact

The proposed APIs are:

GET /v2/pipeline/instance/<uuid>

Return pipeline configuration.

GET /v2/pipeline/tenant/<uuid>

Return a list of pipeline configuration of instances belonging to a tenant.

POST /v2/pipeline/instance/<uuid>

Update pipeline configuration.

Security impact

Pipeline impact

Other end user impact

The proposed APIs and configuration via dashboard will relieve the burdens of admin users and improve system robustness.

Performance/Scalability Impacts

Other deployer impact

Developer impact

Implementation

Assignee(s)

Work Items

Future lifecycle

Dependencies

Testing

Documentation Impact

References