Ceilometer is in sad state.
1. Collector leaks memory. We ran it on same host with mongo, and it
grab 29Gb out of 32, leaving mongo with less than gig memory available.
2. Metering agent cause huge load on neutron-server. o(n) of metering
rules and tenants. Few bugs reported, one bugfix in review.
3. Metering agent simply do no work on multi-network-nodes installation.
It exepects all routers be on same host. Fixed or not - I don't know, we
have our own crude fix.
4. Many rough edges. Ceilometer much less tested than nova. Sometimes it
traces and skip counting. Fresh example: if metadata has '.' in the
name, ceilometer trace on it and did not count in glance usage.
5. Very slow on reports (using mongo's mapreduce).
Overall feeling: barely usable, but with my experience with cloud
billings, not the worst thing I saw in my life.
About load: except reporting and memory leaks, it use rather small
amount of resources.
On 02/11/2015 09:37 PM, Maish Saidel-Keesing wrote:
Is Ceilometer ready for prime time?
I would be interested in hearing from people who have deployed
OpenStack clouds with Ceilometer, and their experience. Some of the
topics I am looking for feedback on are:
- Database Size
- MongoDB management, Sharding, replica sets etc.
- Replication strategies
- Database backup/restore
- Overall useability
- Gripes, pains and problems (things to look out for)
- Possible replacements for Ceilometer that you have used instead
If you are willing to share - I am sure it will be beneficial to the
whole community.
Thanks in Advance
With best regards,
Maish Saidel-Keesing
Platform Architect
Cisco
_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
