hi,
just to follow-up, thanks for the input, the usability of ceilometer is
obviously a concern of ours and something the team tries to address with the
resources we have.
as a quick help/update, here are some points of interests that i think might
help:- if using Juno+, DO use the notifier://
You bring up a very good point. What are the parts that are uniquely useful?
Here are two key reasons why we chose to bite the bullet and operationalize
Ceilometer at work:
1. Stable set of APIs for tenants to access and publish metrics and alarms
2. An unobtrusive way for providers to collect
Dent
Cc: openstack-operators
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience with
Ceilometer deployments - Feedback requested
You bring up a very good point. What are the parts that are uniquely useful?
Here are two key reasons why we chose to bite the bullet
On Thu, 12 Feb 2015, Clint Byrum wrote:
I wonder how hard it would be to push Ceilometer down the road of being
an OpenStack shim for collectd instead of a full implementation. This
would make the problem above go away, as collectd is written in C and is
well known to be highly optimized for
Excerpts from George Shuklin's message of 2015-02-11 17:59:02 -0800:
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.
I wonder how hard it would be to push Ceilometer down
We use StackTach only as a troubleshooting tool. If a user is having an
issue, we'll bring up their event history and review their timeline. I think
this alone makes it an invaluable tool.
+1 for StackTach as an invaluable troubleshooting tool.
It's probably worth calling out stacky CLI
February 2015 02:59
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience with
Ceilometer deployments - Feedback requested
Ceilometer is in sad state.
1. Collector leaks memory. We ran it on same host with mongo, and it grab 29Gb
out of 32
]
Sent: 12 February 2015 12:24
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience with
Ceilometer deployments - Feedback requested
Unfortunately, I can only confirm the sorry state of Ceilometer.
We tried it on a very small
Hi Tim,
Does anyone have any proposals regarding
- Possible replacements for Ceilometer that you have used instead
It seems that many sites have written their own systems.
Sorry - I should have appended this at the end of my last post.
I need to preface this with I have never used
Shuklin [mailto:george.shuk...@gmail.com]
Sent: Thursday 12 February 2015 02:59
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience with
Ceilometer deployments - Feedback requested
Ceilometer is in sad state.
1. Collector leaks
To: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience
with
Ceilometer deployments - Feedback requested
Unfortunately, I can only confirm the sorry state of Ceilometer.
We tried it on a very small setup (6 compute nodes) and run in so
From: Tim Bell [tim.b...@cern.ch]
Sent: Thursday, February 12, 2015 11:47 AM
To: Daniele Venzano; openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience with
Ceilometer deployments - Feedback requested
Does anyone have
Subject: Re: [Openstack-operators] [Ceilometer] Real world experience
with
Ceilometer deployments - Feedback requested
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
btw if you want to know how StackTach handles billing, here's the salient part
from our Hong Kong presentation [1]. Back when we were attempting Ceilometer
integration.
[1] http://youtu.be/c8zZtSL0t00?t=8m26s
___
OpenStack-operators mailing list
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
15 matches
Mail list logo
