Open Stack

On 06/06/2012 10:35 AM, Julien Danjou wrote:
> 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.

Maybe the problem of discrepancy of configuration is more an issue for
metering than for other components? At least that's my belief.

In fact, I may very well want to have differences in configuration of
different compute nodes in a single zone, for very valid reasons (ie use
different hypervisor settings, balance usage of components, etc...).
However if my metering agents are not all set to report the same things,
I think I'll be in trouble to correlate anything, hence the need for
metering configuration information to be provided centrally, for
anything that sets the behavior of meters and which meters to use.

Nick


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120606/d615355a/attachment.sig>