On Tue, 9 Jun 2015, Luo Gangyi wrote:
In current, ceilometer load pollsters by agent namespace, So do you
mean you want load pollsters one by one through their name(maybe
defined in pipeline.yaml)?
If loading all pollsters in one time do not cost much, I think your
change is bit unnecessary.
On Tue, 9 Jun 2015, gordon chung wrote:
i still like the idea of splitting polling and processing task.
pros:
- it moves load off poll agents and onto notificaiton agent
- we essentially get free healthcheck events by doing this
con:
to play devil's advocate. the one down side is that now
A couple things about this seem less than ideal:
* 2 means we load redundant stuff unless we edit entry_points.txt.
We do not want to encourage this sort of behavior. entry_points is
not configuration[1]. We should configure elsewhere to declare I
care about things X (including the
, Jun 8, 2015 09:04 PM
To: openstack-operatorsopenstack-operat...@lists.openstack.org;
OpenStack-devOpenStack-dev@lists.openstack.org;
Subject: [openstack-dev] [ceilometer] polling agent configuration speculation
(Posting to the mailing list rather than writing a spec or making
code because I
(Posting to the mailing list rather than writing a spec or making
code because I think it is important to get some input and feedback
before going off on something wild. Below I'm talking about
speculative plans and seeking feedback, not reporting decisions
about the future. Some of this
