instance and instance.<type> meters emitted at different frequencies

[Eoghan Glynn]

The instance and instance.<type> counters are emitted at differing frequencies:

 - instance reflects the periodic_interval config (default = 600s)

 - instance.<type> reflects the instance_usage_audit_period config for nova (default = 1 month, usually the frequency is maxed out at 1 hour for ceilo-enabled deployments)

This occurs because the instance-related notification handlers emit both meters (driven by the instance.exists event) whereas the InstancePollster does not emit instance.<type>.

Both trigger-points should emit both meters.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/14852

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/14852
Committed: http://github.com/stackforge/ceilometer/commit/365c7a849a4c3333e40c944ce021263280eb2149
Submitter: Jenkins
Branch: master

commit 365c7a849a4c3333e40c944ce021263280eb2149
Author: Eoghan Glynn <email address hidden>
Date: Thu Oct 25 21:00:29 2012 +0000

    Instance pollster emits instance.<type> meter

    Fixes bug 1071486

    Previously the instance pollster emitted only the instance meter,
    whereas the notification handler for the instance.exists event
    emitted both instance and instance.<type>.

    Since the pollster & handler would generally be triggered at different
    frequencies (e.g. every 600s versus once an hour) this led to an
    imbalance in the metering store whereby the instance counters didn't
    match the sum of the per-flavor counters as expected.

    Change-Id: Ic76a645f150a87bc92b4ccfc7a777dfe13502467