Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ceilometer Pipeline DB Storage

Strategy and Design principles to store samples pipeline configuration in Database. This allows dynamic changes to the pipeline without service restart. It could also allow simplified service on-boarding.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

  • Be the first to like this

Ceilometer Pipeline DB Storage

  1. 1. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Ceilometer Pipeline Configuration DB Storage Fabio Giannetti and Rohit Jaiswal February 2015
  2. 2. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.2 Introduction Ceilometer uses the pipeline configuration (pipeline.yml) as a way to define the “producers” and “consumers” for meters. The sources from where the meters are harvested are defined in the sources part and the transformation are re-publishing details are stored in the sinks part. These are the two main parts that have a unique id (using a name) and have a many-to-many relationship between them, i.e. one source can have many sinks and one sink can have many sources.
  3. 3. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.3 Scope The change has the scope of allowing pipeline changes without having to re-start the Ceilometer Notification, Central and Compute Agent. These Agents can now periodically verify if there has been a change in the pipeline and dynamically re-load the new pipeline and apply the necessary changes. This should also simplify services onboarding for Ceilometer.
  4. 4. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.4 Overall Design
  5. 5. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.5 Using Pipeline Stored by API Pipeline is loaded by a client REST call. The call can contain the pipeline definition in the payload or it is an external reference. Pipeline data is stored in a separate persistence layer that is independent from Meters and Samples.
  6. 6. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.6 Using Pipeline Stored by Agent Agent is started and the ceilometer.conf has the parameter to store pipeline in the db as true. Agent verify there isn’t already a pipeline available. If there isn’t it will store the one specified in its starting parameter or default location.
  7. 7. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.7 Agent Checking for Changes Agent is periodically verifying that the pipeline has not changed using a configuration setting for the interval value. Once a new pipeline has been detected it will re-load the pipeline from the database and apply the changes without restarting.
  8. 8. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.8 Patching Sources/Sinks Clients can patch, replace or add sources or sinks in case they want to perform partial changes to the overall pipeline. Agents are reacting to the change the same way it was a completely new pipeline.
  9. 9. © Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Thank you The OpenStack word mark and the Square O Design, together or apart, are trademarks or registered trademarks of OpenStack Foundation in the United States and other countries, and are used with the OpenStack Foundation's permission.

    Be the first to comment

    Login to see the comments

Strategy and Design principles to store samples pipeline configuration in Database. This allows dynamic changes to the pipeline without service restart. It could also allow simplified service on-boarding.

Views

Total views

791

On Slideshare

0

From embeds

0

Number of embeds

12

Actions

Downloads

20

Shares

0

Comments

0

Likes

0

×