blob: 7e59df89a003f77dffd30c1be766e4e1d04ced65 [file] [log] [blame]
Filip Pytlouna87b4712015-10-06 16:28:31 +02001
2==========
3Ceilometer
4==========
5
Jakub Pavlikf1514c62016-05-20 11:04:39 +02006The ceilometer project aims to deliver a unique point of contact for billing
7systems to acquire all of the measurements they need to establish customer
8billing, across all current OpenStack core components with work underway to
9support future OpenStack components.
Filip Pytlouna87b4712015-10-06 16:28:31 +020010
11Sample pillars
12==============
13
14Ceilometer API/controller node
15
16.. code-block:: yaml
17
18 ceilometer:
19 server:
20 enabled: true
21 version: havana
22 cluster: true
23 secret: pwd
24 bind:
25 host: 127.0.0.1
26 port: 8777
27 identity:
28 engine: keystone
29 host: 127.0.0.1
30 port: 35357
31 tenant: service
32 user: ceilometer
33 password: pwd
34 message_queue:
35 engine: rabbitmq
36 host: 127.0.0.1
37 port: 5672
38 user: openstack
39 password: pwd
40 virtual_host: '/openstack'
41 rabbit_ha_queues: true
42 database:
43 engine: mongodb
44 host: 127.0.0.1
45 port: 27017
46 name: ceilometer
47 user: ceilometer
48 password: pwd
49
50Ceilometer Graphite publisher
51
52.. code-block:: yaml
53
54 ceilometer:
55 server:
56 enabled: true
57 publisher:
58 graphite:
59 enabled: true
60 host: 10.0.0.1
61 port: 2003
62
63Ceilometer compute agent
64
65.. code-block:: yaml
66
67 ceilometer:
68 agent:
69 enabled: true
70 version: havana
71 secret: pwd
72 identity:
73 engine: keystone
74 host: 127.0.0.1
75 port: 35357
76 tenant: service
77 user: ceilometer
78 password: pwd
79 message_queue:
80 engine: rabbitmq
81 host: 127.0.0.1
82 port: 5672
83 user: openstack
84 password: pwd
85 virtual_host: '/openstack'
86 rabbit_ha_queues: true
87
88Read more
89=========
90
91* https://wiki.openstack.org/wiki/Ceilometer
92* http://docs.openstack.org/developer/ceilometer/install/manual.html
93* http://docs.openstack.org/developer/ceilometer/
94* https://fedoraproject.org/wiki/QA:Testcase_OpenStack_ceilometer_install
95* https://github.com/spilgames/ceilometer_graphite_publisher
96* http://engineering.spilgames.com/using-ceilometer-graphite/
97
98Things to improve/consider
99==========================
100
101* Graphite publisher http://engineering.spilgames.com/using-ceilometer-graphite/
Jakub Pavlikf1514c62016-05-20 11:04:39 +0200102* Juno additions - Split Events/Meters and Alarms databases, Polling angets are
103HA now, active/Activr Workload partitioning to central agents
104* Kilo additions - Splint Events - Meters - Agents, notification agents are HA
105now (everything is HA now), events - elastic search
Filip Pytlouna87b4712015-10-06 16:28:31 +0200106* User notifier publisher vs rpc publisher (Juno+)
107* Enable jittering (rendom delay) to polling. (Kilo+)
108* Collect what you need - pipeline.yaml, tweak polling interval (Icehouse+)
109* add more agents as load inceases (Juno+)
110* Avoid open-ended queries - query on a time range
111* Install api behind mod_wsgi, tweak wsgi daemon - threads and processes
112* Set TTL - expire data to minimise database size
113* Run Mongodb on separate node - use sharding and replica-sets
114
115Deployment scenarios
116--------------------
117
118* Lambda design - use short term and long term databases in the same time
119* Data segragation - separatem
120* JSON files - Apache spark
121* Fraud detection - proprietary alarming system
122* Custom consumers - kafka - Apache Storm (kilo+)
123* Debugging - Collecttions - Elastic serach - Kibana
124* Noisy services - Multiple notification buses
Jakub Pavlikf1514c62016-05-20 11:04:39 +0200125
126Documentation and Bugs
127============================
128
129To learn how to deploy OpenStack Salt, consult the documentation available
130online at:
131
132 https://wiki.openstack.org/wiki/OpenStackSalt
133
134In the unfortunate event that bugs are discovered, they should be reported to
135the appropriate bug tracker. If you obtained the software from a 3rd party
136operating system vendor, it is often wise to use their own bug tracker for
137reporting problems. In all other cases use the master OpenStack bug tracker,
138available at:
139
140 http://bugs.launchpad.net/openstack-salt
141
142Developers wishing to work on the OpenStack Salt project should always base
143their work on the latest formulas code, available from the master GIT
144repository at:
145
146 https://git.openstack.org/cgit/openstack/salt-formula-ceilometer
147
148Developers should also join the discussion on the IRC list, at:
149
150 https://wiki.openstack.org/wiki/Meetings/openstack-salt