Ceilometer lsf-intergration-openstack-summit

1,048 views
851 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,048
On SlideShare
0
From Embeds
0
Number of Embeds
30
Actions
Shares
0
Downloads
21
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ceilometer lsf-intergration-openstack-summit

  1. 1. CeilometerCERN use case:● CERN delivers resources in form of virtual machines and via traditionalbatch and Grid computing● Individual batch nodes execute payload from different users andcommunities● Accounting should cover both use cases● Interesting metrics include● What is the resource usage of experiment A during December ?● What is the resource usage of user B last year ?● Accounting information has to be reported to Grid bodies (WLCG) byexperimentFacts:● Details of users jobs present in batch accounting database already● It is a huge DB with around 400,000 records being added everydaySolution● Use of ceilometer as single source of truth for accounting data● Batch data is put in the ceilometer database for accounting purpose
  2. 2. CERNs idea to use ceilometer
  3. 3. Ceilometer: Current ImplementationCeilometerAgent CentralWith batch PluginCeilometerCollectorfor batch DataCeilometerDatabase(mongodb)RabbitMQRabbitMQ-LSFCeilometerAgentCentralCeilometerCollectorCeilometerAPICeilometerAgentComputebatch specificinstancesBatchaccountingdatabaseIaaS specificinstances
  4. 4. Ceilometer: Current Implementation● Written a ceilometer-agent-central plugin, which pollsthe batch accounting database for unpublished records● The unpublished records are then pushed to meteringqueue (RabbitMQ)● The ceilometer-collector instance consumes themessages from the metering queue and inserts them inthe ceilometer database (mongodb)
  5. 5. Ceilometer: Current Implementation● In order to decrease the load on the openstackmessaging server, the batch data is being pushed to adifferent messaging server than the one to which otheropenstack messages (e.g. those from agent-compute)go.● This means that there are dedicated instances ofagent-central and collector for VM and batch metering● The collectors writes the data into a single database
  6. 6. Ceilometer: LSF Data Statistics● The batch plugin is run once per hour if the previousrun has finished● Most runs do not have any unpublished data as data inthe batch accounting database arrives in bursts● Most data of the day is published to the messagingserver within 2 runs of around 200,000 job recordseach● It takes around 5 hrs to complete one such run
  7. 7. Ceilometer: Batch Data Statistics● The average rate of record publishing to the batchrabbitmq server is 11 Hz. This includes– the time to read unpublished records,– push them to the rabbit-server and– marking records in batch accounting database aspublished● Most of this time is spent in records publishing only● The time for activities other than publishing isminuscule● The grow rate of the mongodb database is about2GB/day

×