Open Stack

On Tue, Jun 05 2012, Nick Barcet wrote:

> The main idea is that all agents of a given type should be sending
> similarly formatted information in order for the information to be
> usable, hence the need to ensure that configuration info is centrally
> stored and retrieved.  This would rule out, in my mind, the idea that we
> could use the global flags object, as distribution of the configuration
> file is left to the cloud implementor and does not lend for easy and
> synchronized updates of agent config.

IMHO this is solving a problem that already exists for all other
OpenStack components. A problem that no other OpenStack components tried
to resolved, AFAIK. So I don't see why we should try to resolve
configuration deployment in ceilometer when it's a much larger issue in
the project.

-- 
Julien Danjou
// eNovance                      http://enovance.com
// ✉ julien.danjou at enovance.com  ☎ +33 1 49 70 99 81